My exchange database were corrupted after a unsuccessfull back up. so i tried to fix it with eseutil /p and eseutil /d but when i try to mount the database i still get an error and it suggest me to restart exchange information store and exchange system manager.
Cannot mount mailbox store. ESEUTIL reports clean. ISINTEG cannot run.
After restart the mailbox store will not mount "The database files in this store are corrupted". I ran eseutil /p and eseutil /d on both the public an private stores. I attempted to mount the store once before running isinteg.exe as directed but the stores won't mount. Still says database files are corrupted. When I attempt to run isinteg anyway it returns "isinteg cannot initiate verification process, check log file...". I cannot find a log file at the default location. I added the -l parameter to direct the log file to the current directory but no file was created.
after doing the /p did you check with the header of the database with the eseutil /mh wheter is it in a cleanshutdown state if yes
check with the storage group properties and check with the log file location and make sure that we dont have any logfiles there because when we mount the store it will try to replay the log file which will not work in our case because we already did a repair so the log signatures are completely diff now
so even after that if we have some problem in mounting the store try to mount a blank store and check we are able to mount it
for the ISINTEG to fail with the verification process try to run ISINTEG with the rowcounts switch which will fix the issue
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi mate,
Common mistake... which i use to see on most of the customer environment who use to run hard repair... may be this could be causing...
When we run hard repair major 3 steps procedure eseutil /p eseutil /d isinteg -fix
Once we do eseutil /p run eseutil /mh and confirm your database status should be clean shutdown.. Then run eseutil /d and then run eseutil /mh and confirm the status...
Now it's a time to mount the database (where the major mistake happen) Client use to forget that then need only keep the .edb and stm and rest of the files like log files, chk, temp etc need to moved out because those log file have old signature and our database will new signature.
Second think before you mount the database make sure you check the option "this database can be overwritten with the previous version"
Then dismount the database and run isinteg -fix
If you are still not able to mount after eseutil /d please paste the error message and application log event id.
Client use to forget that then need only keep the .edb and stm and rest of the files like log files, chk, temp etc need to moved out because those log file have old signature and our database will new signature.
Thanks for the reply. My server is working now. ^_^
Although Microsoft Exchange server application offers ESEUTIL and ISINTEG command line utilities to solve Exchange errors. But, sometimes users have to face the data loss problems after running these tools. These command line utilities remove the damaged database pages during repair process and users face precious data loss situations. Therefore, ensure that you can live without some data before using these inbuilt utilities. Here is a good article that has explained how to use these utilities: http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html
In case, these command line utilities do not help or want to avoid data loss problems, users can try a third party Exchange server recovery software such as:http://www.recover-computerdata.com/exchange-server-recovery.html
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> General >> Exchange database doesn't mount 
Exchange database doesn't mount - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
