Event ID 2202 — DNS Server Configuration

Event ID 2202 — DNS Server Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

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.

 

Event Details

Product: Windows Operating System
ID: 2202
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_REGISTRY_WRITE_FAILED
Message: The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size for the server registry has been reached. The DNS server will not be able to save server or zone configuration parameters to in the registry unless the problem is fixed.

Resolve
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.

Verify

To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly.

To verify DNS configuration settings:

  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, double-click Roles, double-click DNS Server, and then double-click DNS.
  3. Right-click the DNS server, and then click Properties.
  4. Review the settings on each tab, and verify that they contain the intended values.
  5. Expand the DNS server.
  6. Expand a zone folder, right-click a zone, and then click Properties.
  7. Review the settings on each tab, and verify that they contain the intended values.
  8. Repeat steps 6 and 7 for each zone.

To verify that DNS client computers can resolve names properly:

  1. On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER.

If the client can resolve the name, the ping command responds with the following message:

Pinging
hostname [ip_address]

Note: The name resolution is successful even if the ping command reports that the destination is unreachable.

If the client cannot resolve the name, the ping command responds with the following message:

Ping request could not find host
hostname

Related Management Information

DNS Server Configuration

DNS Infrastructure

Related:

Event ID 2202 — Performance Counter Status

Event ID 2202 — Performance Counter Status

Updated: August 5, 2011

Applies To: Windows Server 2008 R2

Performance Counters are collected and used by services and applications. If they are installed incorrectly or with improper permissions, or if required files are not enabled on the system, those services or applications cannot collect or interpret the data.

Event Details

Product: Windows Operating System
ID: 2202
Source: Microsoft-Windows-PerfCtrs
Version: 6.1
Symbolic Name: TDI_PROVIDER_STATS_FREED
Message: Successfully released the Provider Stats data block.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Performance Counter Status

Management Infrastructure

Related:

A fatal MTA database server error was encountered. The object reservation count for object has been decremented below zero. [ ] (16)

Details
Product: Exchange
Event ID: 2202
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: A fatal MTA database server error was encountered. The object reservation count for object <object name> has been decremented below zero. [<value> <value> <value> <value>] (16)
   
Explanation

The message transfer agent (MTA) encountered an internal processing error while processing a message or report object. This indicates a logic error or database integrity failure. The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full. The MTA DAT files may be corrupt.

   
User Action

If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk. Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service.

If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt. If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out.

Contact Microsoft Product Support Services for assistance.

Related:

A fatal MTA database server error was encountered. The object reservation count for object {object name} has been decremented below zero. [{value}{value}{value}{value}] (16)

Details
Product: Exchange
Event ID: 2202
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA02202
Message: A fatal MTA database server error was encountered. The object reservation count for object {object name} has been decremented below zero. [{value}{value}{value}{value}] (16)
   
Explanation
The message transfer agent encountered an internal processing error while processing a message or report object. This indicates a logic error or database integrity failure.
   
User Action
To help Microsoft Product Support Services track down the problem, create log files. For more information, see Knowledge Base articles Q163032 and Q168906. To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA and set the logging level of the Interoperability and Interface categories to Maximum. To create Bf*.log files, set the logging level of the APDU and X.400 Service categories to Maximum.Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services.You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance.

Related: