Posts: 54
Joined: 26.Aug.2003
From: New Jersey
Status: offline
I came in on tuesday morning and found the exchange2003 Enterprise server was down. I went ot boot it up and came upon a msg of no boot disk found I did a manual reboot and the system came back up but the store would not mount. The IS while start though. I went do perform a /r /d and a /p but each opreation ended with a -1003 error code. I copied the priv1.edb and priv1.stm to antoher machine along with the required files and now I am getting a-550 (JET_errDatabseDirtyShutdown......)
any recommendations? also the the most current backups are not clean either so I am thinking the db has been corrupt for some time.
I have an Exchange 2010 enterprise srver ready to go.... What should I do to repair this db and migrate it?
It is the most common error and generally occurs when the Exchange Information Stored Database File is corrupted or damaged. Built-in eseutil.exe utilities can repair the damaged database but it might delete "Leaf Pages" all around the damaged database pages thus creating the data loss situation. In this case, a third party Exchange Server recovery software like Stellar Phoenix Mailbox Exchange recovery may help you. You can try the demo version to evaluate the results and its functionality interface.
When a database is in a dirty shutdown state, it means is that it has some transaction log files that have not been committed to it before it went offline. Do NOT run a hard repair (/p) yet!
Open a command prompt and change directory to drive:\exchange installation path\bin folder.
Type ESEUTIL /MH "drive:\path\databasename.edb" and check the output. There should be a log required entry that specifies which log files are needed to bring the database back into a clean shutdown state.
Locate these log files and make sure they are in the transaction log file path!
Move all other log files out of the folder.
In the command prompt, type ESEUTIL /R "drive:\path\e00.log" and it should replay the missing log files into the database.
Run ESEUTIL /MH "drive:\path\databasename.edb" again and check to see the state of the database.
If the required log files are missing, then you can restore from backup or run the hard repair but those are last resorts!
_____________________________
Ibrahim Benna - Microsoft Exchange MVP Forum Moderator Navantis
In order to sort out this issue, you need to use the following measures:
1. Run eseutil /r for the corrupted database that allows playing the transaction log files 2. If this doesn't help, restore from the last online backup if available 3. In case no valid backup is present, you can run run eseutil /p command, followed by eseutil /d to defragment the database.
Eeseutil /p is a hard repair command and checks each 4 KB database page for errors. If it finds errors that it cannot correct, it simply discards the page and proceeds further. Thus the command can cause serious data loss. To avoid data loss problem, you are suggested to use a safer Exchange server recovery program like this:http://www.recover-computerdata.com/exchange-server-recovery.html.
This EDB repair utility scans the corrupted database and repair it using powerful, yet safe, algorithms.The software rebuilds the Exchange database file and repaired database file can be directly mounted on the server. This tool is compatible with all versions of Exchange Server.
Which info or problem you show here, I think this is not a big deal for this Exchange Server Recovery Tool which I wish to recommend here. You can get back your all Exchange Server data any of versions to another Outlook PST format and use this PST on any of MS Outlook format. EDB to PST gives you guarantee for full accuracy in work and complete Data Recovery and Conversion. Get more info: http://www.exchangeedbtopst.edbpst.biz/
Make a right decision because data is most important!
_____________________________
Yasar Arafat Business Development Manager at Exchange Recovery
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Corrupt Priv1.edb 
Corrupt Priv1.edb - 
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
