Last night I had one hard drive on the raid 5 array die. The hot spare took over and the array is currently rebuilding. Unfortunately the exchange databases and log files reside on that array and the e00.log file is corrupt. I ran integrity checks on both priv1 and pub1 databases and they are ok.
To solve this the following steps have to be done:
In this situation I would first take a copy of everything in your mdbdata folder as it is now. Once that’s done and confirmed you can move on. Have you confirmed the current state of the datbases via eseutil /mh.
i.e. eseutil /mh “c:program filesexchsrvrpriv1.edb”
If this shows the database as clean shutdown state then all the log files should have been committed to the database so you should be able to MOVE all the E00*.log files and mount that database. As I said before keep a copy of these just in case DON’T delete ANYTHING.
If the database state is dirty shutdown then you can try to rename the last E00*.log file back to E00.log and then try to mount the database.
http://support.microsoft.com/?kbid=896143.
Searching on the internet i found a post on Daniel Petri :
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724
In the Application event log, you may also receive following events.
Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 455
Date: 3/18/2001
Time: 5:14:22 PM
User: N/A
Computer: SERVER1
Description: Information Store (2376) Error -1811 (0xfffff8ed) occurred while opening log file D:exchsrvrMDBDATAE000xxx.log.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 3/18/2001
Time: 5:14:22 PM
User: N/A
Computer: SERVER1
Description: Error Current log file missing starting Storage Group /DC=COM/DC=COMPANY/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=MICROSOFT/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVER1/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store.
There might be a few reasons for these errors:
- You might be running an Anti-Virus program on the Exchange server and that program might not be properly configured. Read article KB245822 for more info on how to properly configure your Anti-Virus software on a computer running Exchange server.
- If the Anti-Virus Quarantine option is enabled on the Exchange server and the anti-virus is not configured according to article KB245822.
- If your Anti-Virus software is configured to scan x:Program FilesexchsrvrMDBDATA it might think that the “E00.log “ contains a virus, or that the file itself is the virus, therefore it will automatically quarantine the E00.log and cause the Exchange services to crash.
In order to solve these errors you might want to consider the following options:
Resolution
- Stop all exchange services.
- Configure your Anti-Virus program according to article KB245822.
- Save your current log files that are usually located on x:Program FilesexchsrvrMDBDATAExxxxxxx.Log to a temporary folder.
- Delete all *.log files in the x:Program FilesexchsrvrMDBDATA.
- Check that the folder “(x:Program FilesexchsrvrMDBDATA)” only contains the following files:
e00.chk
res1.log
res2.log
If not, move all extra files to a temporary folder.
- Start all Exchange Services and mount the Information Store service.
If the above procedure did not work, you might have a problem in the Exchange Database and you will need to try to resolve it by following option number two.
If the above procedure did not work, you might have a problem in the Exchange Database and you will need to refer to article KB313184.