|Message ||Exchange 5.5 sp3
Corrupt Information store pub.edb or priv.edb
This was a fix that worked when an Exchange 5.5 information store was corrupted because of a .vbs virus. The information store unexpectedly stopped and could not be restarted. You must have a recent Information Store back up and the backup software must support Exchange Server for this to work.
1. Stop all Exchange services.
2. Go to the directory or directories \exchsrvr\mdbdata where the priv.edb, pub.edb, and log files are stored and rename folder or folders "mdbdata" to "mdbdataold".
NOTE: Make sure the drive that the mdbdata folder is on has enough space to hold a little more than a copy of the files ( example: if the information stores are 25gig combined make sure there is 26gig or more space available).
If there is not enough space on server, then you will have to move the mdbdataold folder or folders to another server that has space. If the server has more than one drive.
EXAMPLE: c:\exchsrvr\mdbdata--no files in directory
d:\exchsrvr\mdbdata--log files in directory
e:\exchsrvr\mdbdata--information store files only
*Log files and Information store files are separated*
If the Server has one drive.
EXAMPLE: \exchsrvr\mdbdata--log files and information store files
*Log files and Information store files are together*
3. Create a new folder in \exchsrvr\ called mdbdata if you have multiple drives and renamed multiple mdbdata folders to mdbdataold, create new mdbdata folders on those drives too.
4. Check \exchsrvr\mdbdata folder or folders and make sure there are no files in those directories, if there are files go back and follow the directions on step 2-3 again.
5. Start the System Attendant service
6. ONLY Run a full restore of the Information Store from the last backup.
*your backup software MUST support MS Exchange and be able to back up the Information Store*
7. After restore is completed check the Low Log and High Log file number. Go to regedit and go to the following key:
~~~~Check the RIP Restore Progress key---High log and Low log number~~~~
EXAMPLE OF NUMBERS:
Low : edbx377a.log
Write these numbers down.
8. Go to the directory where log files are stored \exchsrvr\mdbdata and check to see which log files are stored. The Log sequence should start with the Low Log number and end with the High Log number.
9. Go to the \exchsrvr\mdbdataold directory where the old log files were stored and check the sequence of the log files.
This is an EXAMPLE of a GENERAL sequence of log files. ( all log files must be 5.0mb if they are not, they are not complete and can not be used)
* edbxxx80.log *ect... ---sequence starts over---
Only copy the log files that will complete the sequence to \exchsrvr\mdbdata . All files that do not complete a sequence can not be used. Here is an EXAMPLE of what to do with the information above.
edbx3778.log 5.0mb.............edbx377a.log 5.0mb
edbx3779.log 5.0mb.............edbx377b.log 5.0mb
edbx377a.log 5.0mb.............edbx377c.log 5.0mb
From the mdbdataold folder you can only copy log files [ edbx377d.log---edbx777f.log ] because that would make the sequence complete. All other log files could not be used.
10. Double check log file sequence in the directory \exchsrvr\mdbdata
11. Start MS Exchange services.
12. The Services manager should show the MS Exchange Information Store "Starting"
13. The Event viewer under applications should show the Processing of Log files ( this will take a couple of minuets depending on the number of log files).
14. After log files are processed all exchange services should start and the Exchange Server should be up and running.
This MAY work on Exchange 2000, but has never been tried.