This event indicates an unexpected error that relates to the Jet engine, ESE.dll, or to the Store process, (Store.exe). This is a generic error and the causes are various.
Associated problems seen with this event include a corrupt Exchange store database, but this symptom is not always associated with this event. In some cases, when there has been corruption of a database, an associated ESE Event ID 448 is logged in the application log. This indicates that there is a corruption or inconsistency in a table in the Jet database. In other cases, there has been no actual problem with Jet or the Exchange store and restarting the Exchange store has solved the issue.
- Check the application log for associated events, including checking ESE Event ID 448. If there is a question about the Exchange store database, check the integrity of the database using the command “ESEUTIL /G” (without the quotation marks).
- If there is an ESE Event ID 448 in the application log, check the log carefully for related events and patterns that could relate to this event. 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. Do this before proceeding to the next step.
If the Exchange store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database. If the database is running, you can also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.
If the Exchange store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the application log.
If the Exchange store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.
- If the error recurs, consider contacting Microsoft Product Support Services. If the root cause cannot be determined from the application and system logs, a debug session may be necessary to determine the root cause. However, the exact symptom would need to recur to capture the event in a debug session.