Solved

Exchange 5.5 ESE97 STOP error during backup.

Posted on 2004-03-25
1
503 Views
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.

Regards,

Sean  
0
Comment
Question by:johns12345678902002
1 Comment
 
LVL 27

Accepted Solution

by:
Exchange_Admin earned 125 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.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Office 365 Login Audit Report 1 36
Exchange 2003 to Office 365 8 58
Email Header Detail 12 55
ADFS: When usernames dont match with your Active Directory 26 30
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

778 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