Hi,Our old Exchange 2003 server got a data corruption recently, we have to build a new Exchange server and restore the last know good backup into it. After the restore, the user mailbox database mounted successfully. But we have to re-link the AD user with each mailbox manually. Then another problem comes, the Exchange 2003 server for some reason,runs very very slow during the day time (The CPU is always in high usage for store.exe process). And we got heaps of warning in event log for the restore user mailbox storage. Users though can send/receive emails without any problems. The event log warning says sth like "Problem with Functions and Description of Storage: UserMailbox Database, EcUpdate Link fail". Sorry I forgot to write down the event ID. But hoep those info helps.The Exchange Server does perform well after the business hour... with few users logged on.My suspecision is the usermailbox store db is still in kind of dirty status. I am thinking to creat another mail store and move all the user database across?Can anyone tell is that the right thing to do?Cheers,

~ First thing I would say to run ExBPA and see if something reasonable pops up there related to stale entry of old server. ~ Make sure that Exchange is fully updated with latest patchesavailableat update site. ~ It's a good idea, you may also try by moving mailboxes to new database which would skip the corruption from mailboxes. Also post the errors related to database, which may help to identify the direction...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hi Amit,The event warning for the databaseis:Event Source: MSExchangeIS MailboxType: WarningCategory: GeneralEvent ID: 1025An error occurred on database "First Storage Group\Mailbox Store".Function name or description of problem: SLINK::EcUpdateError: 0x8004010f Thanks for the suggestions.

Hello, Please run ExBPA and update your server with the latest updates. Then restart the server and test the issue again. The 1025 events are not an indication of serious corruption in a database. They do however point out that some pointers are not valid within the information store. I suggest you run Isinteg on the server and test the issue c:\program files\exchsrvr\bin>isinteg -s servername -fix -test alltests Exchange Command-Line Parameters for the Isinteg.exe Tool http://support.microsoft.com/?id=301460 After you run ISINTEG FIX, you will see many warnings but you can safely ignore these messages. You should only pay attendtion to the end of ISINTEG. There should be zero errors reported. If there is an error, run ISINTEG again. Related article: Using the Exchange tools ISINTEG and ESEUTIL to Ensure the Health of your Information Store http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html Thanks, Elvis