Hello. I've seen on the Windows Event Log the following error messages every 20 minutes: Event ID 1025: An error occurred on database "DB03 ". Function name or description of problem: Cannot generate Read Notification when Sender Data is missing!!!! Error: 0x8004010f Event ID 1025: An error occurred on database "DB03 - Executivos". Function name or description of problem: EcSetRNProps: Error: 0x8004010f Event ID 1025: An error occurred on database "DB03 - Executivos". Function name or description of problem: EcGenerateReadReport: Error: 0x8004010f Event ID 1025: An error occurred on database "DB03 - Executivos". Function name or description of problem: EcGenerateNRN: Error: 0x8004010f Any ideas about this ?

Any Exchange feature that is not working? Anything you did that lead to this?

Apparently all the things are working fine.

Try this blog: http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/2455f214-643e-4f4f-9b08-21c1860dc67b

Hi Jean, I have some points for you: 1 Run Isinteg -s servername -fix -test alltests 2 Refer to http://support.microsoft.com/kb/899393 Thanks.Rowen TechNet Community Support

I see that KB is designed for Exchange 2000 and Exchange 2003. I'm running Exchange 2010. Is there any problem on doing that procedures?

Eseutil and isinteg are Exchange 2007 compatible tools as well. Therefore, you should be good with 2010. Please note to test your procedures first on a testing environment.

Hi Jean, In Exchange 2010 RTM and earlier, you could repair a mailbox with the Information Store Integrity Checker (Isinteg.exe) tool. To repair mailboxes, you needed to dismount the mailbox database on which that mailbox resided and run the fixes while the database was offline. Exchange 2010 SP1 introduces the New-MailboxRepairRequest cmdlet that allows you to detect and repair a corrupted mailbox while leaving the mailbox database online. http://technet.microsoft.com/en-us/library/ff625226.aspx Thanks.Rowen TechNet Community Support

I will try this command on the weekend.

hi, Any update? thanks,CastinLu TechNet Community Support

Looks like this problem was solved. :) But now, from random time, those messages appear on this server: Event ID 1 Source: VDS Basic Provider Unexpected failure. Error code: 490@01010004 and Event ID 36888 Source: Schannel The following fatal alert was generated: 10. The internal error state is 1203. Any updates?