Windows 8

  1. The DNS server encountered error %1 attempting to load zone %2 from Active Directory. The DNS server will attempt to load ...
  2. The DNS server encountered error %1 building the zone list from Active Directory. The DNS server will sleep for %2 seconds ...
  3. The DNS server encountered error {0} attempting to load zone {1} from Active Directory. The DNS server will attempt to load ...
  4. The DNS server encountered error {0} building the zone list from Active Directory. The DNS server will sleep for {1} seconds ...
  5. The DNS server encountered invalid class token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  6. The DNS server encountered invalid class token "{0}" in zone file {1} at line {2}. Although the DNS server continues to load, ...
  7. The DNS server encountered invalid domain name "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  8. The DNS server encountered invalid domain name "{0}" in zone file {1} at line {2}. Although the DNS server continues to load, ...
  9. The DNS server encountered invalid or corrupted forwarder parameters in registry data. To fix the forwarders: - connect to ...
  10. The DNS server encountered invalid or corrupted forwarder parameters in registry data. To fix the forwarders: - connect to ...
  11. The DNS server encountered invalid token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring ...
  12. The DNS server encountered invalid token "{0}" in zone file {1} at line {2}. Although the DNS server continues to load, ignoring ...
  13. The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions: ...
  14. The DNS server encountered invalid WINS record in file {0}, line {1}. WINS records are subject to the following conditions: ...
  15. The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored. ...
  16. The DNS server encountered the directive '{0}' in file {1} at line {2}. The directive is not yet supported and was ignored. ...
  17. The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
  18. The DNS server encountered the port "{0}" specified for the well known service (WKS) resource record (RR) in zone file {1} ...
  19. The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
  20. The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
  21. The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
  22. The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
  23. The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
  24. The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
  25. The DNS server has completed a scavenging cycle: Visited Zones = %1, Visited Nodes = %2, Scavenged Nodes = %3, Scavenged ...
  26. The DNS server has completed a scavenging cycle: Visited Zones = {0}, Visited Nodes = {1}, Scavenged Nodes = {2}, Scavenged ...
  27. The DNS server has completed background loading of zone %1. The zone is now available for updates and zone transfers if allowed ...
  28. The DNS server has completed background loading of zone {0}. The zone is now available for updates and zone transfers if ...
  29. The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
  30. The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
  31. The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...
  32. The DNS server has detected that for the primary zone {0} its has no zone file name stored in registry data. You can either ...
  33. 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 ...
  34. The DNS server has detected that the application directory partition %1 has finished replicating onto this domain controller. ...
  35. The DNS server has detected that the application directory partition %1 is replicating onto this domain controller. DNS data ...
  36. The DNS server has detected that the application directory partition {0} has finished replicating onto this domain controller. ...
  37. The DNS server has detected that the application directory partition {0} is replicating onto this domain controller. DNS ...
  38. The DNS server has detected that the secondary zone %1 has no master IP addresses in registry data. Secondary zones require ...
  39. The DNS server has detected that the secondary zone {0} has no master IP addresses in registry data. Secondary zones require ...
  40. The DNS server has detected that the zone %1 has a missing or corrupted zone type in registry data. To correct the problem, ...
  41. The DNS server has detected that the zone %1 has invalid or corrupted registry data. To correct the problem, you can delete ...
  42. The DNS server has detected that the zone {0} has a missing or corrupted zone type in registry data. To correct the problem, ...
  43. The DNS server has detected that the zone {0} has invalid or corrupted registry data. To correct the problem, you can delete ...
  44. The DNS server has detected that zone signing parameters for zone %1 have been changed. The zone will be re-signed in %2 ...
  45. The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning ...
  46. The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning ...
  47. The DNS server has finished the background loading and signing of zones. All zones are now available for DNS updates and ...
  48. The DNS server has finished the background loading of zones. All zones are now available for DNS updates and zone transfers, ...
  49. The DNS server has invalid or corrupted registry parameter %1. To correct the problem, you can delete the applicable registry ...
  50. The DNS server has invalid or corrupted registry parameter {0}. To correct the problem, you can delete the applicable registry ...
  51. The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the %1 directory partition. ...
  52. The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the {0} directory partition. ...
  53. The DNS server has successfully assumed Key Master responsibilities for zone %1. The Key Master role was transferred to this ...
  54. The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were ...
  55. The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were ...
  56. The DNS server is being contacted to retrieve the zone information. Depending upon the load on the DNS Server, there may ...
  57. The DNS server is experiencing high SOA query load. This may be caused by a large number of local client machines performing ...
  58. The DNS server is experiencing high SOA query load. This may be caused by a large number of local client machines performing ...
  59. The DNS server is ignoring an invalid resource record in zone file %1 at line %2. See the previously logged event for a description ...
  60. The DNS server is ignoring an invalid resource record in zone file {0} at line {1}. See the previously logged event for a ...
  61. The DNS server is not root authoritative and no root hints were specified in the cache.dns file. Where the server is not ...
  62. The DNS server is not root authoritative and no root hints were specified in the cache.dns file. Where the server is not ...
  63. The DNS server is now booting from the registry or directory. The existing server boot file will no longer be read by the ...
  64. The DNS server is now booting from the registry or directory. The existing server boot file will no longer be read by the ...
  65. The DNS server is now starting to load zone %1 in the background. While the zone is being loaded all DNS updates and zone ...
  66. The DNS server is now starting to load zone {0} in the background. While the zone is being loaded all DNS updates and zone ...
  67. The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the ...
  68. The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the ...
  69. The DNS server list is empty. The local IP address will be configured as the primary DNS server address because Microsoft ...
  70. The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. ...
  71. The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. ...
  72. The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server ...
  73. The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server ...
  74. The DNS server properties view enables service availability monitoring for DNS servers managed by IPAM. You can track service ...
  75. The DNS server received a bad DNS query from %1. The query was rejected or ignored. The event data contains the DNS packet. ...