() Callback function call ended with error .

Details
Product: Exchange
Event ID: 904
Source: ESE BACKUP
Version: 6.5.7638.0
Component: Microsoft Exchange Extensible Storage Engine Backup
Message: <process name> (<process id>) Callback function call <name> ended with error <error code> <error message>.
   
Explanation

This Error event indicates that an Extensible Storage Engine (ESE) callback function returned an error. This can potentially signify a serious situation in which a backup or restore process has failed. The error message that is included in the message text of Event ID 904 will vary, depending on the problem encountered. See User Action for some specific causes and resolutions to this error.

   
User Action

The following are specific causes and resolutions for this problem:

  • Log files are missing, or are invalid, and ESE cannot finish log file replay after restoring the database files. For information about how to test your transaction log files for damage, see Microsoft Knowledge Base article 248122 “How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=248122).
  • You tried to restore a database and did not specify the option to enable the existing database to be overwritten by the restore process. You specify this option by selecting This database can be overwritten by a restore check box. This check box is located on the properties of a mailbox store or public folder store. For more information, see Microsoft Knowledge Base article 291996 “XADM: Event ID 904, 8012, 8010, and 8003 Messages Are Logged When You Restore a Database from Backup” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=291996).
  • The database was not dismounted before you started the restore process. Dismount the databases that you want to restore, and re-try the restore process.
  • You have tried to restore a database and the original database display name has been changed or is different. When restoring an online backup, make sure that the database names match the names of the databases at the time the backup was taken.
  • The checksum of the log files that exist on the server does not match the checksum of the log files on the backup. If this error occurs, one or more of your transaction log files may be damaged. For information about how to test your transaction log files for damage, see Microsoft Knowledge Base article 248122 “How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=248122).

If you cannot restore your backup after considering the information provided in this article, search the Microsoft Knowledge Base for more information about the specific error codes in this event. If after consulting additional information in the Microsoft Knowledge Base, you still cannot resolve this problem, contact Microsoft Product Support Services.

Related:

Leave a Reply