locked
Microsoft Windows Server DNS Monitoring v7.1.10100.0 High CPU Usage on Windows Server 2012 R2 RRS feed

  • Question

  • Hello!

    I've a big problem with this MP. When the zone monitoring is enabled (by default) the MonitoringHost.exe takes up all the CPU. I've put the zones in Maintenance mode.

    I've got this problem only with a new Windows 2012 R2 server. Other Windows Servers (2003 R2, 2008 & 2008 R2) with DNS Server Role they don't have this problem.

    Any ideas?

    Thank you!

    The configuration is:

    • SCOM 2012 R2
    • Microsoft Windows Server DNS Monitoring v7.1.10100.0 Management Pack
    • DNS Management Pack Action Account has been configured
    • "Act as proxy..." is enabled

    The monitored server config:

    • Windows Server 2012 R2 (standalone)
    • DNS Server Role installed
    • DNS Management Pack Action Account is a member of the "Administrators" group

    The only events I've are the following but I'm not sure if they're related (because of the ...DNSSEC...):

    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          8/11/2013 11:16:21
    Event ID:      11903
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NS2...
    Description:
    The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.

    Property Expression: Property[@Name='QueriesResponded']

    Property Value: Property[@Name='QueriesResponded']

    Conversion Type: DataItemElementTypeInteger(5)

    Original Error: 0x80FF005A

    One or more workflows were affected by this. 

    Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
    Instance name: <zone-name> on NS2...
    Instance ID: {4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}
    Management group: <grp-name>
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11903</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-11-08T09:16:21.000000000Z" />
        <EventRecordID>9602</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>NS2...</Computer>
        <Security />
      </System>
      <EventData>
        <Data><grp-name></Data>
        <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
        <Data><zone name> on NS2...</Data>
        <Data>{4BCB4738-1287-2E6F-E0AA-1FF8D66DDB0B}</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>DataItemElementTypeInteger(5)</Data>
        <Data>0x80FF005A</Data>
      </EventData>
    </Event>

    Friday, November 8, 2013 10:04 AM

Answers

  • Problem solved!

    It was the failing monitor above! I disabled every monitor about DNSSEC (we're not using DNSSEC on our DNS) and everything is back to normal!

    • Marked as answer by Ste7ios Friday, November 8, 2013 11:39 AM
    Friday, November 8, 2013 11:39 AM

All replies

  • Problem solved!

    It was the failing monitor above! I disabled every monitor about DNSSEC (we're not using DNSSEC on our DNS) and everything is back to normal!

    • Marked as answer by Ste7ios Friday, November 8, 2013 11:39 AM
    Friday, November 8, 2013 11:39 AM
  • Glad to see you found the solution and thanks for your sharing.

    Niki Han

    TechNet Community Support

    Thursday, November 21, 2013 8:25 AM
  • Problem solved!

    It was the failing monitor above! I disabled every monitor about DNSSEC (we're not using DNSSEC on our DNS) and everything is back to normal!

    Could you specify the DNSSEC monitors / Rules you disabled?

    Tuesday, May 27, 2014 3:06 PM
  • just search for name "DNS SEC" in overrides view
    Monday, June 16, 2014 1:43 PM
  • There is an update to the DNS management pack that was released 8/27/14. I'm importing it now.
    Wednesday, October 8, 2014 2:39 PM
  • So far, after importing the new MP, I have not had the alert be raised
    Wednesday, October 8, 2014 4:47 PM