Hi all, Exchange 2010 ent server 1 database inconsistency eseutil /mh dirty shutdown eseutil /p running Deleting unicode fixup table. eseutil.exe crash Faulting application name: eseutil.exe, version: 14.0.692.0, time stamp: 0x4b8b6d3c Faulting module name: ESE.dll, version: 14.0.692.0, time stamp: 0x4b8b6d3e Exception code: 0xc0000005 Fault offset: 0x0000000000230274 Faulting process id: 0xaa4 Faulting application start time: 0x01cb40d1071020d2 Faulting application path: C:\Program Files\Microsoft\Exchange Server\V14\bin\eseutil.exe Faulting module path: C:\Program Files\Microsoft\Exchange Server\V14\bin\ESE.dll Report Id: 5318ec65-acc7-11df-b097-0050568f1ee1 Event id: 4999 Exchange 2010 Rollup4 install

Not sure if there is a question here, but running eseutil in repair mode is not a good idea unless you have no valid backups and can not move mailboxes if the store is up. After running eseutil/p, run isinteg until there are no errors. If you can mount the store, I would get a full, online backup and move mailboxes to another new clean store ASAP. Note that eseutil/p can result in data loss.

On Sat, 21 Aug 2010 13:18:02 +0000, AndyD_ wrote: > > >Not sure if there is a question here, but running eseutil in repair mode is not a good idea unless you have no valid backups and can not move mailboxes if the store is up. > >After running eseutil/p, run isinteg until there are no errors. If you can mount the store, I would get a full, online backup and move mailboxes to another new clean store ASAP. Note that eseutil/p can result in data loss. After running "eseutil /p" you should run "isinteg /d" and THEN isinteg. Lord knows what screwy-ness the repair introduced in indexes, views, etc. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Indeed. ( though I think you meant eseutil /d)

AndyD_: After running eseutil/p, run isinteg until there are no errors. If you can mount the store, I would get a full, online backup and move mailboxes to another new clean store ASAP. Note that eseutil/p can result in data loss. IsInteg and Exchange 2010? As of Exchange 2010 the well-known IsInteg tool was dropped. IsInteg is installed with the Mailbox Server role (default location C:\Program Files\Microsoft\Exchange Server\V14\Bin). But IsInteg hasn’t been updated to understand Exchange 2010′s new database structure. Goodbye IsInteg, hello New-MailboxRepairRequest http://eightwone.com/2010/06/14/goodbye-isinteg-hello-new-mailboxrepairrequest/ [Exchange 2010] Can not check mail database with isinteg Information Store crash http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/0e3278b8-517f-4dde-a0d7-0830f438c641 MCTS: Messaging | MCSE: S+M | Small Business Specialist

AndyD_: After running eseutil/p, run isinteg until there are no errors. If you can mount the store, I would get a full, online backup and move mailboxes to another new clean store ASAP. Note that eseutil/p can result in data loss. IsInteg and Exchange 2010? As of Exchange 2010 the well-known IsInteg tool was dropped. IsInteg is installed with the Mailbox Server role (default location C:\Program Files\Microsoft\Exchange Server\V14\Bin). But IsInteg hasn’t been updated to understand Exchange 2010′s new database structure. Goodbye IsInteg, hello New-MailboxRepairRequest http://eightwone.com/2010/06/14/goodbye-isinteg-hello-new-mailboxrepairrequest/ [Exchange 2010] Can not check mail database with isinteg Information Store crash http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/0e3278b8-517f-4dde-a0d7-0830f438c641 MCTS: Messaging | MCSE: S+M | Small Business Specialist Ah good one! Totally forgot about that. Thanks for the reminder! I just posted that one on automatic drive.

On Sat, 21 Aug 2010 23:00:28 +0000, AndyD_ wrote: > > >Indeed. ( though I think you meant eseutil /d) ACK! Yes, I did. Thanks. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi MsTolga, From your description, I am not clear about what is the meaning of “eseutil.exe crash”. Running in repair mode is not a good idea unless you did not have valid backups and quarantined Exchange log file. If the database is dirty shutdown, it can be resolved though these ways: 1. If the Exchange log file was quarantined, follow these steps to have a try: a. Recover the Exchange log to the folder that contains your production log files. b. Start the Microsoft Exchange Information Store service. 2. If the Exchange log file was deleted or the first method cannot give you any help, you can restore the database form a backup. 3. The last way is to resolve the problem by use eseutil/p. For your issue, you can try the other two ways before you use eseutil/p to repair the database. Here is a related article for your reference, hope this may give your some help: http://support.microsoft.com/kb/896143 Best wishes, Tyler