Error message: An error occurred on database "Third Storage Group\Mailbox Database3". Function name or description of problem: SLINK::EcUpdate Error: 0x8004010f ----This is the first time to receive this message. Yesterday my online maintenance for databases were overlapping, so I changed the times. No error message for the other two db or storage groups.What do I need to do.

Hi,Looks like database has some minor logical corruption, you can run isinteg on Exchange database to remove it.You can run below command to just test Exchange database for corruption.isinteg.exe -s <servername> -test alltestsIf you see any corruption in above command then you can run it with -fix switch to correct the corruption.isinteg.exe -s <servername> -fix -test alltestsReferences:Exchange Command-Line Parameters for the Isinteg.exe Toolhttp://support.microsoft.com/kb/301460Similar thread:http://www.winserverkb.com/Uwe/Forum.aspx/exchange-admin/49846/Event-1025-SLINK-EcUpdateAmit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

As stated by Amit already you can always run ISINTEG or ESUTIL /G to check the corruption level in the relative information store yet that demands a significant downtime for the services. If you are comfortable doing a logical check on databases you can go with option suggested by Amit. The other way around it would be to create a new information store (if you have enterprise edition, and I preassume that you are running Exchange 2003) and start moving all your mailboxes to the newer one.M-Milind Naphade

What causes a database to be corrupted? I moved the mailboxes to another database from the database that appeared corruption. When doing so, I choose the option to skip the mailbox if a message was corrupted. All the mailboxes moved fine and the database did not show corrupted afterwards in the event viewer. What next?

There are many factor involved in database corruption, third-party software installed on server, mailbox access method by various third-party products, file-level antivirus scanning, hardware problem ect... however which you had, was minor corruption in which some pointer would be pointing to incorrect address in the database and could be ignored if error doesn't log frequently in event log...Just monitor the database where you moved mailboxes for couple of days for the same error. You can dialtone the Mailbox Database3 (dismount the database, delete edb/stm file and mount the store by ignoring warning that it will mount blank database) then you can move the mailboxes back to database3 to balance mailboxes load if required...Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com