This Warning event indicates that the backup has been stopped because it was halted by the client or the connection with the client failed.

The most frequent cause of the error is that a third-party online Exchange-aware backup software program has problems. Other known causes are as follows:

• A checksum mismatch (corruption) in the database.

• Losing the connection between the backup client and the Exchange server.

• Manually ending the connection between the backup client and the Exchange server.

To resolve this event, try one or more of the following:

• If you are using a third-party backup application, the first step is to make sure that logging of the backup software itself is enabled. Then, examine the logs of the backup software.

• Check on the Web site of the backup software vendor to see whether this is a known issue and if an update or hotfix is available.

• Try the backup with NT Backup. If the backup succeeds, the backup software is at fault and the issue must be referred to the backup software vendor.

• Check the Application log and make sure that there are no database errors.

• Check the System log for hardware errors.

• Make sure that the backup software agent has not lost network connectivity to the Exchange server. If this happens, restart the database backup.

Note  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.

You receive the following error in the Description section of ESE Event ID 215:

The backup has been stopped because it was halted by the client or the connection with the client failed.

The most frequent cause of the error is that a 3rd party online Exchange-aware backup software program has problems.

Other known causes are a checksum mismatch (corruption) in the database, losing the connection between the backup client and the Exchange server, and manually ending the connection between the backup client and the Exchange server.

1. The first step is to make sure logging of the backup software itself is enabled. Examine the logs of the backup software. Check on the web site of the backup software vendor to see if this is a known issue and if a hotfix is available. Try the backup with NT Backup. If the backup succeeds, the backup software is at fault and the issue needs to be referred to the backup software vendor.
2. Check the application log and make sure there are no database errors and check the system log for hardware errors.
3. Make sure that the backup software agent has not lost network connectivity to the Exchange server. If so, restart the database backup.

You receive the following error in the Description section of ESE Event ID 215:

The backup has been stopped because it was halted by the client or the connection with the client failed.

The most frequent cause of the error is that a 3rd party online Exchange-aware backup software program has problems.

Other known causes are a checksum mismatch (corruption) in the database, losing the connection between the backup client and the Exchange server, and manually ending the connection between the backup client and the Exchange server.

1. The first step is to make sure logging of the backup software itself is enabled. Examine the logs of the backup software. Check on the website of the backup software vendor to see if this is a known issue and if a patch or hotfix is available. Try the backup with NT Backup. If the backup succeeds, the backup software is at fault and the issue needs to be referred to the backup software vendor.

2. Check the application log and make sure there are no database errors and check the system log for hardware errors.

3. Make sure that the backup software agent has not lost network connectivity to the Exchange server. If so, restart the database backup.