Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Information Store (<PID>) Database recovery failed with error <error> because it encountered references to a database, '<database>', which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of ESENT?
Several support forums posts suggest the use of third party edb recovery tools instead of esutil (esutil will not try too hard to recover the lost data, but simply will remove the parts that cause a problem without attempting to restore the actual content). Try a Google search for "edb file recovery".
If you receive this event with error -1216 (JET_errAttachedDatabaseMismatch), refer to ME296843 for more detailed info about this and recovery steps to take.
As per Microsoft: "This behavior may occur if the information store does not have access to the Microsoft Active Directory directory service. During the recovery procedure, the information store process queries Active Directory for the existence of the database GUID that is represented by the transaction log files in the Exchsrvr\Mdbdata log folder. If the GUID is not located, these logs are determined to be from a different database. The soft recovery process does not commit these transactions". See ME823168, ME843092, MSEX2K3DB, and the links to "EventID 494 from source ESE98" and EV100310 (ESE Errors) for details on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 494 from source ESE98|
|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