Article ID: 251410
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q251410
SYMPTOMS
A backup program that is Exchange-aware may stop during a backup or restore procedure of Microsoft Exchange Server 5.5 databases. Additionally, one or more of the following events may be logged in the application event log:
Event Type: Error
Event Source: ESE97
Event Category: Logging/Recovery
Event ID: 105
Description: MSExchangeIS ((nnn)) The database engine has stopped the backup with error -1032.
Event Type: Error
Event Source: ESE97
Event Category: General
Event ID: 145
Description: MSExchangeIS ((nnn)) The database engine could not access the file called [path]\exchsrvr\MDBDATA\\edbxxxxx.log.
Event Type: Error
Event Source: ESE97
Event Category: General
Event ID: 145
Description: (1996) The database engine could not access the file called [path]\exchsrvr\mdbdata\tmp.edb.
CAUSE
This problem can occur if the current backup or restore job cannot access a file. A file can be made unavailable when another backup or restore job puts a file lock on the file, or when antivirus software mistakenly quarantines the file. When the Extensible Storage Engine (ESE) backup or restore process cannot open a needed file, ESE97 generates events similar to those in the "Symptoms" section, and the backup or restore process stops.
RESOLUTION
Disable one of the conflicting backup or restore jobs, or make sure that the antivirus software is not file-level scanning the Exchange folders. You may have to contact the software vendor to find the conflicting backup or restore job, or for help with the configuration of file-level virus scan exclusions.
Keywords: kbprb KB251410
