Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 494 Source: ESENT

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.
As per ME954407, this issue occurs if the previous IFM (Install from Media) procedure was canceled or closed before it was finished. When this occurs, temporary files may be left in the Temp folder in the user's profile. See the article for resolution.
- Error code: -1216 - See ME954403.
In my case, renaming/moving all *.log files from %WINDIR%\system32\Catroot2 solved the problem.
See the link to "EventID 494 from source ESE" for details on this event.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.