Share via

Failed Accessing Windows Event Log Microsoft-Windows-Dhcp-Server

  • Article

Failed Accessing Windows Event Log Microsoft-Windows-Dhcp-Server is affecting the Agent Health State (Warning) for non-DHCP 2008 R2 computers

Alert Description:

The Windows Event Log Provider is still unable to open the Microsoft-Windows-Dhcp-Server/Operational event log on computer 'ServerName.Domain'.
The Provider has been unable to open the Microsoft-Windows-Dhcp-Server/Operational event log for 5760 seconds.

Most recent error details: The system cannot find the file specified.

 

One or more workflows were affected by this.

Workflow name: Microsoft.Windows.2008R2.DHCP.Server.Monitor.ActivityLogging

Instance name: ServerName.Domain

Instance ID: {1C306FEA-3578-5DBE-DDCA-705B9393F80E}

Management group: ManagemenGroupName

 

Cause:

This is a incorrct discovey, the affected servers are not Windows Server 2008 R2 computers, mostly (in the cases I faced) Windows Server 2003 Computers,

 

Resolution:

Disable the Windows Server 2008 R2 DHCP Descovery for a group (Windows Server 2003 Computer Group)

  1. Open the Operations Console | Monitoring 
  2. Management Pack Objects
  3. Object Discoveries
  4. Find "Microsoft.Windows.2008R2.DHCP.Server.Discovery"
  5. Right click the discovery Override for a group "Windows Server 2003 Computer Group" - Enabled false
  6. From Operations Manager shell >> Remove-DisabledMonitoringObject

Couple of minutes and the warnings will disappear, you might need to restart the HealthService on the affected agents..

Comments

  • Anonymous
    January 01, 2003
    Hi Ernie, In the cases I faced the DHCP 2003/2008 was already imported, and the DHCP 2008 R2 was imported seperate.. so, I have DHCP 2003 view, DCHP 2008 and one for 2008 R2 But, now the only availlable MP is the DHCP 2008 R2 which supposed to cover the 3 versions.. Regards, Mazen

  • Anonymous
    March 11, 2012
    Hello Mazen Thanks for posting this informaiton, the other I see (apart from this one) with the MP installed was there was only one MP named for Windows 2008, this then created a View with 2008R2 in the name. my WIndows 2003 DHCP Servers show up under this view, basically very confusing for other admins (as the class defintion/view is all over the place in this MP). For now I have removed the MP, and created a few custom rules. Did you get the same issue with the View name? if so did you export, change then reimport the MP? I believe you can do this with seal MP but never tired it myself yet. Thanls Ernie