Exchange 5.5 ESE97 STOP error during backup.

Posted on 2004-03-25
Medium Priority
Last Modified: 2008-02-01
Dear Sir,

Our Exchange 5.5 box has been producing an ESE97 error in its logs.  
Event ID:105, Source: ESE97, Type:  Error, Category: Logging/Recovery
Description:  MSExchangeIS (267) The database engine has stopped the backup with error -1811.

This occurs when our Backup Exec attempts to perform a differential backup, the ESE97 starts the backup...MSExchangeDS (236) The database engine is starting an incremental backup...but on the second go of the MSExchange IS, the above log is produced.  

MS article Q178934 says that this is a JET_errFileNotFound error, and that the error signals that a transation log is either missing of corrupt.  It recommends that the IS be stopped, and all .log files in \exchsrvr\mdbdata and the edb.chk from the \exchsrvr\mdbdata be moved to a temporary directory.  It then recommends restarting the IS and performing an online backup.

Veritas has an article that mirrors this one, however it recommends (smartly), a flat file backup before removing the logs  It also aims the article at 5.0, but the MS article says this info applies to 5.0 and 5.5.

My concern is in the accuracy of these articles.  Like others, I've been stung by the inaccuracy of these articles and, with an issue as serious as removing the logs/edb.chk and starting the IS, I wanted to check with and get the opinion of an expert first.  As well, the event I am experiencing starts with "MS Exchange IS (267)"  whereas the MS article refers to (190) and (202) and the Veritas article refers to (329).

Your advice would be appreciated.


Question by:johns12345678902002
1 Comment
LVL 27

Accepted Solution

Exchange_Admin earned 500 total points
ID: 10680815
When you stop the Information Store service all the log files will be committed to the database.
At this point you can move all the .log and edb.cjk files to a temporary location.

As long as the IS service stops gracefully everything should be ok and the IS service will be able to restart. If the IS does not restart properly then you can just move the log files back to their original locations.

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
Here is a method which can be used to help resolve a "Content Index Failed" error on a Microsoft Exchange Server.
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

586 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question