() Error () during backup of a database (file ). The database will be unable to restore.

Details
Product: Exchange
Event ID: 217
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <number>Error (<error code>) during backup of a database (file <file name>). The database will be unable to restore.
   
Explanation

An error occurred during the online Exchange-aware backup of an Exchange Information Store database.

The cause for the online backup failure depends on the error listed in the Description section of the event. The most frequent causes are listed below.

  • This error may be generated because ESE was unable to gain exclusive access to the .pat file for the database. This file is created when the backup starts and it contains information about the changes that are made to specific pages while the backup is running. If pages are deleted during the backup after that part of the database has been written to tape, the .pat file holds the updated information. When the backup is completed, the .pat file is backed up and deleted. If the database goes offline during backup, the .pat file is not deleted until the next time backup starts and ESE deletes the current one and creates a new one.
  • Another cause relates to the -1018 error = JET_errReadVerifyFailure in the Description. This error indicates a hardware-related root cause. Check the system log, run chkdsk and perform other diagnostic tasks.
  • Another possible description relates to the -613 error. Error -613 translates to JET_errSLVReadVerifyFailure (checksum error in SLV file during backup, where “SLV” stands for “streaming” or “.stm” file). Error -613 may also be hardware related. Check the system log, run chkdsk and perform other diagnostic tasks. It is suspected that Error -613 may occur from non-hardware related issues such as different 3rd party SMTP disclaimer software packages.

Other causes are under investigation. If you have exhaustively checked all hardware-related causes, contact Microsoft Product Support Services.

   
User Action
  • If the .pat file is locked by another program such as antivirus or backup software, ESE will fail the backup. The resolution is to stop the other software or wait for it to finish accessing the .pat file. Perform another backup of the database.
  • If the Error in the description is -1018, to perform a successful backup, use one of the following methods. First determine the root cause of the failure and fix it — Error -1018 will return if the root cause is not fixed. Restore the information store from the previous online backup or if the mailbox store is affected and you have an Enterprise version of Exchange, move the mailboxes to another server or mailbox store. To repair the corruption in database pages if you do not have a valid backup and you are running the standard version of Exchange, run the eseutil /p command, and then run the isinteg -fix command on the affected store.

    CAUTION: After you make repairs to the database by using the eseutil /p switch, the database may not be stable and reliable. Because the repair process deletes database pages, data loss is likely.

    NOTE: If you must run a hard repair on your production database, Microsoft recommends that you move the data out of the repaired database to a new database, or rebuild the database using Move Mailbox or ExMerge.

  • If the Error in the description is -613, follow the resolution steps for Error -1018. NOTE: if the resolution requires a repair (as a last resort), you cannot repair the .stm file alone — you must repair the .edb file and its associated .stm file.

Related:

%1 (%2) %3The backup has stopped with error %4.

Details
Product: Exchange
Event ID: 214
Source: ESE
Version: 8.0
Symbolic Name: STOP_BACKUP_ERROR_INSTANCE_ID
Message: %1 (%2) %3The backup has stopped with error %4.
   
Explanation

This Warning event indicates that the backup has stopped with an error. The cause depends on the error listed at the end of the Description section of the event. The most frequent causes are as follows:

  • Error -521 = 0xfffffdf7 = 4294966775 = Jet_errInvalidBackupSequence = Backup callout of sequence. This is a generic error with several causes and it has been seen when antivirus software is running on the server and scanning the folder of affected databases. The error has been seen when third-party backup software is running on the server and a problem with the software is causing the error.

  • Error -1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file – the file is locked or in use. This error can occur if the account performing the backup does not have enough permissions to perform the backup.

  • Error -612 = 0xfffffd9c = Jet_errLogReadVerifyFailure = Checksum error in log file during backup. This indicates a corrupt transaction log file. A backup cannot be made of a corrupt log file and the backup will fail. A checksum ESE error indicates a hardware root cause and is caused by hardware, controller, or file system-level problems related to hardware.

   
User Action

To resolve this warning, do one or more of the following:

  • For error -521, the resolution depends on the cause. If antivirus software is running on the server, do a comprehensive and exhaustive check on the subfolders the software is running against and remove the Exchange databases, log files, and check files. If you are using third-party backup software, attempt a backup with Exchange-aware backup software. If it succeeds, check with your vendor for any patches, updates, or fixes for your software.

  • For error -1032, ensure that the account performing the backup has enough permissions to perform the backup.

  • For error -612, check the application event log carefully for related events and patterns. Check the System log carefully for related events and patterns, including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. If the Exchange store database is running, use ExMerge to transfer your data to .pst files. You may then be able to stop the Exchange store. Run eseutil /mh and if the database is consistent, remove all the log files and check file, start the Exchange store, and perform a successful online backup.

  • For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

() The backup has stopped with error .

Details
Product: Exchange
Event ID: 214
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <instance>The backup has stopped with error <error code>.
   
Explanation

The backup has

