Ops Mgr 2007 “Failed Accessing Windows Event Log”
If you’ve been getting these errors from your Operations Manager 2007 DHCP Management Pack, the solution is at hand! Here’s the typical error you’d get:
Failed Accessing Windows Event Log
The Windows Event Log Provider was unable to open the System event log on computer ‘{69E3F0CF-36C3-9FDC-1892-42FB003E34DB}’ for reading. The provider will retry opening the log every 30 seconds. Most recent error details: The RPC server is unavailable. One or more workflows were affected by this. Workflow name: Microsoft.Windows.DHCPServer.Library.Server.UnitMonitor.DependentServiceHealth Instance name: myserver.mycompany.local Instance ID: {69E3F0CF-36C3-9FDC-1892-42FB003E34DB} Management group: MyCompany-SysCtrOpsMgr
It seems that the DHCP MP v6.0.6383.0 introduced this annoying bug that seemingly had no solution. Well, I guess it really didn’t have a solution…until the next version was released. That version, v6.0.6452.0, was released in November and seems to fix the problem. Before you import this updated version though, be sure to remove any exisitng DHCP management packs. Per the included documentation:
Before you import the Windows Server DHCP Management Pack, take the following actions:
- Perform a full backup of the Operations Manager 2007 database.
- Uninstall any existing DHCP management packs. You may wish to record custom overrides and rules for possible inclusion in the new DHCP management pack.
Of course, the fix for this bug isn’t documented in the release notes, but none the less it does appear to be fixed.
Comments
2 Responses to “Ops Mgr 2007 “Failed Accessing Windows Event Log””
Leave a Reply
-
Translator
Thanks for this. I had struggled trying to find out what was causing the “Failed to access windows event log error” - but loading the updated DHCP MP fixed the problem.
Glad it was helpful, this error frustrated me as well until I found that.