Windows 8.1
- 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 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 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 "@" token "{0}" in zone file {1} at line {2}. Although the DNS server continues to ...
- 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 DNS update message from {0}. 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 domain name in a packet from {0}. 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 host (A) resource record in zone file {0} at line {1}. 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 IP address "{0}" in zone file {1} at line {2}. Although the DNS server continues to ...
- 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 IPv6 address "{0}" in zone file {1} at line {2}. Although the DNS server continues ...
- 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 name server (NS) resource record in zone file {0} at line {1}. 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 preference value "{0}" in zone file {1} at line {2}. The preference must be a valid ...
- 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 response message from {0}. 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 SOA (Start Of Authority) resource record (RR) in file {0} at line {1}. 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 invalid WINS reverse lookup (WINSR) resource record (RR) in file {0} at line {1}. 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 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 boot option {0} in file {1} at line {2}. 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 or unsupported resource record (RR) type {0} in zone file {1} at line {2}. Although ...
- 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 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 unknown WINS-to-DNS mapping flag {0} in file {1} at line {2}. 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 an unsupported 'directory' directive in the server boot file {0} at line {1}. 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 domain name "{0}" 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 error {0} attempting to load zone {1} from Active Directory. The DNS server will attempt to load ...
- The DNS server encountered error {0} building the zone list from Active Directory. The DNS server will sleep for {1} 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 class token "{0}" in zone file {1} at line {2}. 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 domain name "{0}" in zone file {1} at line {2}. 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 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 token "{0}" in zone file {1} at line {2}. 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 invalid WINS record in file {0}, line {1}. WINS records are subject to the following conditions: ...
- The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored. ...
- The DNS server encountered the directive '{0}' in file {1} at line {2}. The directive is not yet supported and was ignored. ...
- The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
- The DNS server encountered the port "{0}" specified for the well known service (WKS) resource record (RR) in zone file {1} ...
- The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
- 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 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 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 a scavenging cycle: Visited Zones = {0}, Visited Nodes = {1}, Scavenged Nodes = {2}, Scavenged ...
- The DNS server has completed background loading of zone %1. The zone is now available for updates and zone transfers if allowed ...
- The DNS server has completed background loading of zone {0}. The zone is now available for updates and zone transfers if ...
- The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
- The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
- The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...
- The DNS server has detected that for the primary zone {0} its has no zone file name stored in registry data. You can either ...
- The DNS server has detected that it is no longer the Key Master for zone %1. The Key Master role has been seized or transferred ...
- The DNS server has detected that the application directory partition %1 has finished replicating onto this domain controller. ...
- The DNS server has detected that the application directory partition %1 is replicating onto this domain controller. DNS data ...