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: 25100 Source: OnePointOperations

Failed to create a COM object for inserting events into the database. Will retry every 30 seconds.
Details: <details>.
- Details: The specified module could not be found - I caught this error after upgrading the HDD in my server and moving all files between HDDs using Windows Explorer.
The problem is in 8.3 names. To fix this problem do the following:
1. Open log file Temp\Microsoft Operations Manager\*init*.
2. Find inside it all GUIDs with error "not found".
3. Open command prompt, type "cd c:\program files", then dir /x.
4. Remember the short name for "Microsoft Operations Manager 2005", in my case it was "MICROS~4".
5. Open regedit, find one by one all GUIDs and change where it is necessary the short name to the new one. In my case, I replaced MICROS~3 with MICROS~4.
See ME922333 and the link to "FAQShop Article" for information on solving this problem.

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.