Microsoft Windows Server DNS Configuration Registry Operation Failed

Microsoft.Windows.Server.DNS.Configuration.RegistryOperationFailed (Rule)

Alert generating rule for Configuration.

Knowledge Base article:

Summary

The DNS server configuration consists of the settings that determine how the DNS server will function on a network and how those settings are stored and retrieved when they are needed.

Causes

The DNS server failed to perform a registry operation.

Resolutions

Correct the registry access problem

Check the following conditions:

Ensure that the server system disk is not full or corrupted.

Ensure that the registry has not reached the maximum allowed size.

Ensure that the registry is not corrupted.

If any of these conditions exists, the DNS server cannot update configuration data in the registry until the problem is fixed.

Reload, restart, or reinstall

A zone failed to load properly. If an attempt to reload the zone is unsuccessful, restart the DNS Server service. If the DNS Server service cannot restart, reinstall the Domain Name System (DNS) server role.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

If the DNS Server service started but could not load a zone, reload the zone.

To reload a zone:

1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.

2.In the console tree, expand Roles, expand DNS Server, and then expand DNS.

3.Expand the server hosting the zone that failed to load, and then double-click the folder containing the zone.

4.Right-click the zone, and then click Reload.

If the zone still does not load, restart the DNS Server service.

To restart the DNS Server service:

1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.

2.In the console tree, expand Roles, expand DNS Server, and then expand DNS.

3.Right-click the DNS server, click All Tasks, and then click Restart.

If the DNS Server service does not start, reinstall the DNS server role:

1.On the DNS server, start Server Manager, and then click Roles.

2.In Roles Summary, click Remove roles, and then follow the instructions in the wizard to remove the DNS server role.

3.If you are required to restart the computer, after the computer restarts, start Server Manager.

4.In Roles Summary, click Add roles, and then follow the instructions in the wizard to install the DNS server role.

External

http://technet.microsoft.com/en-us/library/dd349648(v=ws.10).aspx

Element properties:

Target

Microsoft.Windows.Server.DNS.Server

Category

Alert

Enabled

True

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Remotable

True

Alert Message

Windows DNS - Configuration Registry Operation Failed

Event ID: {0}
Event Source: {1}
Event Log: {2}

Event Description: {3}

Event Log

DNS Server

Member Modules:

ID	Module Type	TypeId	RunAs
DS	DataSource	Microsoft.Windows.EventProvider	Default
Alert	WriteAction	System.Health.GenerateAlert	Default

Source Code:

<Rule ID="Microsoft.Windows.Server.DNS.Configuration.RegistryOperationFailed" Enabled="true" Target="Microsoft.Windows.Server.DNS.Server" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>DNS Server</LogName>

      <Expression>

        <Or>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">2200</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">2202</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">2203</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </Or>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.DNS.Configuration.RegistryOperationFailed.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDisplayNumber$</AlertParameter1>

        <AlertParameter2>$Data/EventSourceName$</AlertParameter2>

        <AlertParameter3>$Data/Channel$</AlertParameter3>

        <AlertParameter4>$Data/EventDescription$</AlertParameter4>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>