Windows Server 2008
- The DNS server could not create zone %1 specified in file %2 at line %3. Check that the zone file is located in the %SystemRoot%\System32\Dns ...
- The DNS server could not delete a registry key. The registry is likely corrupted. The DNS server will not be able to save ...
- The DNS server could not find or open boot file %1. This file should be called 'Boot' and be located in the %SystemRoot%\System32\Dns ...
- The DNS server could not find or open the root hints file, Cache.dns, in the %SystemRoot%\System32\Dns directory. Verify ...
- The DNS server could not find or open zone file %1. in the %SystemRoot%\System32\Dns directory. Verify that the zone file ...
- The DNS server could not find protocol "%1" specified for the well known service (WKS) resource record (RR) in zone file ...
- The DNS server could not find the service "%1" specified for the well known service (WKS) resource record (RR) in zone file ...
- The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service ...
- The DNS server could not listen on Transmission Control Protocol (TCP) socket for address %1. The event data is the error ...
- The DNS server could not load or initialize the plug-in DLL %1. The event data is the error code returned by the plug-in ...
- The DNS server could not load the records for the DNS name %1 found in the Active Directory integrated zone %2. A possible ...
- The DNS server could not map file %1 to memory. Either close other applications that are not in use or reboot the computer ...
- The DNS server could not open a registry key. Reinstall the DNS server if it was not able to be started. If the DNS server ...
- The DNS server could not open socket for address %1. Verify that this is a valid IP address for the server computer. If it ...
- The DNS server could not open the file %1. Check that the file exists in the %SystemRoot%\System32\Dns directory and that ...
- The DNS server could not parse an unexpected token "%1" in zone file %2 at line %3. Although the DNS server continues to ...
- The DNS server could not parse the token "%1" in zone file %2 at line %3. Although the DNS server will continue to load, ...
- The DNS server could not parse the zone file %1 at line %2. Although the DNS server continues to load, ignoring this line, ...
- The DNS server could not parse zone file %1 for zone %2. Check that the zone file is located in the %SystemRoot%\System32\Dns ...
- The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size ...
- The DNS server created an CNAME (alias) loop loading CNAME at %1. One link in CNAME loop: DNS name %2 is an alias for CNAME ...
- The DNS server created CNAME (alias) loop caching CNAME resource records (RRs). The record is ignored, since CNAME loops ...
- The DNS server detected that it is not enlisted in the replication scope of the directory partition %1. This prevents the ...
- The DNS server detected that it is not enlisted in the replication scope of the directory partition %1. This prevents the ...
- The DNS server did not detect any zones of either primary or secondary type during initialization. It will not be authoritative ...
- The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, cache.dns, ...
- The DNS server encountered a 'forwarders' directive in with no forwarding addresses in file %1 at line %2. Although the DNS ...
- The DNS server encountered a bad packet from %1. Packet processing leads beyond packet length. The event data contains the ...
- The DNS server encountered a CNAME (alias) resource record (RR) in zone file %1 at line %2 for a domain name with existing ...
- The DNS server encountered a domain name exceeding the maximum length in the packet from %1. The event data contains the ...
- The DNS server encountered a name outside of the specified zone in zone file %1 at line %2. Although the DNS server continues ...
- The DNS server encountered a name with a label whose length exceeds the maximum of 63 bytes from %1. The event data contains ...
- The DNS server encountered a packet addressed to itself on IP address %1. The packet is for the DNS name "%2". The packet ...
- The DNS server encountered a packet name exceeding the maximum label count from %1. The event data contains the DNS packet. ...
- The DNS server encountered a problem while attempting to load the zone. The transfer of zone data from the master server ...
- The DNS server encountered a problem while attempting to load the zone. The zone data may not be available in Active Directory, ...
- The DNS server encountered a problem while attempting to load the zone. The zone file may not be found, or the zone data ...
- The DNS server encountered a resource record (RR) in the zone file %1 at line %2 for a domain name with an existing CNAME ...
- The DNS server encountered a text string "%1" in zone file %2 at line %3 that exceeds the maximum permissible length. Although ...
- The DNS server encountered a token "%1" of the wrong format in zone file %2 at line %3. Although the DNS server continues ...
- The DNS server encountered a WINS reverse lookup (WINSR) resource record (RR) without a domain specified for resulting names ...
- The DNS server encountered an alias (CNAME or DNAME) resource record (RR) in zone file %1 at line %2 that forms an alias ...
- The DNS server encountered an error writing current configuration back to boot file. Verify that the current boot file contains ...
- The DNS server encountered an error writing to file. Most likely the server disk is full. Free some disk space at the server ...
- The DNS server encountered an invalid "@" token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
- The DNS server encountered an invalid DNS update message from %1. The packet was rejected. The event data contains the DNS ...
- The DNS server encountered an invalid domain name in a packet from %1. The packet will be rejected. The event data contains ...
- The DNS server encountered an invalid host (A) resource record in zone file %1 at line %2. The use of A resource records ...
- The DNS server encountered an invalid IP address "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
- The DNS server encountered an invalid IPv6 address "%1" in zone file %2 at line %3. Although the DNS server continues to ...
- The DNS server encountered an invalid name server (NS) resource record in zone file %1 at line %2. The use of NS resource ...
- The DNS server encountered an invalid preference value "%1" in zone file %2 at line %3. The preference must be a valid 16-bit ...
- The DNS server encountered an invalid response message from %1. The packet was rejected. The event data contains the DNS ...
- The DNS server encountered an invalid SOA (Start Of Authority) resource record (RR) in file %1 at line %2. An SOA record ...
- The DNS server encountered an invalid WINS reverse lookup (WINSR) resource record (RR) in file %1 at line %2. WINSR records ...
- The DNS server encountered an non-writeable or unknown resource record (RR) type when writing the zone database to file. ...
- The DNS server encountered an unknown boot option %1 in file %2 at line %3. The option is ignored. You may want to remove ...
- The DNS server encountered an unknown or unsupported resource record (RR) type %1 in zone file %2 at line %3. Although the ...
- The DNS server encountered an unknown protocol writing a well known service (WKS) resource record to the zone file. The event ...
- The DNS server encountered an unknown WINS-to-DNS mapping flag %1 in file %2 at line %3. Although the DNS server continues ...
- The DNS server encountered an unsupported 'directory' directive in the server boot file %1 at line %2. All database files ...
- The DNS server encountered domain name "%1" exceeding maximum length. Although the DNS server continues to load, ignoring ...
- The DNS server encountered error %1 attempting to load zone %2 from Active Directory. The DNS server will attempt to load ...
- The DNS server encountered error %1 building the zone list from Active Directory. The DNS server will sleep for %2 seconds ...
- The DNS server encountered invalid class token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
- The DNS server encountered invalid domain name "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
- The DNS server encountered invalid or corrupted forwarder parameters in registry data. To fix the forwarders: - connect to ...
- The DNS server encountered invalid token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring ...
- The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions: ...
- The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
- The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
- The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
- The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
- The DNS server has completed a scavenging cycle: Visited Zones = %1, Visited Nodes = %2, Scavenged Nodes = %3, Scavenged ...
- The DNS server has completed background loading of zone %1. The zone is now available for updates and zone transfers if allowed ...