() The database engine could not find the entrypoint in the file .

Details
Product: Exchange
Event ID: 601
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The database engine could not find the entrypoint <name> in the file <file name>.
   
Explanation

The database engine could not find the function at the specified entry point.

   
User Action

Check the version of the DLL file. The version number should be at least 6.0.

Related:

() The database engine could not access the file called .

Details
Product: Exchange
Event ID: 427
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The database engine could not access the file called <file name>.
   
Explanation

This occurs when access is denied to the file.

   
User Action

This event will be preceded by other related events which have specific information necessary to resolve the issue.

Related:

() The database created at was not recovered.

Details
Product: Exchange
Event ID: 422
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>The database <name> created at <date/time> was not recovered.
   
Explanation

Unable to recover the current database.

   
User Action

Restore an external backup version of the database. Use a backup utility to retrieve the database from backup media.

Related:

() File system error during IO on database . If this error persists, the database file may be damaged and may need to be restored from a previous backup.

Details
Product: Exchange
Event ID: 441
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>File system error <error code> during IO on database <name>. If this error persists, the database file may be damaged and may need to be restored from a previous backup.
   
Explanation

A file system error was reported when doing input/output (I/O) operations.

   
User Action

If the error persists, the database file may be damaged. The database needs to be restored from a previous backup.

Related:

%1 (%2) %3The database engine stopped the instance (%4).

Details
Product: Windows Operating System
Event ID: 103
Source: ESENT
Version: 5.2
Symbolic Name: STOP_INSTANCE_ID
Message: %1 (%2) %3The database engine stopped the instance (%4).
   
Explanation
There is only one Jet database engine, ESE.dll, per server. However, there can be one instance of Jet running per storage group. Event 103 indicates which instance has stopped. Event ID 103 has many potential causes – check events in the Application log before and after Event 103 to determine which errors are mentioned in the Description section of other events. Known causes for the database instance stopping with event 103 are as follows:

  • Failing to apply an Exchange service pack for a reinstall or an Exchange-aware restore.
  • Running out of disk space.
  • Attempting to restore multiple storage groups simultaneously.
  • Applying an Exchange service pack, which resulted in the databases becoming inconsistent.
   
User Action
The resolution depends on the error code in the Description of the associated events in the application log. In many cases, no user intervention will be necessary.

Related: