Exchange 2007, SP1--Server 2003One error message I received was:An error occurred on database "Third Storage Group\Mailbox Database3".Function name or description of problem: SLINK::EcUpdateError: 0x8004010f Another was a calendar error message on one mailbox.I moved all the mailboxes from the corrupted db and storage group to another db/storage group. When doing so, I marked do not move if any corrupted messages. All mailboxes/messages went without a problem. Unforunately we are not able to take the system down and trouble by dismounting any db. Next I deleted the db, storage group.Recreated the db and storage group and moved back the mailbox with the message about the calendar items being over the limit of 250.I removed all items/reminders from the mailbox with the message. While archiving the information from the mailbox I received an error message it needed to be repaired and to run scanpst.exeI did so and unchecked the cache mode. I was able to open the mailbox and archive.My manager wants to know exactly what happened and why. Thanks

That can be a difficult thing to assess in most cases. Checking the Event Log might give you some idea as running isinteg but mailboxes sometimes become corrupt. Could be AV file scanner not setup properly, could be hard disk issues, etc.MVP Exchange Server

Could moving a mailbox to a new storagegroup/db during the middle of the day cause it? I went through the event logs and noted this has happened 8 times since the beginning of the year. For 6 of those days, we were most likely moving mailboxes for testing.We were getting errors on our AV file scanner,could evenan updated for your AV file scanner did not occur cause this?Another thing we did was move the third storagegroup/db to a separate disk or drive. The folder is called Exchange and we placed the db/logs in that folder. Should we havecopied the folder like it is on theother disk or drive and removed those db and logs that would not apply? Thanks,

Could moving a mailbox to a new storagegroup/db during the middle of the day cause it? I would not think so as the mailbox is essentially closed/disconnected when moving.Have confirmedthe database free of integrity weaknesses?http://support.microsoft.com/kb/182081We were getting errors on our AV file scanner,could evenan updated for your AV file scanner did not occur cause this?Only if its scanning the database directory which shouldalways be excluded from AV File based scanning but in most cases must be manually configured to do so.Another thing we did was move the third storagegroup/db to a separate disk or drive. The folder is called Exchange and we placed the db/logs in that folder. Should we havecopied the folder like it is on theother disk or drive and removed those db and logs that would not apply?I assume you followed this procedure to move the databases and log files,http://support.microsoft.com/default.aspx/kb/821915MVP Exchange Server