stopped with an error [error #].

The cause depends on the Error listed at the end of the Description section of the event. The most frequent causes are as follows:

  • Error -521 = 0xfffffdf7 = 4294966775 = JET_errInvalidBackupSequence = Backup call out of sequence. This is a generic error with several causes and it has been seen when anti-virus software is running on the server and scanning the folder where affected databases were. The error has been seen when anti-virus software is scanning the M: drive. The error has been seen when 3rd Party backup software is running on the server and a problem with the software is causing the error.
  • Error -1032 = 0xfffffbf8 = 4294966264 = JET_errFileAccessDenied = Cannot access file – the file is locked or in use. This error can occur if the account performing the backup does not have enough permissions to perform the backup.
  • Error -612 = 0xfffffd9c = JET_errLogReadVerifyFailure = Checksum error in log file during backup. This indicates a corrupt transaction log file. A backup cannot be made of a corrupt log file and the backup will fail. A checksum Jet error indicates a hardware root cause and is caused by hardware, controller, or file system level problems related to hardware.
   
User Action
  • Error -521 – the resolution depends on the actual cause. If anti-virus software is running on the server, do a comprehensive and exhaustive check on which subfolders the software is running against and remove the Exchange databases, log files, and check files and remove the M: drive from the scan. If you are using 3rd Party backup software, attempt a backup with NT Exchange-aware backup. If it succeeds, check with your vendor for any patches, updates, or fixes for your software.
  • Error -1032 – ensure the account performing the backup has enough permissions to perform the backup.
  • Error -612 – Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. If the information store database is running, it is suggested that you ExMerge your data to .pst files. You then may be able to stop the information store. If the database is consistent with Eseutil /MH, you can then remove all the log files and check file, start the information store, and perform a successful online backup.

Related:

%1 (%2) %3Error (%4) during backup of a database (file %5). The database will be unable to restore.

Details
Product: Exchange
Event ID: 217
Source: ESE
Version: 8.0
Symbolic Name: BACKUP_ERROR_FOR_ONE_DATABASE
Message: %1 (%2) %3Error (%4) during backup of a database (file %5). The database will be unable to restore.
   
Explanation

This Error event indicates that an error occurred during the online Exchange-aware backup of an Exchange store database. The cause for the online backup failure depends on the error listed in the Description section of the event. The most frequent causes are the following:

  • This error may be generated because ESE was unable to gain exclusive access to the .pat file for the database. This file is created when the backup starts and it contains information about the changes that are made to specific pages while the backup is running.

    • If pages are deleted during the backup, then after that part of the database has been written to tape, the .pat file holds the updated information. When the backup is completed, the .pat file is backed up and deleted.

    • If the database goes offline during backup, then the .pat file is not deleted until the next time backup starts and ESE deletes the current one and creates a new one.

  • Another cause relates to the -1018 error in the Description section. This error indicates a hardware-related root cause. Check the system log, run chkdsk and perform other diagnostic tasks.

  • Another possible description relates to the -613 error. Error -613 signifies a checksum error in the SLV file during backup, where SLV stands for streaming, or .stm file. Error -613 may also be hardware-related. Check the system log, run chkdsk and perform other diagnostic tasks. It is suspected that error -613 may occur from non-hardware related issues such as different third-party SMTP disclaimer software packages. Other causes are under investigation. If you have exhaustively checked all hardware-related causes, contact Microsoft Product Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

   
User Action

To resolve this error, do one or more of the following:

  • If the .pat file is locked by another program such as antivirus or backup software, ESE will fail the backup. To resolve this error, stop the other software or wait for it to finish accessing the .pat file. Perform another backup of the database.

  • If the error in the description is error -1018, perform a successful backup, by one of the following methods. First, determine the root cause of the failure and fix it. -1018 errors will return if the root cause is not fixed. Restore the Exchange store from the previous online backup or if the mailbox store is affected and you have an Enterprise version of Exchange, move the mailboxes to another server or mailbox store. To repair the corruption in database pages if you do not have a valid backup and you are running the Standard version of Exchange, run the eseutil /p command, and then run the isinteg -fix command on the affected store. After you make repairs to the database by using the eseutil /p command, the database may not be stable and reliable. Because the repair process deletes database pages, data loss is likely.

    Note   If you must run a hard repair on your production database, Microsoft recommends that you move the data out of the repaired database to a new database, or rebuild the database using Move Mailbox or ExMerge.

  • If the error in the description is -613, follow the resolution steps for error -1018. If the resolution requires a repair, as a last resort, you cannot repair the .stm file alone. You must repair the .edb file and its associated .stm file.

  • For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

%1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.

Details
Product: Windows Operating System
Event ID: 489
Source: ESENT
Version: 5.2
Symbolic Name: OSFS_OPEN_FILE_RO_ERROR_ID
Message: %1 (%2) %3An attempt to open the file “%4” for read only access failed with system error %6: “%7”. The open file operation will fail with error %5.
   
Explanation

An error occurred while a file was being opened.

Probable causes include:

  • The file is locked or in use.
  • A virus checker might have mistakenly quarantined a file, or a backup process might have temporarily denied access.
  • A flat file backup system or anti-virus software might be running against the database, the check file directories, or the M drive.
  • The permissions on the folder (such as MDBDATA) that contains the files for the information stores are not sufficient for the stores to function correctly.
  • A disk input/output (I/O) problem prevented access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive was lost, perhaps temporarily. This issue can occur when the path for the check file (such as E00.chk) is not correct.
  • The path for the log files or the check file was changed before the system was restored.
  • The check file (such as E00.chk) is corrupted.
   
User Action

To solve this problem, do one or all of the following:

If the file is locked or in use:

  • Change the permissions on the folders that contain the information store files to the default permissions.
  • Configure the flat file backup and anti-virus software to not scan the Windows Information Store subdirectories or the M drive.
  • Use an online backup and anti-virus software.

If there is an Input/Output problem, do one or all of the following:

  • Run chkdsk /f /r at the command prompt.
  • Examine the permissions on the folder structure.
  • Troubleshoot any file-level antivirus software running.
  • Check the System Log in Event Viewer for any related I/O or drive events.
  • Check and correct the path for the check file (such as E00.chk).
  • Correct the root cause, and then restore from online backup, if there is a recent backup.

If the path was changed:

  • Move the Information Store files back to their original locations and then try to restore again.
  • If the .chk file is corrupt, you may be able to remove it and read all the transactions into the database. If the database remains inconsistent, then restore from online backup if there is a recent version.

For more information about this event, see article Q823022 in the Microsoft Knowledge Base.

Related: