Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 145 Source: ESE97
MSExchangeIS ((nnn)) The database engine could not access the file called <path>\exchsrvr\MDBDATA\\edbxxxxx.log.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Information Store service?
This event might occur after you restore the directory from an offline backup. See ME311396 for details about this issue.
See ME242063, ME253111 and "JSI Tip 1780" for additional information on this event.
A program has the file that the event lists locked open. Backup and antivirus software may lock files open.
As per Microsoft: "This issue can occur if the Exchange Server service account does not have Write permission to the Priv.edb file. The ability to write to this file can be restricted by insufficient NTFS file system (NTFS) rights to the PRIV.EDB file, or by a read-only file attribute applied to the PRIV.EDB file". See ME245058 for more details.
There are several Microsoft articles with information about this event: ME224977, ME241855, ME247788, ME251410 and ME260230.
This problem can occur if the current backup job conflicts with another backup job, which may or may not be Exchange Server aware. When the Extensible Storage Engine (ESE) backup process cannot open a transaction log because there is a conflicting backup job, ESE97 generates the two events in the "Symptoms" section of this article, and the backup program stops.
|Private comment: Subscribers only. See example of private comment|
|Links: ME224977, ME241855, ME242063, ME245058, ME247788, ME251410, ME253111, ME260230, ME311396, JSI Tip 7180|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated