() Server registered: / (callback DLL , flags ).

Product: Exchange
Event ID: 905
Version: 6.5.7638.0
Component: Microsoft Exchange Extensible Storage Engine Backup
Message: <process name> (<process id>) Server registered: <name> / <service name> (callback DLL <DLL name>, flags <value>).

This is an informational event typically associated with an Exchange store database or a Site Replication Service (SRS) database that dismounts with an error or cannot be mounted with an error.

Note   “Server registered” always refers to Exchange Server and means that the Extensible Storage Engine (ESE) backup endpoints have been registered. The service referenced in the event can be the Microsoft Exchange Information Store service or the SRS.

See User Action for some specific causes and resolutions to this error.

User Action

The following are some specific causes and resolutions associated with ESEBackup Event 905:

  • The version of antivirus software being used had a problem that caused the database shutdown, and required an upgrade of the version, a downgrade of the version, or a fix. Check to determine whether this could be caused by the current state of the antivirus software installed on the server that is running Exchange. For information about troubleshooting this potential cause, contact your antivirus software vendor.
  • The incorrect restore file was selected for an online Exchange-aware restore. Rerun the restore process using the correct backup file.
  • Some of the log files used by the Exchange store database and the storage group had been removed and replaced. For information about troubleshooting Exchange transaction log file problems during data recovery, see Microsoft Knowledge Base article 812592 “How and when to manipulate Exchange transaction logs in disaster recovery” (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=812592).

If you still cannot restore your backup, examine the Application log for associated events that may help you determine the root cause of the Exchange store database failure or the SRS database failure.


Leave a Reply