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

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

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.


Leave a Reply