dcdiag.exe Active Directory Domain Services / Lightweight Directory Services diagnosis utility 59f1f6d4f1ea5bc99345ef38ff47b4d7

File name:	dcdiag.exe.mui
Size:	183296 byte
MD5:	59f1f6d4f1ea5bc99345ef38ff47b4d7
SHA1:	1749049ae51500d66806f86dfa0ddc28566c54bb
SHA256:	4c8bed7ce5f3a33143899fcaa20e72c0aee6c3c0f0a8e69b0f4318ece859c8df
Operating systems:	Windows 10
Extension:	MUI
In x64:	dcdiag.exe Active Directory Domain Services / Lightweight Directory Services diagnosis utility (32-bit)

If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	English (U.S.)	English
1001	Ldap search capability attribute search failed on server %1, return value = %2!d!	Ldap search capability attribute search failed on server %1, return value = %2!d!
1002	[%1] LDAP search failed with error %2!d!,%n	[%1] LDAP search failed with error %2!d!,%n
1003	%1.currentTime = %2!ls!%n	%1.currentTime = %2!ls!%n
1004	[%1] Warning: Root DSE attribute %2!ls! is missing%n	[%1] Warning: Root DSE attribute %2!ls! is missing%n
1005	[%1] Warning: Root DSE attribute %2!ls! is has invalid value %3!ls!%n	[%1] Warning: Root DSE attribute %2!ls! is has invalid value %3!ls!%n
1006	Status is %1!d!: (unknown)	Status is %1!d!: (unknown)
1007	%1.highestCommittedUSN = %2!I64d!%n	%1.highestCommittedUSN = %2!I64d!%n
1009	%1.isSynchronized = %2!d!%n	%1.isSynchronized = %2!d!%n
1011	%1.isGlobalCatalogReady = %2!d!%n	%1.isGlobalCatalogReady = %2!d!%n
1012	[%1] LDAP connection failed with error %2!d!,%n	[%1] LDAP connection failed with error %2!d!,%n
1013	[%1] LDAP setting options failed with error %2!d!,%n	[%1] LDAP setting options failed with error %2!d!,%n
1014	[%1] LDAP bind failed with error %2!d!,%n	[%1] LDAP bind failed with error %2!d!,%n
1015	[%1] DsBindWithSpnEx() failed with error %2!d!,%n	[%1] DsBindWithSpnEx() failed with error %2!d!,%n
1016	* You must make sure there are no existing net use connections,%n you can use "net use /d %1" or "net use /d%n \\\"%n	* You must make sure there are no existing net use connections,%n you can use "net use /d %1" or "net use /d%n \\\"%n
1017	Fatal Error: Not enough memory to complete operation. %n	Fatal Error: Not enough memory to complete operation. %n
1018	Fatal Error: The network resource is already in use%n	Fatal Error: The network resource is already in use%n
1019	User credentials does not have permission to perform this operation.%nThe account used for this test must have network logon privileges%nfor the target machine's domain.%n	User credentials does not have permission to perform this operation.%nThe account used for this test must have network logon privileges%nfor the target machine's domain.%n
1020	[%1] An net use or LsaPolicy operation failed with error %2!d!, %3.%n	[%1] An net use or LsaPolicy operation failed with error %2!d!, %3.%n
1021	Could not find any Sites in the AD, %nContinue%n	Could not find any Sites in the AD, %nContinue%n
1022	* Identifying all servers.%n	* Identifying all servers.%n
1023	* Connecting to directory service on server %1.%n	* Connecting to directory service on server %1.%n
1024	[%1] Unrecoverable LDAP Error %2!ld!:%n	[%1] Unrecoverable LDAP Error %2!ld!:%n
1025	[%1] Directory Binding Error %2!ld!:%n	[%1] Directory Binding Error %2!ld!:%n
1026	This may limit some of the tests that can be performed.%n	This may limit some of the tests that can be performed.%n
1028	* Collecting site info.%n	* Collecting site info.%n
1029	Naming context %1!ws! cannot be found.%n	Naming context %1!ws! cannot be found.%n
1030	* Found %1!ld! DC(s). Testing %2!ld! of them.%n	* Found %1!ld! DC(s). Testing %2!ld! of them.%n
1031	Done gathering initial info.%n	Done gathering initial info.%n
1032	Unable to logon user %1\%2 (%3!d!).%n	Unable to logon user %1\%2 (%3!d!).%n
1033	Unable to impersonate user %1\%2 (%3!d!).%n	Unable to impersonate user %1\%2 (%3!d!).%n
1034	There is a horrible inconsistency in the directory, the server%n%1%ncould not be found in it's own directory.%n	There is a horrible inconsistency in the directory, the server%n%1%ncould not be found in it's own directory.%n
1035	Time Generated: %1!02d!/%2!02d!/%3!02d! %4!02d!:%5!02d!:%6!02d!%n	Time Generated: %1!02d!/%2!02d!/%3!02d! %4!02d!:%5!02d!:%6!02d!%n
1036	An event occurred. EventID: 0x%1!08X!%n	An event occurred. EventID: 0x%1!08X!%n
1037	Event String: %1%n	Event String: %1%n
1038	(Event String (event log = %1) could not be retrieved, error 0x%2!x!)%n	(Event String (event log = %1) could not be retrieved, error 0x%2!x!)%n
1039	FATAL ERROR: Out of Memory%n	FATAL ERROR: Out of Memory%n
1040	Error %1!d! opening %2!ws! eventlog %3:%4:%n %5%n	Error %1!d! opening %2!ws! eventlog %3:%4:%n %5%n
1041	Error %1!d! accessing %2!ws! eventlog: %3%n	Error %1!d! accessing %2!ws! eventlog: %3%n
1042	An unknown error occurred trying to read the event log:%nError(%1!d!):%2%n	An unknown error occurred trying to read the event log:%nError(%1!d!):%2%n
1043	Command Line: "dcdiag.exe	Command Line: "dcdiag.exe
1044	DcDiag: a dcdiag exception raised, handling error %1%n	DcDiag: a dcdiag exception raised, handling error %1%n
1045	DcDiag: uncaught exception raised, continuing search %n	DcDiag: uncaught exception raised, continuing search %n
1046	Testing server: %1\%2%n	Testing server: %1\%2%n
1047	Testing site: %1%n	Testing site: %1%n
1048	Running partition tests on : %1%n	Running partition tests on : %1%n
1049	Running enterprise tests on : %1%n	Running enterprise tests on : %1%n
1050	Skipping all tests, because server %1 is not responding to directory service requests.%n	Skipping all tests, because server %1 is not responding to directory service requests.%n
1051	......................... %1 passed test %2%n	......................... %1 passed test %2%n
1052	......................... %1 failed test %2%n	......................... %1 failed test %2%n
1053	Performing initial setup:%n	Performing initial setup:%n
1054	Couldn't initialize WinSock with error: %1%n	Couldn't initialize WinSock with error: %1%n
1055	Doing initial required tests%n	Doing initial required tests%n
1056	%nDoing primary tests%n	%nDoing primary tests%n
1057	No memory.%n	No memory.%n
1058	Password:	Password:
1059	User name must be prefixed by domain name.%n	User name must be prefixed by domain name.%n
1060	Password must be accompanied by user name.%n	Password must be accompanied by user name.%n
1061	The syntax of domain distinguished name %1!ws! is incorrect.%n	The syntax of domain distinguished name %1!ws! is incorrect.%n
1062	Translation failed with error: %1.%n	Translation failed with error: %1.%n
1063	A Directory Server holding %1!ws! could not be located.%n	A Directory Server holding %1!ws! could not be located.%n
1064	The error is %1%n	The error is %1%n
1065	Try specifying a server with the /s option.%n	Try specifying a server with the /s option.%n
1066	* The home server picked is %1!ws! in site %ws.%n	* The home server picked is %1!ws! in site %ws.%n
1067	Memory allocation failure%n	Memory allocation failure%n
1068	Check syntax and validity of specified name.%n	Check syntax and validity of specified name.%n
1069	The syntax of DNS domain name %1!ws! is incorrect.%n	The syntax of DNS domain name %1!ws! is incorrect.%n
1070	The distinguished name of the domain is %1!ws!.%n	The distinguished name of the domain is %1!ws!.%n
1071	The specified naming context is incorrect and will be ignored.%n	The specified naming context is incorrect and will be ignored.%n
1072	Starting test: %1%n	Starting test: %1%n
1073	Test omitted by user request: %1%n	Test omitted by user request: %1%n
1075	Password too long!%n	Password too long!%n
1076	A domain named %1!ws! could not be located.%n	A domain named %1!ws! could not be located.%n
1077	The domain name is %1!ws!.%n	The domain name is %1!ws!.%n
1078	* Identifying all NC cross-refs.%n	* Identifying all NC cross-refs.%n
1079	%tError, Server %1 has no domain partition!%n	%tError, Server %1 has no domain partition!%n
1080	RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.%n	RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.%n
1081	Couldn't get RPC Extended Error Info: %1!d!%n	Couldn't get RPC Extended Error Info: %1!d!%n
1082	Printing RPC Extended Error Info:%n	Printing RPC Extended Error Info:%n
1083	Error Record %1!d!, ProcessID is %2!d!	Error Record %1!d!, ProcessID is %2!d!
1084	(DcDiag)	(DcDiag)
1085	Computer Name is %1%n	Computer Name is %1%n
1086	System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d!%n	System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d!%n
1087	Generating component is %1!d! (this application)	Generating component is %1!d! (this application)
1088	Generating component is %1!d! (RPC runtime)	Generating component is %1!d! (RPC runtime)
1089	Generating component is %1!d! (security provider)	Generating component is %1!d! (security provider)
1090	Generating component is %1!d! (NPFS file system)	Generating component is %1!d! (NPFS file system)
1091	Generating component is %1!d! (redirector)	Generating component is %1!d! (redirector)
1092	Generating component is %1!d! (named pipe system)	Generating component is %1!d! (named pipe system)
1093	Generating component is %1!d! (IO system or driver)	Generating component is %1!d! (IO system or driver)
1094	Generating component is %1!d! (winsock)	Generating component is %1!d! (winsock)
1095	Generating component is %1!d! (authorization API)	Generating component is %1!d! (authorization API)
1096	Generating component is %1!d! (LPC facility)	Generating component is %1!d! (LPC facility)
1097	Generating component is %1!d! (unknown)	Generating component is %1!d! (unknown)
1098	Status is %1!d! (no error)	Status is %1!d! (no error)
1099	Status is %1!d! %2	Status is %1!d! %2
1100	Detection location is %1!d!%n	Detection location is %1!d!%n
1101	Flags is %1!d!%n	Flags is %1!d!%n
1102	1: previous EE info records are missing%n	1: previous EE info records are missing%n
1103	2: next EE info records are missing%n	2: next EE info records are missing%n
1104	4: use file time%n	4: use file time%n
1105	NumberOfParameters is %1!d!%n	NumberOfParameters is %1!d!%n
1106	Ansi string: %1%n	Ansi string: %1%n
1107	Unicode string: %1%n	Unicode string: %1%n
1108	Long val: %1!d!%n	Long val: %1!d!%n
1109	Short val: %1!d!%n	Short val: %1!d!%n
1110	Pointer val: %1!d!%n	Pointer val: %1!d!%n
1111	Truncated%n	Truncated%n
1112	Invalid type: %1!d!%n	Invalid type: %1!d!%n
1113	Couldn't finish RPC extended error enumeration: %1!d!%n	Couldn't finish RPC extended error enumeration: %1!d!%n
1116	%1!ws!(%2!ws!, %3!ws!): mapping NULL/no-error into NULL/ERROR_DS_GENERIC_ERROR%n	%1!ws!(%2!ws!, %3!ws!): mapping NULL/no-error into NULL/ERROR_DS_GENERIC_ERROR%n
1117	%1!ws!(%2!ws!, %3!ws!, %4!d! remaining): waiting for object	%1!ws!(%2!ws!, %3!ws!, %4!d! remaining): waiting for object
1122	%1!ws! not found%n	%1!ws! not found%n
1123	Test skipped for RODC: %1%n	Test skipped for RODC: %1%n
1178	Attempt to obtain DNS name server info failed with error %1!d!%n	Attempt to obtain DNS name server info failed with error %1!d!%n
1179	%nName server IP address: %1%n	%nName server IP address: %1%n
1180	%nSRV name: %1, A addr: %2!d!.%3!d!.%4!d!.%5!d!.%6!d!%n	%nSRV name: %1, A addr: %2!d!.%3!d!.%4!d!.%5!d!.%6!d!%n
1181	%nSOA query returned record type %1!d!%n	%nSOA query returned record type %1!d!%n
1182	%nA record, name: %1, IP address: %2!d!.%3!d!.%4!d!.%5!d!.%6!d!%n	%nA record, name: %1, IP address: %2!d!.%3!d!.%4!d!.%5!d!.%6!d!%n
1183	%nSOA name: %1, zone primary server: %2%n	%nSOA name: %1, zone primary server: %2%n
1184	%nNS query returned record type %1!d!%n	%nNS query returned record type %1!d!%n
1185	%nNS name: %1, host: %2%n	%nNS name: %1, host: %2%n
1186	Reading the size of the adapter address data failed with error %1!d!%n	Reading the size of the adapter address data failed with error %1!d!%n
1189	%nServer IP address: %1!d!.%2!d!.%3!d!.%4!d! (0x%5!08x!)%n	%nServer IP address: %1!d!.%2!d!.%3!d!.%4!d! (0x%5!08x!)%n
1190	Opening the service controller failed with error %1!d!%n	Opening the service controller failed with error %1!d!%n
1191	%1!ws!: %2!ws!: %3!ws! missing %4!ws!%n	%1!ws!: %2!ws!: %3!ws! missing %4!ws!%n
1192	%1!ws!: %2!ws!: %3!ws! names don't match (%4!ws! %5!ws! != %6!ws! %7!ws!)%n	%1!ws!: %2!ws!: %3!ws! names don't match (%4!ws! %5!ws! != %6!ws! %7!ws!)%n
1193	DsRole: %1!ws!: %2!ws! modes don't match (DsRole %3!d! != DsGet %4!d!)%n	DsRole: %1!ws!: %2!ws! modes don't match (DsRole %3!d! != DsGet %4!d!)%n
1199	DsRole: %1!ws!: Primary Dc not writable (DsRole %2!x! != DsGet %3!x!)%n	DsRole: %1!ws!: Primary Dc not writable (DsRole %2!x! != DsGet %3!x!)%n
1200	DsRole: %1!ws!: GUID's don't match%n	DsRole: %1!ws!: GUID's don't match%n
1201	%1!ws!(%2!ws!, %3!ws!): %4!d! secrets not underwritten%n	%1!ws!(%2!ws!, %3!ws!): %4!d! secrets not underwritten%n
1202	%1!ws!(%2!ws!, %4!ws!, %5!d! remaining): waiting for %6!d! overwrites%n	%1!ws!(%2!ws!, %4!ws!, %5!d! remaining): waiting for %6!d! overwrites%n
1204	%1!ws!(%2!ws!, %3!ws!): %4!d! secrets not overwritten%n	%1!ws!(%2!ws!, %3!ws!): %4!d! secrets not overwritten%n
1205	Domain behavior version (%1!d!) is not w2k3 or greater (%2!d!)%n	Domain behavior version (%1!d!) is not w2k3 or greater (%2!d!)%n
1206	Test results for domain controllers:%n	Test results for domain controllers:%n
1207	DC: %1!ws!%n	DC: %1!ws!%n
1208	Domain: %1!ws!%n%n	Domain: %1!ws!%n%n
1209	Authentication test: Successfully completed	Authentication test: Successfully completed
1210	Total query time:%1!ws!. Total RPC connection time:%2!ws!%n	Total query time:%1!ws!. Total RPC connection time:%2!ws!%n
1211	Total WMI connection time:%1!ws! Total Netuse connection time:%2!ws!%n	Total WMI connection time:%1!ws! Total Netuse connection time:%2!ws!%n
1212	Error: No LDAP connectivity	Error: No LDAP connectivity
1213	Error: No DS RPC connectivity	Error: No DS RPC connectivity
1214	The OS %1!ws! is supported.%n	The OS %1!ws! is supported.%n
1215	Error: The OS %1!ws! is not supported.%n	Error: The OS %1!ws! is not supported.%n
1216	%1!ws! service is running%n	%1!ws! service is running%n
1217	DC is a DNS server%n	DC is a DNS server%n
1218	DC is not a DNS server%n	DC is not a DNS server%n
1219	Network adapters information:%n	Network adapters information:%n
1220	Adapter %1!ws!:%n	Adapter %1!ws!:%n
1221	IP Address is static	IP Address is static
1222	Warning IP address is dynamic (can be a misconfiguration)	Warning IP address is dynamic (can be a misconfiguration)
1223	Warning: Adapter %1!ws! has dynamic IP address (can be a misconfiguration)%n	Warning: Adapter %1!ws! has dynamic IP address (can be a misconfiguration)%n
1224	DNS servers:%n	DNS servers:%n
1225	Warning:	Warning:
1226	Warning: adapter %1!ws! has invalid DNS server: %2!ws! (%3!ws!)%n	Warning: adapter %1!ws! has invalid DNS server: %2!ws! (%3!ws!)%n
1227	Warning: The Active Directory zone on this DC/DNS server was not found (probably a misconfiguration)	Warning: The Active Directory zone on this DC/DNS server was not found (probably a misconfiguration)
1228	Warning: Root zone on this DC/DNS server was found primary (could be a misconfiguration)	Warning: Root zone on this DC/DNS server was found primary (could be a misconfiguration)
1229	Warning: Root zone on this DC/DNS server was found secondary (could be a misconfiguration)	Warning: Root zone on this DC/DNS server was found secondary (could be a misconfiguration)
1230	Error: Both root hints and forwarders are not configured or broken. Please make sure at least one of them works.%n	Error: Both root hints and forwarders are not configured or broken. Please make sure at least one of them works.%n
1231	Error: Root hints list has invalid root hint server: %1!ws! (%2!ws!)%n	Error: Root hints list has invalid root hint server: %1!ws! (%2!ws!)%n
1232	Error: %1!ws!%n	Error: %1!ws!%n
1233	Error: DNS server: %1!ws! IP:%2!ws! [%3!ws!]%n	Error: DNS server: %1!ws! IP:%2!ws! [%3!ws!]%n
1234	Error: DNS server: %1!ws! IP: [%2!ws!]%n	Error: DNS server: %1!ws! IP: [%2!ws!]%n
1235	Warning: Dynamic update is enabled on the zone but not secure %1!ws!%n	Warning: Dynamic update is enabled on the zone but not secure %1!ws!%n
1236	Network Adapter %1!ws!:%n	Network Adapter %1!ws!:%n
1237	has been configured to prevent registration of this Record.Unable to reead registry/group policy)%n%n	has been configured to prevent registration of this Record.Unable to reead registry/group policy)%n%n
1238	(Ignore the error if DNSAvoidRegisterRecord registry key or its Group Policy%n	(Ignore the error if DNSAvoidRegisterRecord registry key or its Group Policy%n
1239	Error: Record registrations cannot be found for all the network adapters%n	Error: Record registrations cannot be found for all the network adapters%n
1240	Warning: Record Registrations not found in some network adapters%n	Warning: Record Registrations not found in some network adapters%n
1241	Error: Internet name %1!ws! cannot be resolved%n	Error: Internet name %1!ws! cannot be resolved%n
1242	Error:%1!ws! IP: Status:%2!ws!%n	Error:%1!ws! IP: Status:%2!ws!%n
1243	Error: Dynamic update is not enabled on the zone %1!ws!%n	Error: Dynamic update is not enabled on the zone %1!ws!%n
1244	Summary of DNS test results:%n	Summary of DNS test results:%n
1245	_________________________________________________________________	_________________________________________________________________
1246	Domain: %1!ws!%n	Domain: %1!ws!%n
1247	Enterprise DNS infrastructure test results:%n%n	Enterprise DNS infrastructure test results:%n%n
1248	For parent domain %1!ws! and subordinate domain %2!ws!:%n	For parent domain %1!ws! and subordinate domain %2!ws!:%n
1249	Warning: Neither forwarders nor root hints are configured from subordinate domain to parent domain%n	Warning: Neither forwarders nor root hints are configured from subordinate domain to parent domain%n
1250	Error: Delegation is not configured on the parent domain%n	Error: Delegation is not configured on the parent domain%n
1251	Error: Delegation is present but the glue record is missing for the following name server(s): %1	Error: Delegation is present but the glue record is missing for the following name server(s): %1
1254	Error: %1!ws! is wrongly configured from parent domain to subordinate domain%n	Error: %1!ws! is wrongly configured from parent domain to subordinate domain%n
1255	Auth Basc Forw Del Dyn RReg Ext	Auth Basc Forw Del Dyn RReg Ext
1256	Parent domain's %1!ws! list contains subordinate domain's DNS server IP: %2!ws!%n	Parent domain's %1!ws! list contains subordinate domain's DNS server IP: %2!ws!%n
1257	Error: %1!ws! are configured from subordinate to parent domain but some of them failed DNS server tests%n	Error: %1!ws! are configured from subordinate to parent domain but some of them failed DNS server tests%n
1258	(See DNS servers section for error details)%n	(See DNS servers section for error details)%n
1259	Summary of test results for DNS servers used by the above domain controllers:%n%n	Summary of test results for DNS servers used by the above domain controllers:%n%n
1260	DNS server: %1!ws! (%2!ws!)%n	DNS server: %1!ws! (%2!ws!)%n
1261	All tests passed on this DNS server%n	All tests passed on this DNS server%n
1262	%1!d! test failure on this DNS server%n	%1!d! test failure on this DNS server%n
1264	Total query time:%1!ws!, Total WMI connection time:%2!ws!%n	Total query time:%1!ws!, Total WMI connection time:%2!ws!%n
1265	This is not a valid DNS server. %1!ws!%n	This is not a valid DNS server. %1!ws!%n
1266	(%1!ws! must be configured from subordinate domain to parent Domain)%n	(%1!ws! must be configured from subordinate domain to parent Domain)%n
1267	Total Time taken to test all the DCs:%1!ws!%n	Total Time taken to test all the DCs:%1!ws!%n
1268	Warning: Attempting to connect to the GC port of %1 which our information dictates isn't currently a GC. Attempting anyway...%n	Warning: Attempting to connect to the GC port of %1 which our information dictates isn't currently a GC. Attempting anyway...%n
1269	[%1] LDAP bind failed with error %2!d!. %3%n	[%1] LDAP bind failed with error %2!d!. %3%n
1270	* The current DC is not in the domain controller's OU%n	* The current DC is not in the domain controller's OU%n
1271	The account %1 is disabled. It cannot replicate.%n	The account %1 is disabled. It cannot replicate.%n
1272	Error, cannot format userAccountControl string! (%1!d!)%n	Error, cannot format userAccountControl string! (%1!d!)%n
1273	Warning: Attribute userAccountControl of %1 is: %2%n	Warning: Attribute userAccountControl of %1 is: %2%n
1274	Typical setting for a DC is %1%n	Typical setting for a DC is %1%n
1275	ldap_search_sW failed with %1!d!: %2%n	ldap_search_sW failed with %1!d!: %2%n
1276	* %1 Server Reference is incorrect! Should be %2, and is %3.%n	* %1 Server Reference is incorrect! Should be %2, and is %3.%n
1277	Could not get NetBIOSDomainName%n	Could not get NetBIOSDomainName%n
1278	Failed with %1!d!: %2%nCan not test for LDAP SPN%n	Failed with %1!d!: %2%nCan not test for LDAP SPN%n
1279	Failed can not test for LDAP SPN%n	Failed can not test for LDAP SPN%n
1280	Failed with %1!d!: %2%nCan not test for HOST SPN%n	Failed with %1!d!: %2%nCan not test for HOST SPN%n
1281	Failed can not test for HOST SPN%n	Failed can not test for HOST SPN%n
1282	Failed with %1!d!: %2%nCan not test for replication SPN%n	Failed with %1!d!: %2%nCan not test for replication SPN%n
1283	Can not test for replication SPN%n	Can not test for replication SPN%n
1284	Failed with %1!d!: %2%nCan not test for GC SPN%n	Failed with %1!d!: %2%nCan not test for GC SPN%n
1285	Failed can not test for GC SPN%n	Failed can not test for GC SPN%n
1286	Error: %1!d!: [%2]. Could not perform DsBind() with [%3]. Some SPN's Will not be checked%n	Error: %1!d!: [%2]. Could not perform DsBind() with [%3]. Some SPN's Will not be checked%n
1287	Failed to fix computer account object %1 by writing missing replication spn %2 : error %3%n	Failed to fix computer account object %1 by writing missing replication spn %2 : error %3%n
1288	* Missing SPN :%1%n	* Missing SPN :%1%n
1289	Could not open pipe with [%1]:failed with %2!d!: %3%n	Could not open pipe with [%1]:failed with %2!d!: %3%n
1290	Could not open Lsa Policy%n	Could not open Lsa Policy%n
1291	Failed with %1!d!: %2%n	Failed with %1!d!: %2%n
1292	The account %1 is locked out. It cannot replicate.%n	The account %1 is locked out. It cannot replicate.%n
1293	The account %1 is not trusted for delegation. It cannot replicate.%n	The account %1 is not trusted for delegation. It cannot replicate.%n
1294	The account %1 is not a DC account. It cannot replicate.%n	The account %1 is not a DC account. It cannot replicate.%n
1295	This may be affecting replication?%n	This may be affecting replication?%n
1296	* %1 Server Reference is incorrect%n	* %1 Server Reference is incorrect%n
1297	ldap_search_sW of RootDSE for serverName failed with %1!d!: %2%n	ldap_search_sW of RootDSE for serverName failed with %1!d!: %2%n
1298	ldap_search_sW of RootDSE for default NC failed with %1!d!: %2%n	ldap_search_sW of RootDSE for default NC failed with %1!d!: %2%n
1299	ldap_search_sW subtree of %1 for sam account failed with %2!d!: %3%n	ldap_search_sW subtree of %1 for sam account failed with %2!d!: %3%n
1300	ldap_search_sW of RootDSE for schemaNC failed with %1!d!: %2%n	ldap_search_sW of RootDSE for schemaNC failed with %1!d!: %2%n
1301	** Did not run Outbound Secure Channels test because /testdomain: was not entered%n	** Did not run Outbound Secure Channels test because /testdomain: was not entered%n
1302	Could not Query Trusted Domain [%1]: error 0x%2!x! "%3"%n	Could not Query Trusted Domain [%1]: error 0x%2!x! "%3"%n
1303	Could not open Lsa Policy to [%1]: error 0x%2!x! "%3"%n	Could not open Lsa Policy to [%1]: error 0x%2!x! "%3"%n
1304	Could not open Remote ipc to [%1]: error 0x%2!x! "%3"%n	Could not open Remote ipc to [%1]: error 0x%2!x! "%3"%n
1305	Could not Check secure channel from %1 to %2: error 0x%3!x! "%4"%nRPC Extended error message:%n	Could not Check secure channel from %1 to %2: error 0x%3!x! "%4"%nRPC Extended error message:%n
1306	Error with Secure channel from [%1] to [%2]: error 0x%3!x! "%4"%n	Error with Secure channel from [%1] to [%2]: error 0x%3!x! "%4"%n
1307	[%1] Does not have UF_INTERDOMAIN_TRUST_ACCOUNT set on downlevel trust object for [%2]%n	[%1] Does not have UF_INTERDOMAIN_TRUST_ACCOUNT set on downlevel trust object for [%2]%n
1308	[%1] Does not have downlevel trust object for [%2]%n	[%1] Does not have downlevel trust object for [%2]%n
1309	Could not find objectCatagory for Trusted Domains	Could not find objectCatagory for Trusted Domains
1310	[%1] Does not have uplevel trust object for [%2]%n	[%1] Does not have uplevel trust object for [%2]%n
1311	ldap_search_sW of %1 for rid manager reference failed with %2!d!: %3%n	ldap_search_sW of %1 for rid manager reference failed with %2!d!: %3%n
1312	ldap_search_sW of %1 for FSMO Role Owner failed with %2!d!: %3%n	ldap_search_sW of %1 for FSMO Role Owner failed with %2!d!: %3%n
1313	The DS has corrupt data: %1 value is not valid%n	The DS has corrupt data: %1 value is not valid%n
1314	Warning: attribute FSMORoleOwner missing from %1%n	Warning: attribute FSMORoleOwner missing from %1%n
1315	Warning: FSMO Role Owner is deleted.%n	Warning: FSMO Role Owner is deleted.%n
1316	ldap_search_sW of %1 for hostname failed with %2!d!: %3%n	ldap_search_sW of %1 for hostname failed with %2!d!: %3%n
1317	Could not get Rid set Reference :failed with %1!d!: %2%n	Could not get Rid set Reference :failed with %1!d!: %2%n
1318	ldap_search_sW of %1 for rid set references failed with %2!d!: %3%n	ldap_search_sW of %1 for rid set references failed with %2!d!: %3%n
1319	No rids allocated -- please check eventlog.%n	No rids allocated -- please check eventlog.%n
1320	Warning: rid set reference is deleted.%n	Warning: rid set reference is deleted.%n
1321	Warning: attribute rIdSetReferences missing from %1%n	Warning: attribute rIdSetReferences missing from %1%n
1322	Warning: attribute rIdSetReferences present on %1%n	Warning: attribute rIdSetReferences present on %1%n
1323	ldap_search_sW of %1 for rid info failed with %2!d!: %3%n	ldap_search_sW of %1 for rid info failed with %2!d!: %3%n
1324	Could not open %1 Service on %2, error 0x%3!x! "%4"%n	Could not open %1 Service on %2, error 0x%3!x! "%4"%n
1325	Could not query %1 Service on %2, error 0x%3!x! "%4"%n	Could not query %1 Service on %2, error 0x%3!x! "%4"%n
1326	%1 Service is stopped on [%2]%n	%1 Service is stopped on [%2]%n
1327	%1 Service is paused on [%2]%n	%1 Service is paused on [%2]%n
1328	%nError: %1 Service is hung starting on [%2]%n	%nError: %1 Service is hung starting on [%2]%n
1329	%nError: %1 Service is hung pending continue on [%2]%n	%nError: %1 Service is hung pending continue on [%2]%n
1330	%nError: %1 Service is hung pending stop on [%2]%n	%nError: %1 Service is hung pending stop on [%2]%n
1331	%nError: %1 Service is hung pending pause on [%2]%n	%nError: %1 Service is hung pending pause on [%2]%n
1332	Error: %1 Service is in an unknown state [%2]%n	Error: %1 Service is in an unknown state [%2]%n
1333	Could not open Service Control Manager on %1, error 0x%2!x! "%3"%n	Could not open Service Control Manager on %1, error 0x%2!x! "%3"%n
1335	Error during resolution of hostname %1 through %2 stack.%n*** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. Hostname resolution error 0x%3!x! "%4"%n	Error during resolution of hostname %1 through %2 stack.%n*** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. Hostname resolution error 0x%3!x! "%4"%n
1336	Warning during resolution of hostname %1 through %2 stack.%n*** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS.%n	Warning during resolution of hostname %1 through %2 stack.%n*** Warning: could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS.%n
1338	Fatal Error: Not enough memory to complete operation.%n	Fatal Error: Not enough memory to complete operation.%n
1339	LDAP couldn't retrieve the root object from the server %1.%n	LDAP couldn't retrieve the root object from the server %1.%n
1341	LDAP couldn't retrieve the root object from the server %1, error %2.%n	LDAP couldn't retrieve the root object from the server %1, error %2.%n
1342	LDAP search error: %1.%n	LDAP search error: %1.%n
1343	Server %1 resolved to these IP addresses: %2, but none of the addresses could be reached (pinged). Please check the network.%nError: 0x%3!x! "%4"%n	Server %1 resolved to these IP addresses: %2, but none of the addresses could be reached (pinged). Please check the network.%nError: 0x%3!x! "%4"%n
1345	This error more often than not means the local machine is disconnected from the network.%n	This error more often than not means the local machine is disconnected from the network.%n
1346	This error more often means that the targeted server is shutdown or disconnected from the network.%n	This error more often means that the targeted server is shutdown or disconnected from the network.%n
1347	The host %1 could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc.%n	The host %1 could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc.%n
1348	An error that is usually temporary occurred during DNS host lookup. Please try again later.%n	An error that is usually temporary occurred during DNS host lookup. Please try again later.%n
1349	An error occurred during DNS host lookup, that the program could not recover from.%n	An error occurred during DNS host lookup, that the program could not recover from.%n
1350	An error occurred during DNS host lookup.%n	An error occurred during DNS host lookup.%n
1351	There is a problem with the network. Check to see the sockets services are up, the computer is connected to the network, etc.%n	There is a problem with the network. Check to see the sockets services are up, the computer is connected to the network, etc.%n
1352	This may be a transient error. Try running dcdiag again in a few minutes. If the error persists, there might be a problem with the target server. Try running nettest and dcdiag on the target server.%n	This may be a transient error. Try running dcdiag again in a few minutes. If the error persists, there might be a problem with the target server. Try running nettest and dcdiag on the target server.%n
1353	This server could not be located on the network. This might be due to one or several of these reasons:%na) The target server is temporarily down;%nb) There is a problem with the target server. Try running nettest and dcdiag on the target server.%nc) The target server's DNS name is registered incorrectly in the directory service.%n	This server could not be located on the network. This might be due to one or several of these reasons:%na) The target server is temporarily down;%nb) There is a problem with the target server. Try running nettest and dcdiag on the target server.%nc) The target server's DNS name is registered incorrectly in the directory service.%n
1354	Warning: %1!ws! could not resolve the name for role%n	Warning: %1!ws! could not resolve the name for role%n
1355	The name error was %1!ws!.%n	The name error was %1!ws!.%n
1356	Warning: %1!ws! is the %2!ws!, but is deleted.%n	Warning: %1!ws! is the %2!ws!, but is deleted.%n
1357	Warning: %1!ws! returned role-holder name%n	Warning: %1!ws! returned role-holder name%n
1358	%1!ws! that is unknown to this Enterprise.%n	%1!ws! that is unknown to this Enterprise.%n
1359	Warning: %1!ws! is the %2!ws!, but is not responding to DS RPC Bind.%n	Warning: %1!ws! is the %2!ws!, but is not responding to DS RPC Bind.%n
1360	Warning: %1!ws! is the %2!ws!, but is not responding to LDAP Bind.%n	Warning: %1!ws! is the %2!ws!, but is not responding to LDAP Bind.%n
1361	Warning: the directory service on %1!ws! has not completed initial synchronization.%nOther services will be delayed.%nVerify that the server can replicate.%n	Warning: the directory service on %1!ws! has not completed initial synchronization.%nOther services will be delayed.%nVerify that the server can replicate.%n
1362	Fatal Error:DsGetDcName (%1!ws!) call failed, error %2!d!%nThe Locator could not find the server.%n	Fatal Error:DsGetDcName (%1!ws!) call failed, error %2!d!%nThe Locator could not find the server.%n
1363	Warning: DsGetDcName returned information for %1!ws!, when we were trying to reach %2!ws!.%nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.%n	Warning: DsGetDcName returned information for %1!ws!, when we were trying to reach %2!ws!.%nSERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.%n
1364	Warning: %1!ws! is NOT advertising as a directory server Domain Controller.%nCheck that the database on this machine has sufficient free space.%n	Warning: %1!ws! is NOT advertising as a directory server Domain Controller.%nCheck that the database on this machine has sufficient free space.%n
1365	Warning: %1!ws! is NOT advertising as a LDAP server.%n	Warning: %1!ws! is NOT advertising as a LDAP server.%n
1366	Warning: %1!ws! is NOT advertising as a writable directory server.%n	Warning: %1!ws! is NOT advertising as a writable directory server.%n
1367	Warning: %1!ws! is advertising as a writable directory server.%n	Warning: %1!ws! is advertising as a writable directory server.%n
1368	Warning: %1!ws! is not advertising as a Key Distribution Center.%nCheck that the Directory has started.%n	Warning: %1!ws! is not advertising as a Key Distribution Center.%nCheck that the Directory has started.%n
1369	Warning: %1!ws! is not advertising as a time server.%n	Warning: %1!ws! is not advertising as a time server.%n
1370	Warning: %1!ws! has not finished promoting to be a GC.%nCheck the event log for domains that cannot be replicated.%n	Warning: %1!ws! has not finished promoting to be a GC.%nCheck the event log for domains that cannot be replicated.%n
1371	Server %1 is advertising as a global catalog, but%nit could not be verified that the server thought it was a GC.%n	Server %1 is advertising as a global catalog, but%nit could not be verified that the server thought it was a GC.%n
1372	Warning: %1!ws! is not advertising as a global catalog.%nCheck that server finished GC promotion.%nCheck the event log on server that enough source replicas for the GC are available.%n	Warning: %1!ws! is not advertising as a global catalog.%nCheck that server finished GC promotion.%nCheck the event log on server that enough source replicas for the GC are available.%n
1373	Error: A GC returned by DsGetDcName() was not a GC in it's directory%n	Error: A GC returned by DsGetDcName() was not a GC in it's directory%n
1374	GC Name: %1!ws!%n	GC Name: %1!ws!%n
1375	Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error %1!d!%n	Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error %1!d!%n
1376	A Global Catalog Server could not be located - All GC's are down.%n	A Global Catalog Server could not be located - All GC's are down.%n
1377	Error: The server returned by DsGetDcName() did not match DsListRoles() for the PDC%n	Error: The server returned by DsGetDcName() did not match DsListRoles() for the PDC%n
1378	Warning: DcGetDcName(PDC_REQUIRED) call failed, error %1!d!%n	Warning: DcGetDcName(PDC_REQUIRED) call failed, error %1!d!%n
1379	A Primary Domain Controller could not be located.%nThe server holding the PDC role is down.%n	A Primary Domain Controller could not be located.%nThe server holding the PDC role is down.%n
1380	Warning: DcGetDcName(TIME_SERVER) call failed, error %1!d!%nA Time Server could not be located.%nThe server holding the PDC role is down.%n	Warning: DcGetDcName(TIME_SERVER) call failed, error %1!d!%nA Time Server could not be located.%nThe server holding the PDC role is down.%n
1381	Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error %1!d!%nA Good Time Server could not be located.%n	Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error %1!d!%nA Good Time Server could not be located.%n
1382	Warning: DcGetDcName(KDC_REQUIRED) call failed, error %1!d!%nA KDC could not be located - All the KDCs are down.%n	Warning: DcGetDcName(KDC_REQUIRED) call failed, error %1!d!%nA KDC could not be located - All the KDCs are down.%n
1383	Failed to read object metadata on %1!ws!, error %2!ws!%n	Failed to read object metadata on %1!ws!, error %2!ws!%n
1384	Asked to verify objects status (object %1 in domain %2) on DC %3 which doesn't hold the object!%n	Asked to verify objects status (object %1 in domain %2) on DC %3 which doesn't hold the object!%n
1385	Ignoring DC %1 in the convergence test of object %2, because we cannot connect!%n	Ignoring DC %1 in the convergence test of object %2, because we cannot connect!%n
1386	Fatal Error: DsListRoles (%1!ws!) call failed, error %2!d!%nCould not reach DS at home server.%n	Fatal Error: DsListRoles (%1!ws!) call failed, error %2!d!%nCould not reach DS at home server.%n
1400	[%1] An LDAP operation failed with error %2!d!%n	[%1] An LDAP operation failed with error %2!d!%n
1401	%1: Unable to lookup account SID with error %2!d!%n	%1: Unable to lookup account SID with error %2!d!%n
1402	Fatal Error: Cannot retrieve Security Descriptor Dacl%n	Fatal Error: Cannot retrieve Security Descriptor Dacl%n
1403	Fatal Error: Cannot retrieve SID%n	Fatal Error: Cannot retrieve SID%n
1404	Error %1 doesn't have %n	Error %1 doesn't have %n
1405	access rights for the naming context:%n	access rights for the naming context:%n
1406	* Security Permissions Check for%n	* Security Permissions Check for%n
1407	* You must make sure there are no existing net use connections,%n* You must make sure there are no existing net use connections,%n \\\%n	* You must make sure there are no existing net use connections,%n* You must make sure there are no existing net use connections,%n \\\%n
1408	Unable to connect to the NETLOGON share! (%1)%n	Unable to connect to the NETLOGON share! (%1)%n
1409	Unable to connect to the SYSVOL share! (%1)%n	Unable to connect to the SYSVOL share! (%1)%n
1410	* Warning %1\%2 did not have the "Access this computer%n"* from network" right.%n	* Warning %1\%2 did not have the "Access this computer%n"* from network" right.%n
1411	[%1] Fatal Error: Not enough memory to complete operation.%n	[%1] Fatal Error: Not enough memory to complete operation.%n
1412	[%1] Fatal Error: The network resource is already in use%n	[%1] Fatal Error: The network resource is already in use%n
1413	[%1] User credentials does not have permission to perform this operation.%nThe account used for this test must have network logon privileges%nfor this machine's domain.%n	[%1] User credentials does not have permission to perform this operation.%nThe account used for this test must have network logon privileges%nfor this machine's domain.%n
1414	The KDC on %1 isn't responsive, please verify that it's running and advertising.%n	The KDC on %1 isn't responsive, please verify that it's running and advertising.%n
1415	Warning: The maximum non-fragmentable UDP transfer unit is %1!d!.%n	Warning: The maximum non-fragmentable UDP transfer unit is %1!d!.%n
1416	This isn't a sufficient size for operation if any DC's in the enterprise are Win2k SP3 or earlier.%n	This isn't a sufficient size for operation if any DC's in the enterprise are Win2k SP3 or earlier.%n
1417	Solution: Either install at least W2K SP4 or better, or configure the network to allow non-fragmented UDP packets of at least 2008 bytes.%n	Solution: Either install at least W2K SP4 or better, or configure the network to allow non-fragmented UDP packets of at least 2008 bytes.%n
1418	This isn't a sufficient size for successful KDC operation unless all DC's in the enterprise are Windows Server 2003 or better.%n	This isn't a sufficient size for successful KDC operation unless all DC's in the enterprise are Windows Server 2003 or better.%n
1419	Solution: Either configure the network to allow non-fragmented UDP packets of at least 1472 bytes, or install Server 2003 on all DC's in the enterprise and configure the KDC kerberos packet size to %1!d!.%n	Solution: Either configure the network to allow non-fragmented UDP packets of at least 1472 bytes, or install Server 2003 on all DC's in the enterprise and configure the KDC kerberos packet size to %1!d!.%n
1420	Cannot establish any contact to the DC %1.%n	Cannot establish any contact to the DC %1.%n
1421	No KDC found for domain %1 in site %2 (%3!d!, %4)%n	No KDC found for domain %1 in site %2 (%3!d!, %4)%n
1422	Error %1!d! querying time on DC %2. Ignoring this DC and continuing...%n	Error %1!d! querying time on DC %2. Ignoring this DC and continuing...%n
1423	Error %1!d! attempting to un-impersonate the requested user. Attempting to continue testing...%n	Error %1!d! attempting to un-impersonate the requested user. Attempting to continue testing...%n
1424	Error %1!d! attempting to impersonate the requested user. Unable to verify time synchronization!%n	Error %1!d! attempting to impersonate the requested user. Unable to verify time synchronization!%n
1425	Time skew error: %1!d! seconds different between:.%n	Time skew error: %1!d! seconds different between:.%n
1426	Time skew error between client and %1!d! DCs! ERROR_ACCESS_DENIED or down machine received by:%n	Time skew error between client and %1!d! DCs! ERROR_ACCESS_DENIED or down machine received by:%n
1427	Cannot verify time sync! Can the local machine authenticate? Continuing...%n	Cannot verify time sync! Can the local machine authenticate? Continuing...%n
1428	Warning, the server %1 was not found!%n	Warning, the server %1 was not found!%n
1429	[%1] DsReplicaGetInfo(NEIGHBORS) failed with error %2!d!,%n	[%1] DsReplicaGetInfo(NEIGHBORS) failed with error %2!d!,%n
1430	[%1] DsReplicaGetInfo(KCC_DS_CONNECT_FAILURES) failed with error %2!d!,%n	[%1] DsReplicaGetInfo(KCC_DS_CONNECT_FAILURES) failed with error %2!d!,%n
1431	Unable to locate the DC %1. The input will be ignored.%n	Unable to locate the DC %1. The input will be ignored.%n
1432	Unable to locate the DC unknown. The input will be ignored.%n	Unable to locate the DC unknown. The input will be ignored.%n
1433	[%1] Unable to query the replication status of existing connections. Continuing...%n	[%1] Unable to query the replication status of existing connections. Continuing...%n
1434	[%1] Unable to query the list of KCC connection failures. Continuing...%n	[%1] Unable to query the list of KCC connection failures. Continuing...%n
1435	[%1] Unable to identify a domain partition on this DC. Cannot continue.%n	[%1] Unable to identify a domain partition on this DC. Cannot continue.%n
1436	[%1] Unable to contact a KDC for the destination domain in it's own site. This means either there are no available KDC's for this domain in the site, *including* the destination DC itself, or we're having network or packet fragmentation issues connecting to it. We'll check packet fragmentation connection to the destination DC, make recommendations, and continue.%n	[%1] Unable to contact a KDC for the destination domain in it's own site. This means either there are no available KDC's for this domain in the site, *including* the destination DC itself, or we're having network or packet fragmentation issues connecting to it. We'll check packet fragmentation connection to the destination DC, make recommendations, and continue.%n
1437	[%1] Unable to contact a KDC for the destination domain. If no KDC for the destination domain is available, replication will be blocked!%n	[%1] Unable to contact a KDC for the destination domain. If no KDC for the destination domain is available, replication will be blocked!%n
1438	If there is some KDC for that domain available, check network connectivity issues or see possible packet fragmentation issues above.%n	If there is some KDC for that domain available, check network connectivity issues or see possible packet fragmentation issues above.%n
1439	Unable to verify the machine account (%1) for %2 on %3.%n	Unable to verify the machine account (%1) for %2 on %3.%n
1440	Unable to verify the convergence of this machine account (%1) on these DC's (%2,%3). Does the machine account password need resetting?%n	Unable to verify the convergence of this machine account (%1) on these DC's (%2,%3). Does the machine account password need resetting?%n
1441	[%1] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:.%n	[%1] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:.%n
1442	Source DC %1 has possible security error (%2!d!). Diagnosing...%n	Source DC %1 has possible security error (%2!d!). Diagnosing...%n
1443	Source DC %1 was requested for a manual security error check. Diagnosing...%n	Source DC %1 was requested for a manual security error check. Diagnosing...%n
1444	[%1] Unable to identify a domain partition on this DC. Cannot continue diagnosing errors with this DC.%n	[%1] Unable to identify a domain partition on this DC. Cannot continue diagnosing errors with this DC.%n
1445	[%1] Unable to contact this DC. Cannot continue diagnosing errors with this DC.%n	[%1] Unable to contact this DC. Cannot continue diagnosing errors with this DC.%n
1446	[%1] Unable to contact a KDC for the source domain in it's own site. This means either there are no available KDC's for this domain in the site, *including* the source DC itself, or we're having network or packet fragmentation issues connecting to it. We'll check packet fragmentation connection to the source DC, make recommendations, and continue.%n	[%1] Unable to contact a KDC for the source domain in it's own site. This means either there are no available KDC's for this domain in the site, *including* the source DC itself, or we're having network or packet fragmentation issues connecting to it. We'll check packet fragmentation connection to the source DC, make recommendations, and continue.%n
1447	[%1] Unable to contact a KDC for the source domain. If no KDC for the source domain is available, replication will be blocked!%n	[%1] Unable to contact a KDC for the source domain. If no KDC for the source domain is available, replication will be blocked!%n
1448	Unable to verify the convergence of this machine account (%1) on these DC's (%2,%3). Does the machine account password need resetting? Are the SPN's in sync?%n	Unable to verify the convergence of this machine account (%1) on these DC's (%2,%3). Does the machine account password need resetting? Are the SPN's in sync?%n
1449	[%1] Unable to verify logon privileges on DC shares. Please check the above output and take appropriate steps.%n	[%1] Unable to verify logon privileges on DC shares. Please check the above output and take appropriate steps.%n
1450	[%1] Unable to diagnose problem for this source. See any errors reported in attempting tests.%n	[%1] Unable to diagnose problem for this source. See any errors reported in attempting tests.%n
1451	Unable to verify the convergence of this machine account (%1) on this domain (%2). Does the machine account password need resetting?%n	Unable to verify the convergence of this machine account (%1) on this domain (%2). Does the machine account password need resetting?%n
1452	Unable to verify the convergence of this machine account (%1) on this domain (%2). Does the machine account password need resetting? Are the SPN's in sync?%n	Unable to verify the convergence of this machine account (%1) on this domain (%2). Does the machine account password need resetting? Are the SPN's in sync?%n
1455	An LDAP search of the RootDSE failed.%n	An LDAP search of the RootDSE failed.%n
1456	REPLICATION LATENCY WARNING%nERROR: Expected notification link is missing.%nSource %1%nReplication of new changes along this path will be delayed.%nThis problem should self-correct on the next periodic sync.%n	REPLICATION LATENCY WARNING%nERROR: Expected notification link is missing.%nSource %1%nReplication of new changes along this path will be delayed.%nThis problem should self-correct on the next periodic sync.%n
1457	ERROR: Unexpected number of reps-to neighbors returned from %1!ws!.%n	ERROR: Unexpected number of reps-to neighbors returned from %1!ws!.%n
1458	ERROR: Reps-to has unexpected contents.%n	ERROR: Reps-to has unexpected contents.%n
1459	Progress is occurring normally on this path.%n	Progress is occurring normally on this path.%n
1460	A large number of replication updates need to be carried on this%npath. Higher priority replication work has temporarily interrupted%nprogress on this link.%n	A large number of replication updates need to be carried on this%npath. Higher priority replication work has temporarily interrupted%nprogress on this link.%n
1461	Boot-time synchronization of this link was skipped because the source%nwas taking too long returning updates. Another sync will be tried%nat the next periodic replication interval.%n	Boot-time synchronization of this link was skipped because the source%nwas taking too long returning updates. Another sync will be tried%nat the next periodic replication interval.%n
1462	Either the source or destination was shutdown during the replication cycle.%n	Either the source or destination was shutdown during the replication cycle.%n
1463	The parent of the object we tried to add is missing%nbecause it is deleted.%nA modification and a parent delete occurred at the same time.%nReplication will correct itself later once the writeable%ncopies synchronize and sort out the inconsistency.%n	The parent of the object we tried to add is missing%nbecause it is deleted.%nA modification and a parent delete occurred at the same time.%nReplication will correct itself later once the writeable%ncopies synchronize and sort out the inconsistency.%n
1464	The source remains down. Please check the machine.%n	The source remains down. Please check the machine.%n
1465	The source %1 is responding now.%n	The source %1 is responding now.%n
1466	The guid-based DNS name %1%nis not registered on one or more DNS servers.%n	The guid-based DNS name %1%nis not registered on one or more DNS servers.%n
1467	Check load and resource usage on %1.%n	Check load and resource usage on %1.%n
1468	Security provider may have returned an unexpected error code.%nCheck the clock difference between the two machines.%n	Security provider may have returned an unexpected error code.%nCheck the clock difference between the two machines.%n
1469	The replication RPC call executed for too long at the server and%nwas cancelled.%nCheck load and resource usage on %1.%n	The replication RPC call executed for too long at the server and%nwas cancelled.%nCheck load and resource usage on %1.%n
1470	The directory on %1 is in the process.%nof starting up or shutting down, and is not available.%nVerify machine is not hung during boot.%n	The directory on %1 is in the process.%nof starting up or shutting down, and is not available.%nVerify machine is not hung during boot.%n
1471	Kerberos Error.%nCheck that the system time between the two servers is sufficiently.%nclose. Also check that the time service is functioning correctly%n	Kerberos Error.%nCheck that the system time between the two servers is sufficiently.%nclose. Also check that the time service is functioning correctly%n
1472	The machine account for the destination %1.%nis not configured properly.%nCheck the userAccountControl field.%n	The machine account for the destination %1.%nis not configured properly.%nCheck the userAccountControl field.%n
1473	Kerberos Error.%nThe machine account is not present, or does not match on the.%ndestination, source or KDC servers.%nVerify domain partition of KDC is in sync with rest of enterprise.%nThe tool repadmin/syncall can be used for this purpose.%n	Kerberos Error.%nThe machine account is not present, or does not match on the.%ndestination, source or KDC servers.%nVerify domain partition of KDC is in sync with rest of enterprise.%nThe tool repadmin/syncall can be used for this purpose.%n
1474	Kerberos Error.%nA KDC was not found to authenticate the call.%nCheck that sufficient domain controllers are available.%n	Kerberos Error.%nA KDC was not found to authenticate the call.%nCheck that sufficient domain controllers are available.%n
1475	Check that the servers have the proper certificates.%n	Check that the servers have the proper certificates.%n
1476	Replication has been explicitly disabled through the server options.%n	Replication has been explicitly disabled through the server options.%n
1477	Try upgrading all domain controllers to the latest software version.%nTry synchronizing the Schema partition on all servers in the forest.%n	Try upgrading all domain controllers to the latest software version.%nTry synchronizing the Schema partition on all servers in the forest.%n
1478	Try synchronizing the Schema partition on all servers in the forest.%n	Try synchronizing the Schema partition on all servers in the forest.%n
1479	The disk containing the database or log files on %1%ndoes not have enough space to replicate in the latest changes.%nTry moving the database files to a larger volume using ntdsutil.%n	The disk containing the database or log files on %1%ndoes not have enough space to replicate in the latest changes.%nTry moving the database files to a larger volume using ntdsutil.%n
1480	The size of the last replication update was too large or complex%nto be held in memory. Consult the error log. The change%nmust be simplified at the server where it originated.%n	The size of the last replication update was too large or complex%nto be held in memory. Consult the error log. The change%nmust be simplified at the server where it originated.%n
1481	A serious error is preventing replication from continuing.%nConsult the error log for further information.%nIf a particular object is named, it may be necessary to manually%nmodify or delete the object.%nIf the condition persists, contact Microsoft Support.%n	A serious error is preventing replication from continuing.%nConsult the error log for further information.%nIf a particular object is named, it may be necessary to manually%nmodify or delete the object.%nIf the condition persists, contact Microsoft Support.%n
1482	Skipping server %1, because it has outbound replication disabled%n	Skipping server %1, because it has outbound replication disabled%n
1483	[%1,%2] A recent replication attempt failed:%n	[%1,%2] A recent replication attempt failed:%n
1484	From %1 to %2%nNaming Context: %3%nThe replication generated an error (%4!ld!):%n%5%nThe failure occurred at %6.%nThe last success occurred at %7.%n%8!d! failures have occurred since the last success.%n	From %1 to %2%nNaming Context: %3%nThe replication generated an error (%4!ld!):%n%5%nThe failure occurred at %6.%nThe last success occurred at %7.%n%8!d! failures have occurred since the last success.%n
1485	[Replications Check,%1] No replication recently attempted:%n	[Replications Check,%1] No replication recently attempted:%n
1486	From %1 to %2%nNaming Context: %3%nThe last attempt occurred at %4 (about %5!I64d! hours ago).%n	From %1 to %2%nNaming Context: %3%nThe last attempt occurred at %4 (about %5!I64d! hours ago).%n
1487	%1: This replication path was preempted by higher priority work.%n	%1: This replication path was preempted by higher priority work.%n
1488	from %1 to %2%nReason: %3%nThe last success occurred at %4.%nReplication of new changes along this path will be delayed.%n	from %1 to %2%nReason: %3%nThe last success occurred at %4.%nReplication of new changes along this path will be delayed.%n
1489	REPLICATION LATENCY WARNING%n	REPLICATION LATENCY WARNING%n
1490	%1: A full synchronization is in progress%n	%1: A full synchronization is in progress%n
1491	from %1 to %2%nReplication of new changes along this path will be delayed.%n	from %1 to %2%nReplication of new changes along this path will be delayed.%n
1492	The full sync is %1!d! percent complete.%n	The full sync is %1!d! percent complete.%n
1493	%1: A long-running replication operation is in progress%n	%1: A long-running replication operation is in progress%n
1494	The job has been executing for %1!d! minutes and %2!d! seconds.%nReplication of new changes along this path will be delayed.%n	The job has been executing for %1!d! minutes and %2!d! seconds.%nReplication of new changes along this path will be delayed.%n
1495	Error: Higher priority replications are being blocked%n	Error: Higher priority replications are being blocked%n
1496	This is normal for a new connection, or for a system%nthat has been down a long time.%n	This is normal for a new connection, or for a system%nthat has been down a long time.%n
1497	Enqueued %1 at priority %2!d!%n	Enqueued %1 at priority %2!d!%n
1498	SYNC FROM SOURCE	SYNC FROM SOURCE
1499	ADD NEW SOURCE	ADD NEW SOURCE
1500	DELETE SOURCE	DELETE SOURCE
1501	MODIFY SOURCE	MODIFY SOURCE
1502	UPDATE CHANGE NOTIFICATION	UPDATE CHANGE NOTIFICATION
1503	UNKNOWN	UNKNOWN
1504	%1: %2!d! replication work items are backed up.%n	%1: %2!d! replication work items are backed up.%n
1505	REPLICATION-RECEIVED LATENCY WARNING%n	REPLICATION-RECEIVED LATENCY WARNING%n
1506	%1: Current time is %2!S!.%n	%1: Current time is %2!S!.%n
1507	Last replication received from %1 at	Last replication received from %1 at
1508	WARNING: This latency is over the Tombstone Lifetime of %1!d! days!%n	WARNING: This latency is over the Tombstone Lifetime of %1!d! days!%n
1509	[Replications Check,%1] An LDAP operation failed with error %2!d!, %3.%n	[Replications Check,%1] An LDAP operation failed with error %2!d!, %3.%n
1510	[Replications Check,%1] Inbound replication is disabled.%n	[Replications Check,%1] Inbound replication is disabled.%n
1511	To correct, run "repadmin /options %1 -DISABLE_INBOUND_REPL"%n	To correct, run "repadmin /options %1 -DISABLE_INBOUND_REPL"%n
1512	[Replications Check,%1] Outbound replication is disabled.%n	[Replications Check,%1] Outbound replication is disabled.%n
1513	To correct, run "repadmin /options %1 -DISABLE_OUTBOUND_REPL"%n	To correct, run "repadmin /options %1 -DISABLE_OUTBOUND_REPL"%n
1514	[Replications Check,%1] Outbound replication is enabled.%n	[Replications Check,%1] Outbound replication is enabled.%n
1515	To correct, run "repadmin /options %1 +DISABLE_OUTBOUND_REPL"%n	To correct, run "repadmin /options %1 +DISABLE_OUTBOUND_REPL"%n
1516	[Replications Check,%1] Connection object translation is disabled.%n	[Replications Check,%1] Connection object translation is disabled.%n
1517	To correct, run "repadmin /options %1 -DISABLE_NTDSCONN_XLATE"%n	To correct, run "repadmin /options %1 -DISABLE_NTDSCONN_XLATE"%n
1518	[Replications Check,%1] Connection object translation is enabled.%n	[Replications Check,%1] Connection object translation is enabled.%n
1519	To correct, run "repadmin /options %1 +DISABLE_NTDSCONN_XLATE"%n	To correct, run "repadmin /options %1 +DISABLE_NTDSCONN_XLATE"%n
1520	[Replications Check,%1] DsReplicaGetInfo(%2, %3) failed, error 0x%4!x! "%5"%n	[Replications Check,%1] DsReplicaGetInfo(%2, %3) failed, error 0x%4!x! "%5"%n
1526	Upstream topology is disconnected for %1!ws!.%n	Upstream topology is disconnected for %1!ws!.%n
1527	Home server %1!ws! can't get changes from these servers:%n	Home server %1!ws! can't get changes from these servers:%n
1528	DsReplicaSyncAllW failed with error %1!ws!.%n	DsReplicaSyncAllW failed with error %1!ws!.%n
1529	Downstream topology is disconnected for %1!ws!.%n	Downstream topology is disconnected for %1!ws!.%n
1530	Failed to bind to %1!ws!: %2!ws!.%n	Failed to bind to %1!ws!: %2!ws!.%n
1531	[Topology Integrity Check,%1] Intra-site topology generation is disabled in this site.%n	[Topology Integrity Check,%1] Intra-site topology generation is disabled in this site.%n
1532	[Topology Integrity Check,%1] Inter-site topology generation is disabled in this site.%n	[Topology Integrity Check,%1] Inter-site topology generation is disabled in this site.%n
1540	%n Directory Server Diagnosis%n%ndcdiag.exe /s:[:] [/u:\ /p:*||""] %n [/hqv] [/n:] [/f:] [/x:XMLLog.xml]%n [/skip:] [/test:]%n /h: Display this help screen	%n Directory Server Diagnosis%n%ndcdiag.exe /s:[:] [/u:\ /p:*||""] %n [/hqv] [/n:] [/f:] [/x:XMLLog.xml]%n [/skip:] [/test:]%n /h: Display this help screen
1541	%n /s: Use as Home Server. Ignored for DcPromo and%n RegisterInDns tests which can only be run locally.%n /n: Use as the Naming Context to test%n Domains may be specified in Netbios, DNS or DN form.%n /u: Use domain\username credentials for binding.%n Must also use the /p option	%n /s: Use as Home Server. Ignored for DcPromo and%n RegisterInDns tests which can only be run locally.%n /n: Use as the Naming Context to test%n Domains may be specified in Netbios, DNS or DN form.%n /u: Use domain\username credentials for binding.%n Must also use the /p option
1542	%n /p: Use as the password. Must also use the /u option%n /a: Test all the servers in this site%n /e: Test all the servers in the entire enterprise. Overrides /a%n /q: Quiet - Only print error messages%n /v: Verbose - Print extended information%n /i: ignore - ignores superfluous error messages.%n /c: Comprehensive, runs all tests, including non-default tests but excluding%n DcPromo and RegisterInDNS. Can use with /skip%n /fix: fix - Make safe repairs.%n /f: Redirect all output to a file seperately%n /x: Redirect xml output to . Currently works with /test:dns option only%n /xsl: Adds the processing instructions that references specified stylesheet. Works with /test:dns /x: option only	%n /p: Use as the password. Must also use the /u option%n /a: Test all the servers in this site%n /e: Test all the servers in the entire enterprise. Overrides /a%n /q: Quiet - Only print error messages%n /v: Verbose - Print extended information%n /i: ignore - ignores superfluous error messages.%n /c: Comprehensive, runs all tests, including non-default tests but excluding%n DcPromo and RegisterInDNS. Can use with /skip%n /fix: fix - Make safe repairs.%n /f: Redirect all output to a file seperately%n /x: Redirect xml output to . Currently works with /test:dns option only%n /xsl: Adds the processing instructions that references specified stylesheet. Works with /test:dns /x: option only
1543	%n /fwttdll: User-specified path for dll for wtt logging. Defaults to WttLog.dll.%n /fwttdev: User-specified path for wtt log file. Defaults to exe name.%n /wtt: Additionally, use wtt logging%n	%n /fwttdll: User-specified path for dll for wtt logging. Defaults to WttLog.dll.%n /fwttdev: User-specified path for wtt log file. Defaults to exe name.%n /wtt: Additionally, use wtt logging%n
1544	%n /test: - Test only this test. Required tests will still%n be run. Do not mix with /skip.%n	%n /test: - Test only this test. Required tests will still%n be run. Do not mix with /skip.%n
1546	%n /skip: - Skip the named test. Required tests will still%n be run. Do not mix with /test.%n	%n /skip: - Skip the named test. Required tests will still%n be run. Do not mix with /test.%n
1547	%n%tAll tests except DcPromo and RegisterInDNS must be run on computers%n%tafter they have been promoted to directory server.%n%n%tNote: Text (Naming Context names, server names, etc) with International or%n%tUnicode characters will only display correctly if appropriate fonts and%n%tlanguage support are loaded%n	%n%tAll tests except DcPromo and RegisterInDNS must be run on computers%n%tafter they have been promoted to directory server.%n%n%tNote: Text (Naming Context names, server names, etc) with International or%n%tUnicode characters will only display correctly if appropriate fonts and%n%tlanguage support are loaded%n
1549	Directory Server Diagnosis%n	Directory Server Diagnosis%n
1550	%nAAAA record, name: %1, IP address: %2%n	%nAAAA record, name: %1, IP address: %2%n
1558	%nDNS Tests are running and not hung. Please wait a few minutes...%n	%nDNS Tests are running and not hung. Please wait a few minutes...%n
1559	Finding server for domain %1...%n	Finding server for domain %1...%n
1560	ERROR: Could not find the server.%n	ERROR: Could not find the server.%n
1561	Server for domain = %1%n	Server for domain = %1%n
1562	Trying to find home server...%n	Trying to find home server...%n
1563	ERROR: Could not find home server.%n	ERROR: Could not find home server.%n
1564	Home Server = %1%n	Home Server = %1%n
1565	The server %1 is the PDC for the %2 domain. It is not supposed to have a secure channel to this domain. The test is skipped.%n	The server %1 is the PDC for the %2 domain. It is not supposed to have a secure channel to this domain. The test is skipped.%n
1568	Unable to determine whether IP4 or IP6 stacks are enabled on the local machine.%nError 0x%1!x! "%2"	Unable to determine whether IP4 or IP6 stacks are enabled on the local machine.%nError 0x%1!x! "%2"
1569	Both IPV4 and IPV6 channels are disabled on all adapter cards of the local server. Hence no connectivity to the server.%n	Both IPV4 and IPV6 channels are disabled on all adapter cards of the local server. Hence no connectivity to the server.%n
1570	Event Session could not be opened to the server %1, error 0x%2!x! "%3"%n	Event Session could not be opened to the server %1, error 0x%2!x! "%3"%n
1571	The event log %1 on server %2 could not be queried, error 0x%3!x! "%4"%n	The event log %1 on server %2 could not be queried, error 0x%3!x! "%4"%n
1572	A rendering context creation on server %1 for rendering events from log %2 failed, error 0x%3!x! "%4"%n	A rendering context creation on server %1 for rendering events from log %2 failed, error 0x%3!x! "%4"%n
1573	Event rendering failed, error %1!d! "%2"%n	Event rendering failed, error %1!d! "%2"%n
1574	Iterating through the events failed, error %1!d! "%2"%n	Iterating through the events failed, error %1!d! "%2"%n
1575	Invalid service type: %1 on %2, current value %3, expected value %4%n	Invalid service type: %1 on %2, current value %3, expected value %4%n
1576	Invalid service startup type: %1 on %2, current value %3, expected value %4%n	Invalid service startup type: %1 on %2, current value %3, expected value %4%n
1577	%1\%2 is an unoccupied RODC account. All tests will be skipped.%n	%1\%2 is an unoccupied RODC account. All tests will be skipped.%n
1578	%n The list of known tests:%n%n	%n The list of known tests:%n%n
1579	%t * Test is applicable to AD/LDS%n	%t * Test is applicable to AD/LDS%n
1580	%t * Test cannot be skipped%n	%t * Test cannot be skipped%n
1581	%t * Test is not run by default, i.e. it must be requested explicitly%n	%t * Test is not run by default, i.e. it must be requested explicitly%n
1582	No host records (A or AAAA) were found for this DC%n	No host records (A or AAAA) were found for this DC%n
1584	Missing A record at DNS server %1!ws!:	Missing A record at DNS server %1!ws!:
1585	Missing AAAA record at DNS server %1!ws!:	Missing AAAA record at DNS server %1!ws!:
1586	Missing CNAME record at DNS server %1!ws!:	Missing CNAME record at DNS server %1!ws!:
1587	Missing SRV record at DNS server %1!ws!:	Missing SRV record at DNS server %1!ws!:
1588	Missing DC SRV record at DNS server %1!ws!:	Missing DC SRV record at DNS server %1!ws!:
1589	Missing GC SRV record at DNS server %1!ws!:	Missing GC SRV record at DNS server %1!ws!:
1590	Missing PDC SRV record at DNS server %1!ws!:	Missing PDC SRV record at DNS server %1!ws!:
1592	Error:	Error:
1593	Got error while checking if the DC is using FRS or DFSR. Error: %1!ws!The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. %n	Got error while checking if the DC is using FRS or DFSR. Error: %1!ws!The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. %n
1594	Got error while checking LDAP and RPC connectivity. Please check your firewall settings.%n	Got error while checking LDAP and RPC connectivity. Please check your firewall settings.%n
1595	Skip the test because the server is running FRS.%n	Skip the test because the server is running FRS.%n
1596	Skip the test because the server is running DFSR.%n	Skip the test because the server is running DFSR.%n
1597	A warning event occurred. EventID: 0x%1!08X!%n	A warning event occurred. EventID: 0x%1!08X!%n
1598	An error event occurred. EventID: 0x%1!08X!%n	An error event occurred. EventID: 0x%1!08X!%n
1599	Error: All forwarders in the forwarder list are invalid.%n	Error: All forwarders in the forwarder list are invalid.%n
10223	Error: all DNS servers are invalid%n	Error: all DNS servers are invalid%n
0x0	The operation was successful.	The operation was successful.
0x1	.%0	.%0
0x2	-----------------------------------------------------	-----------------------------------------------------
0x400007D0	Unused	Unused
0x400007D1	SERVER: %1	SERVER: %1
0x400007D2	The server list is empty.	The server list is empty.
0x400007D3	Doing intersite inbound replication test on site %1:	Doing intersite inbound replication test on site %1:
0x400007D4	Locating & Contacting Intersite Topology Generator (ISTG) ...	Locating & Contacting Intersite Topology Generator (ISTG) ...
0x400007D5	Checking for down bridgeheads ...	Checking for down bridgeheads ...
0x400007D6	Doing in depth site analysis ...	Doing in depth site analysis ...
0x400007D7	The ISTG for site %1 is: %2.	The ISTG for site %1 is: %2.
0x400007D8	Skipping site %1, this site is outside the scope provided by the commandline arguments provided.	Skipping site %1, this site is outside the scope provided by the commandline arguments provided.
0x400007D9	Bridghead %1\\%2 is up and replicating fine.	Bridghead %1\\%2 is up and replicating fine.
0x400007DA	All expected sites and bridgeheads are replicating into site %1.	All expected sites and bridgeheads are replicating into site %1.
0x400007DB	This site should not have been tested, bailing out now.	This site should not have been tested, bailing out now.
0x400007DC	Checking writeable NC: %1 on remote site %2	Checking writeable NC: %1 on remote site %2
0x400007DD	Checking read only NC: %1 on remote site %2	Checking read only NC: %1 on remote site %2
0x400007DE	Remote site %1 is replicating to the local site %2 the writeable NC %3 correctly.	Remote site %1 is replicating to the local site %2 the writeable NC %3 correctly.
0x400007DF	Remote site %1 is replicating to the local site %2 the read only NC %3 correctly.	Remote site %1 is replicating to the local site %2 the read only NC %3 correctly.
0x400007E0	ISTG (%1) Failure Parameters:%n Failover Tries: %2!d!%n Failover Time: %3!d!	ISTG (%1) Failure Parameters:%n Failover Tries: %2!d!%n Failover Time: %3!d!
0x400007E1	* Verifying that the local machine %1, is a Directory Server.	* Verifying that the local machine %1, is a Directory Server.
0x400007E2	This cross-ref (%1) is disabled.	This cross-ref (%1) is disabled.
0x400007E3	For the partition (%1) we encountered the following error retrieving the cross-ref's (%2) information:	For the partition (%1) we encountered the following error retrieving the cross-ref's (%2) information:
0x400007E4	For the partition (%1) we encountered the following error retrieving the cross-ref's information:	For the partition (%1) we encountered the following error retrieving the cross-ref's information:
0x400007E5	The system object reference (%1) %2 and backlink on %3 are correct.	The system object reference (%1) %2 and backlink on %3 are correct.
0x400007E6	Can't determine the age of the cross-ref %1 for the partition %2, so followingerrors relating to this cross-ref/partition may disappear after replication coalesces. Please ensure that replication is working from the Naming Masterto this Directory Server, and retry this test to see if errors continue.	Can't determine the age of the cross-ref %1 for the partition %2, so followingerrors relating to this cross-ref/partition may disappear after replication coalesces. Please ensure that replication is working from the Naming Masterto this Directory Server, and retry this test to see if errors continue.
0x400007E7	* The File Replication Service SYSVOL ready test	* The File Replication Service SYSVOL ready test
0x400007E8	* The File Replication Service Event log test	* The File Replication Service Event log test
0x400007E9	File Replication Service's SYSVOL is ready	File Replication Service's SYSVOL is ready
0x400007EA	* Replication Site Latency Check	* Replication Site Latency Check
0x80000FA1	* Warning: Current ISTG failed, ISTG role should be taken by %1 in %2!d! minutes.	* Warning: Current ISTG failed, ISTG role should be taken by %1 in %2!d! minutes.
0x80000FA2	* Warning: Current ISTG failed, ISTG role should be taken by %1 in %2!d! hours and %3!d! minutes.	* Warning: Current ISTG failed, ISTG role should be taken by %1 in %2!d! hours and %3!d! minutes.
0x80000FA3	Remote bridgehead %1\\%2 also couldn't be contacted by dcdiag. Check thisserver.	Remote bridgehead %1\\%2 also couldn't be contacted by dcdiag. Check thisserver.
0x80000FA4	*Warning: Remote bridgehead %1\\%2 is not eligible as a bridgehead due to toomany failures. Replication may be disrupted into the local site %3.	*Warning: Remote bridgehead %1\\%2 is not eligible as a bridgehead due to toomany failures. Replication may be disrupted into the local site %3.
0x80000FA5	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It willbe %3!d! failed replication attempts before the bridgehead is considered ineligible to be a bridgehead.	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It willbe %3!d! failed replication attempts before the bridgehead is considered ineligible to be a bridgehead.
0x80000FA6	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It will be %3!d! hours %4!d! minutes before the bridgehead is considered ineligible tobe a bridgehead.	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It will be %3!d! hours %4!d! minutes before the bridgehead is considered ineligible tobe a bridgehead.
0x80000FA7	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It willbe %3!d! hours %4!d! minutes and %5!d! failed replication attempts before the bridgehead is considered ineligible to be a bridgehead.	*Warning: Remote bridgehead %1\\%2 has some replication syncs failing. It willbe %3!d! hours %4!d! minutes and %5!d! failed replication attempts before the bridgehead is considered ineligible to be a bridgehead.
0x80000FA8	***Warning: The remote site %1, has only servers that dcdiag considers suspect.Replication from the site %1 into the local site %2 for the read write NC %3may be disrupted right now.	***Warning: The remote site %1, has only servers that dcdiag considers suspect.Replication from the site %1 into the local site %2 for the read write NC %3may be disrupted right now.
0x80000FA9	***Warning: The remote site %1, has only servers that dcdiag considers suspect.Replication from the site %1 into the local site %2 for the read only NC %3 may bedisrupted right now.	***Warning: The remote site %1, has only servers that dcdiag considers suspect.Replication from the site %1 into the local site %2 for the read only NC %3 may bedisrupted right now.
0x80000FAA	*Warning: ISTG time stamp is %1!d! minutes old on %2. Looking for a new ISTG.	*Warning: ISTG time stamp is %1!d! minutes old on %2. Looking for a new ISTG.
0x80000FAB	*Warning: Could not locate the next ISTG or site %1. Using the last known ISTG %2 as the ISTG.	*Warning: Could not locate the next ISTG or site %1. Using the last known ISTG %2 as the ISTG.
0x80000FAC	*Warning: Currest ISTG (%1) is down. Looking for a new ISTG.	*Warning: Currest ISTG (%1) is down. Looking for a new ISTG.
0x80000FAD	*Warning: Current ISTG (%1) has been moved out of this site (%2).Looking for a new ISTG.	*Warning: Current ISTG (%1) has been moved out of this site (%2).Looking for a new ISTG.
0x80000FAE	*Warning: The next ISTG could not be authoratively determined for site %1. A DCshould make an ISTG failover attempt in %2!d! minutes.	*Warning: The next ISTG could not be authoratively determined for site %1. A DCshould make an ISTG failover attempt in %2!d! minutes.
0x80000FAF	Neither the the server name (%1) nor the Guid DNS name (%2)could be resolved by DNS. Check that the server is up andis registered correctly with the DNS server.	Neither the the server name (%1) nor the Guid DNS name (%2)could be resolved by DNS. Check that the server is up andis registered correctly with the DNS server.
0x80000FB0	Although the Guid DNS name (%1) resolved to the IP address (%2), the server name (%3) could not be resolved by DNS. Check that the IP addressis registered correctly with the DNS server.	Although the Guid DNS name (%1) resolved to the IP address (%2), the server name (%3) could not be resolved by DNS. Check that the IP addressis registered correctly with the DNS server.
0x80000FB1	Although the Guid DNS name (%1) couldn't be resolved, the server name (%2)resolved to the IP address (%3) and was pingable. Check that the IP addressis registered correctly with the DNS server.	Although the Guid DNS name (%1) couldn't be resolved, the server name (%2)resolved to the IP address (%3) and was pingable. Check that the IP addressis registered correctly with the DNS server.
0x80000FB2	Although the Guid DNS name (%1) resolved to the IP address (%2), whichcould not be pinged, the server name (%3) resolved to the IP address (%4)and could be pinged. Check that the IP address is registeredcorrectly with the DNS server.	Although the Guid DNS name (%1) resolved to the IP address (%2), whichcould not be pinged, the server name (%3) resolved to the IP address (%4)and could be pinged. Check that the IP address is registeredcorrectly with the DNS server.
0x80000FB3	Although the Guid DNS name (%1) could not be resolved, the server name (%2)resolved to the IP address (%3) but was not pingable. Check that the IPaddress is registered correctly with the DNS server.	Although the Guid DNS name (%1) could not be resolved, the server name (%2)resolved to the IP address (%3) but was not pingable. Check that the IPaddress is registered correctly with the DNS server.
0x80000FB4	Although the Guid DNS name (%1) resolved to the IP address (%2), the servername (%3) resolved to the IP address (%4) and neither could be pinged. Checkthat the IP address is registered correctly with the DNS server.	Although the Guid DNS name (%1) resolved to the IP address (%2), the servername (%3) resolved to the IP address (%4) and neither could be pinged. Checkthat the IP address is registered correctly with the DNS server.
0x80000FB5	The directory service on %1 has not finished initializing.%nIn order for the directory service to consider itself synchronized,it must attempt an initial synchronization with at least one replica of thisserver's writeable domain. It must also obtain Rid information from the RidFSMO holder.%nThe directory service has not signalled the event which lets other services knowthat it is ready to accept requests. Services such as the Key Distribution Center,Intersite Messaging Service, and NetLogon will not consider this system as aneligible domain controller.	The directory service on %1 has not finished initializing.%nIn order for the directory service to consider itself synchronized,it must attempt an initial synchronization with at least one replica of thisserver's writeable domain. It must also obtain Rid information from the RidFSMO holder.%nThe directory service has not signalled the event which lets other services knowthat it is ready to accept requests. Services such as the Key Distribution Center,Intersite Messaging Service, and NetLogon will not consider this system as aneligible domain controller.
0x80000FB6	The \"RID manager reference\" could not be found for domain DN %1.The lack of a RID manager reference indicates that the Security Accounts Managerhas not been able to obtain a pool of RIDs for this machine.The Directory will not allow Netlogon to advertise this machine until thesystem has been able to obtain a RID pool.Please verify that this system can replicate with other members of the enterprise.Failure to replicate with the RID FSMO owner can prevent a system from obtaininga RID Pool.	The \"RID manager reference\" could not be found for domain DN %1.The lack of a RID manager reference indicates that the Security Accounts Managerhas not been able to obtain a pool of RIDs for this machine.The Directory will not allow Netlogon to advertise this machine until thesystem has been able to obtain a RID pool.Please verify that this system can replicate with other members of the enterprise.Failure to replicate with the RID FSMO owner can prevent a system from obtaininga RID Pool.
0x80000FB7	Warning: The \"RID manager reference\" for domain DN %1 refers to a deleted object.This can occur if the machine has been recently demoted and promoted, and thesystem has not yet obtained a new RID pool.	Warning: The \"RID manager reference\" for domain DN %1 refers to a deleted object.This can occur if the machine has been recently demoted and promoted, and thesystem has not yet obtained a new RID pool.
0x80000FB8	The clock difference between the home server %1 and target server %2is greater than one minute.This may cause Kerberos authentication failures.Please check that the time service is working properly. You may need toresynchonize the time between these servers.	The clock difference between the home server %1 and target server %2is greater than one minute.This may cause Kerberos authentication failures.Please check that the time service is working properly. You may need toresynchonize the time between these servers.
0x80000FB9	Warning: Could not verify whether this server has any SMTP replica links and thereforewill not check for services required for SMTP replication.	Warning: Could not verify whether this server has any SMTP replica links and thereforewill not check for services required for SMTP replication.
0x80000FBA	This NC (%1) is supposed to be replicated to this server, but has not been replicated yet.This could be because the replica set changes haven't replicated here yet. If this problempersists, check replication of the Configuration Partition to this server.	This NC (%1) is supposed to be replicated to this server, but has not been replicated yet.This could be because the replica set changes haven't replicated here yet. If this problempersists, check replication of the Configuration Partition to this server.
0x80000FBB	Site %1 was skipped because its metadata was returned in an unrecognized format.	Site %1 was skipped because its metadata was returned in an unrecognized format.
0x80000FBC	Site %1 was skipped because it never had an ISTG running in it.	Site %1 was skipped because it never had an ISTG running in it.
0x80000FBD	Site %1 was skipped because it has no servers in it.	Site %1 was skipped because it has no servers in it.
0x80000FBE	Site %1 was skipped because it has the ISTG turned off.	Site %1 was skipped because it has the ISTG turned off.
0x80000FBF	The GUID based DNS Name resolved to several IPs (%1), but not all were pingable.Replication and other operations may fail if a non-pingable IP is chosen.The first pingable IP is %2.	The GUID based DNS Name resolved to several IPs (%1), but not all were pingable.Replication and other operations may fail if a non-pingable IP is chosen.The first pingable IP is %2.
0xC00007EB	* Identified AD LDS Configuration Set.	* Identified AD LDS Configuration Set.
0xC00007EC	* Identified AD Forest.	* Identified AD Forest.
0xC0001770	Invalid Syntax: Invalid option %1. Use dcdiag.exe /h for help.	Invalid Syntax: Invalid option %1. Use dcdiag.exe /h for help.
0xC0001771	Syntax Error: must use /f:	Syntax Error: must use /f:
0xC0001772	Could not open %1 for writing.	Could not open %1 for writing.
0xC0001773	Syntax Error: must use /ferr:	Syntax Error: must use /ferr:
0xC0001774	Syntax Error: must use /x:	Syntax Error: must use /x:
0xC0001775	Syntax Error: must use /xsl:	Syntax Error: must use /xsl:
0xC0001776	Cannot specify more than one naming context.	Cannot specify more than one naming context.
0xC0001777	Syntax Error: must use /n:	Syntax Error: must use /n:
0xC0001778	Cannot specify more than one server.	Cannot specify more than one server.
0xC0001779	Syntax Error: must use /s:	Syntax Error: must use /s:
0xC000177A	Syntax Error: must use /skip:	Syntax Error: must use /skip:
0xC000177B	Syntax Error: must use /test:	Syntax Error: must use /test:
0xC000177C	Test not found. Please re-enter a valid test name.	Test not found. Please re-enter a valid test name.
0xC000177D	Cannot mix DC and non-DC tests.	Cannot mix DC and non-DC tests.
0xC000177E	Syntax Error: the test name must be followed by a DNS domain name and theoperation, e.g.:/test:DcPromo /DnsDomain:domain.company.com /If =NewTree, then the ForestRoot argument is alsorequired: /ForestRoot:See the help screen (/?) for more information.	Syntax Error: the test name must be followed by a DNS domain name and theoperation, e.g.:/test:DcPromo /DnsDomain:domain.company.com /If =NewTree, then the ForestRoot argument is alsorequired: /ForestRoot:See the help screen (/?) for more information.
0xC000177F	Syntax Error: must use %1	Syntax Error: must use %1
0xC0001780	***Error: %1 is not a Directory Server. Must specify /s: or /n: or nothing to use the local machine.	***Error: %1 is not a Directory Server. Must specify /s: or /n: or nothing to use the local machine.
0xC0001781	Error: Do not omit tests that are not run by default.%nUse dcdiag /? for those tests.	Error: Do not omit tests that are not run by default.%nUse dcdiag /? for those tests.
0xC0001782	*** ERROR: The home server %1 is not in sync with %2, unable to proceed.Suggest you run:%ndcdiag /s:%2	*** ERROR: The home server %1 is not in sync with %2, unable to proceed.Suggest you run:%ndcdiag /s:%2
0xC0001783	***ERROR: There is an inconsistency in the DS, suggest you run dcdiagin a few moments, perhaps on a different DC.	***ERROR: There is an inconsistency in the DS, suggest you run dcdiagin a few moments, perhaps on a different DC.
0xC0001784	Error: A fatal error occured: %1.	Error: A fatal error occured: %1.
0xC0001785	Error: Tried to print out a server list that was NULL. Error out of mem?	Error: Tried to print out a server list that was NULL. Error out of mem?
0xC0001786	Error: Failure connecting to home server %1, error: 0x%2!x! \"%3\"%nInbound intersite replication test cannot proceed.	Error: Failure connecting to home server %1, error: 0x%2!x! \"%3\"%nInbound intersite replication test cannot proceed.
0xC0001787	***Error: Can't contact the ISTG for site %1, must abort inbound intersitereplication test.	***Error: Can't contact the ISTG for site %1, must abort inbound intersitereplication test.
0xC0001788	***Error: On server %1, DsReplicaGetInfo() failed, error: 0x%2!x! \"%3\"%nInbound intersite replication test cannot proceed.	***Error: On server %1, DsReplicaGetInfo() failed, error: 0x%2!x! \"%3\"%nInbound intersite replication test cannot proceed.
0xC0001789	***Error: Detected circular loop trying to locate the ISTG. Must abandoninbound intersite replication test for this site %1.	***Error: Detected circular loop trying to locate the ISTG. Must abandoninbound intersite replication test for this site %1.
0xC000178A	***Error: Could not locate an ISTG or a future ISTG, with which to use for therest of the intersite test. Must abandon inbound intersite replication testfor this site %1.	***Error: Could not locate an ISTG or a future ISTG, with which to use for therest of the intersite test. Must abandon inbound intersite replication testfor this site %1.
0xC000178B	***Error: Couldn't retreive the meta data from %1 for site %2, error 0x%3!x! %4%nMust abandon inbound intersite replication test for this site.	***Error: Couldn't retreive the meta data from %1 for site %2, error 0x%3!x! %4%nMust abandon inbound intersite replication test for this site.
0xC000178C	***Error: Could find no servers that can take the ISTG role in site %1. Mustaboandon inbound intersite replication test for this site.	***Error: Could find no servers that can take the ISTG role in site %1. Mustaboandon inbound intersite replication test for this site.
0xC000178D	***Error: The current ISTG is down in site %1 and further dcdiag could notcontact any other servers in the site that could take the ISTG role. Ensurethere is at least one up DC. Must abandon inbound intersite replication testfor this site.	***Error: The current ISTG is down in site %1 and further dcdiag could notcontact any other servers in the site that could take the ISTG role. Ensurethere is at least one up DC. Must abandon inbound intersite replication testfor this site.
0xC000178E	***Error: The remote site %1, has no servers that can act as bridgeheads betweenthe %1 and the local site %2 for the writeable NC %3. Replication will not continueuntil this is resolved.	***Error: The remote site %1, has no servers that can act as bridgeheads betweenthe %1 and the local site %2 for the writeable NC %3. Replication will not continueuntil this is resolved.
0xC000178F	***Error: The remote site %1, has no servers that can act as bridgeheads betweenthe %1 and the local site %2 for the read only NC %3. Replication will not continueuntil this is resolved.	***Error: The remote site %1, has no servers that can act as bridgeheads betweenthe %1 and the local site %2 for the read only NC %3. Replication will not continueuntil this is resolved.
0xC0001790	***Error: The server %1 is missing its machine account. Try running with the /repairmachineaccount option.	***Error: The server %1 is missing its machine account. Try running with the /repairmachineaccount option.
0xC0001791	Attempting to repair %1's machine account.	Attempting to repair %1's machine account.
0xC0001792	***Error: Repair of missing machine account must be run locally on %1.	***Error: Repair of missing machine account must be run locally on %1.
0xC0001793	Found Directory Server %1 to help repair our account.	Found Directory Server %1 to help repair our account.
0xC0001794	***Error: Unable to find another Domain Controller to help repair our account.	***Error: Unable to find another Domain Controller to help repair our account.
0xC0001795	The machine account %1 was created on %2.	The machine account %1 was created on %2.
0xC0001796	The machine account %1 already existed on %2. This maybe the previous machineaccount whose deletion has not yet replicated to %2. If this is the case, you may need to run this tool again once the deletion has been propogated everywhere.You will know this is the case if the following demotion fails.	The machine account %1 already existed on %2. This maybe the previous machineaccount whose deletion has not yet replicated to %2. If this is the case, you may need to run this tool again once the deletion has been propogated everywhere.You will know this is the case if the following demotion fails.
0xC0001797	***Error: The machine account %1 could not be created on %2 because %3.	***Error: The machine account %1 could not be created on %2 because %3.
0xC0001798	***Error: The machine account %1 password could not be reset on %2 because %3. Please reset the account on %2.	***Error: The machine account %1 password could not be reset on %2 because %3. Please reset the account on %2.
0xC0001799	The Key Distribution Center has been stopped successfully.	The Key Distribution Center has been stopped successfully.
0xC000179A	***Error: The Key Distribution Center could not be stopped because %1.	***Error: The Key Distribution Center could not be stopped because %1.
0xC000179B	The replication from %1 succeeded.	The replication from %1 succeeded.
0xC000179C	***Error: The replication from %1 failed because %2.	***Error: The replication from %1 failed because %2.
0xC000179D	This Domain Controller's machine account has been successfully restored. Pleasedemote and promote this machine to ensure all state is correctly rebuilt.	This Domain Controller's machine account has been successfully restored. Pleasedemote and promote this machine to ensure all state is correctly rebuilt.
0xC000179E	***Error: The attempt to repair the machine account failed because %1.	***Error: The attempt to repair the machine account failed because %1.
0xC000179F	***Error: There is not enough memory to continue, dcdiag must abort.	***Error: There is not enough memory to continue, dcdiag must abort.
0xC00017A0	***Error: Trying to get the local computer name failed with following error: %1	***Error: Trying to get the local computer name failed with following error: %1
0xC00017A1	***Error: The machine could not attach to the DC because the credentials wereincorrect. Check your credentials or specify credentials with /u:\\ & /p:[|*|\"\"]	***Error: The machine could not attach to the DC because the credentials wereincorrect. Check your credentials or specify credentials with /u:\\ & /p:[|*|\"\"]
0xC00017A2	***Error: The machine, %1 could not be contacted, because of a bad net response. Check to make sure that this machine is a Directory Server.	***Error: The machine, %1 could not be contacted, because of a bad net response. Check to make sure that this machine is a Directory Server.
0xC00017A3	***Error: The DNS domain name, %1, is too long. A valid Windows DNS domain name can contain a maximum of %2!d! UTF-8 bytes.	***Error: The DNS domain name, %1, is too long. A valid Windows DNS domain name can contain a maximum of %2!d! UTF-8 bytes.
0xC00017A4	***Error: The syntax of the domain name, %1,is incorrect.DNS names may contain letters (a-z, A-Z), numbers (0-9), and hyphens, but no spaces. Periods (.) are used to separate domains. Each domain label can be no longer than %2!d! bytes. You may not have every label be a number.Example: domain-1.microsoft.com.	***Error: The syntax of the domain name, %1,is incorrect.DNS names may contain letters (a-z, A-Z), numbers (0-9), and hyphens, but no spaces. Periods (.) are used to separate domains. Each domain label can be no longer than %2!d! bytes. You may not have every label be a number.Example: domain-1.microsoft.com.
0xC00017A5	The name '%1' does not conform to Internet Domain Name Service specifications, although it conforms to Microsoft specifications.	The name '%1' does not conform to Internet Domain Name Service specifications, although it conforms to Microsoft specifications.
0xC00017A6	The DcPromo and RegisterInDNS tests can only be run locally, so the /s serverparameter is invalid.	The DcPromo and RegisterInDNS tests can only be run locally, so the /s serverparameter is invalid.
0xC00017A7	The DNS configuration is sufficient to allow this computer to be promoted as areplica domain controller in the %1 domain.	The DNS configuration is sufficient to allow this computer to be promoted as areplica domain controller in the %1 domain.
0xC00017A8	This computer cannot be promoted as a domain controller of the %1 domain becausethe following DNS names (A record) could not be resolved:%2Ask your network/DNS administrator to add the A records to DNS for thesecomputer.	This computer cannot be promoted as a domain controller of the %1 domain becausethe following DNS names (A record) could not be resolved:%2Ask your network/DNS administrator to add the A records to DNS for thesecomputer.
0xC00017A9	This computer cannot be promoted as a domain controller of the %1domain. This is because the DNS server used for DNS name resolution is notcompliant with Internet standards. Ask your network/DNS administrator toupgrade the DNS server or configure this computer to use adifferent DNS server for name resolution.	This computer cannot be promoted as a domain controller of the %1domain. This is because the DNS server used for DNS name resolution is notcompliant with Internet standards. Ask your network/DNS administrator toupgrade the DNS server or configure this computer to use adifferent DNS server for name resolution.
0xC00017AA	This computer cannot be promoted as a domain controller of the %1domain either because:	This computer cannot be promoted as a domain controller of the %1domain either because:
0xC00017AB	1. One or more DNS servers involved in the name resolution of the SRV recordfor the _ldap._tcp.dc._msdcs.%1 name are not responding or contain incorrectdelegation of the DNS zones; or	1. One or more DNS servers involved in the name resolution of the SRV recordfor the _ldap._tcp.dc._msdcs.%1 name are not responding or contain incorrectdelegation of the DNS zones; or
0xC00017AC	2. The DNS server that this computer is configured with contains incorrect roothints.	2. The DNS server that this computer is configured with contains incorrect roothints.
0xC00017AD	The list of such DNS servers may include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers authoritativefor the following zones: _msdcs.%1, %2 and the root zone.	The list of such DNS servers may include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers authoritativefor the following zones: _msdcs.%1, %2 and the root zone.
0xC00017AE	This computer cannot be promoted as a domain controller of the %1 domain.This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%1is not registered in DNS, or some zone from the following list of DNS zones doesn'tinclude delegation to its child zone: %2 and the root zone.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.	This computer cannot be promoted as a domain controller of the %1 domain.This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%1is not registered in DNS, or some zone from the following list of DNS zones doesn'tinclude delegation to its child zone: %2 and the root zone.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.
0xC00017AF	This computer cannot be promoted as a domain controller of the %1domain. This is because some of the DNS servers are configured torefuse queries from this computer or another DNS server that attempted a nameresolution. The list of DNS servers configured to refuse queries can includethe DNS servers with which this computer is configured for name resolution andthe DNS servers authoritative for the following zones: _msdcs.%1, %2 and theroot zone.	This computer cannot be promoted as a domain controller of the %1domain. This is because some of the DNS servers are configured torefuse queries from this computer or another DNS server that attempted a nameresolution. The list of DNS servers configured to refuse queries can includethe DNS servers with which this computer is configured for name resolution andthe DNS servers authoritative for the following zones: _msdcs.%1, %2 and theroot zone.
0xC00017B0	This computer cannot be promoted as a domain controller of the %1 domain becausethe SRV DNS records for _ldap._tcp.dc._msdcs.%1 are missing.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.	This computer cannot be promoted as a domain controller of the %1 domain becausethe SRV DNS records for _ldap._tcp.dc._msdcs.%1 are missing.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.
0xC00017B1	This computer cannot be promoted as a domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%1 are missing.	This computer cannot be promoted as a domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%1 are missing.
0xC00017B2	Verify that the network connections of this computer are configuredwith the correct IP addresses of the DNS servers to be used for name resolution.	Verify that the network connections of this computer are configuredwith the correct IP addresses of the DNS servers to be used for name resolution.
0xC00017B3	Dcdiag cannot reach a conclusive result because it cannot interpret the followingmessage that was returned: %1!d!.	Dcdiag cannot reach a conclusive result because it cannot interpret the followingmessage that was returned: %1!d!.
0xC00017B4	The DNS configuration is sufficient to allow this computer to be promoted as thefirst DC in the %1 Active Directory domain.	The DNS configuration is sufficient to allow this computer to be promoted as thefirst DC in the %1 Active Directory domain.
0xC00017B5	This computer cannot be promoted as a first domain controller of the %1 domainbecause the following DNS names (A record) could not be resolved: %2.Contact your DNS/network administrator to add the A records for thiscomputer to DNS.	This computer cannot be promoted as a first domain controller of the %1 domainbecause the following DNS names (A record) could not be resolved: %2.Contact your DNS/network administrator to add the A records for thiscomputer to DNS.
0xC00017B6	This computer cannot be promoted as a first domain controller of the %1domain. This is because the DNS server used for DNS name resolutionis not compliant with Internet standards. Ask your network/DNSadministrator to upgrade the DNS server or configure this computer to use adifferent DNS server for name resolution.	This computer cannot be promoted as a first domain controller of the %1domain. This is because the DNS server used for DNS name resolutionis not compliant with Internet standards. Ask your network/DNSadministrator to upgrade the DNS server or configure this computer to use adifferent DNS server for name resolution.
0xC00017B7	This computer cannot be promoted as a first domain controller of the %1domain, either because:	This computer cannot be promoted as a first domain controller of the %1domain, either because:
0xC00017B8	1. One or more DNS servers involved in the name resolution of the SRV recordfor the _ldap._tcp.dc._msdcs.%1 name are not responding or contain incorrectdelegation of the DNS zone(s); or	1. One or more DNS servers involved in the name resolution of the SRV recordfor the _ldap._tcp.dc._msdcs.%1 name are not responding or contain incorrectdelegation of the DNS zone(s); or
0xC00017B9	2. The DNS server that this computer is configured to use contains incorrectroot hints.	2. The DNS server that this computer is configured to use contains incorrectroot hints.
0xC00017BA	The list of such DNS servers might include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers authoritativefor the following zones: _msdcs.%1, %1, %2 and root zone.	The list of such DNS servers might include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers authoritativefor the following zones: _msdcs.%1, %1, %2 and root zone.
0xC00017BB	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%2is not registered in DNS, or some zone from the following list of DNS zones doesnot include delegation to its child zone: %3	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%2is not registered in DNS, or some zone from the following list of DNS zones doesnot include delegation to its child zone: %3
0xC00017BC	Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.	Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%1 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.
0xC00017BD	This computer cannot be promoted as a first domain controller of the %1domain because some of the DNS servers are configured to refuse queries fromthis computer or another DNS server that attempted a name resolution. Thelist of DNS servers configured to refuse queries can include the DNS serverswith which this computer is configured for name resolution and the DNS serversresponsible for the following: _msdcs.%2, %3 and the root zone.	This computer cannot be promoted as a first domain controller of the %1domain because some of the DNS servers are configured to refuse queries fromthis computer or another DNS server that attempted a name resolution. Thelist of DNS servers configured to refuse queries can include the DNS serverswith which this computer is configured for name resolution and the DNS serversresponsible for the following: _msdcs.%2, %3 and the root zone.
0xC00017BE	This computer cannot be promoted as a first domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%2 do not exist in DNS.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%2 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.	This computer cannot be promoted as a first domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%2 do not exist in DNS.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%2 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.
0xC00017C0	This computer cannot be promoted as the first domain controller of the %1 ActiveDirectory Domain due to failure of the DNS name (A record) resolution for the %2name(s). Contact your DNS/network administrator to add the A records for thiscomputer to DNS.	This computer cannot be promoted as the first domain controller of the %1 ActiveDirectory Domain due to failure of the DNS name (A record) resolution for the %2name(s). Contact your DNS/network administrator to add the A records for thiscomputer to DNS.
0xC00017C1	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because the DNS server used for DNS name resolution is notcompliant with Internet standards. Ask your network/DNS administrator toupgrade the DNS server or configure this computer to use adifferent DNS server for the name resolution.	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because the DNS server used for DNS name resolution is notcompliant with Internet standards. Ask your network/DNS administrator toupgrade the DNS server or configure this computer to use adifferent DNS server for the name resolution.
0xC00017C2	This computer cannot be promoted as a first domain controller of the %1 domain,either because:	This computer cannot be promoted as a first domain controller of the %1 domain,either because:
0xC00017C4	2. The DNS server that this computer is configured to use contains incorrect roothints.	2. The DNS server that this computer is configured to use contains incorrect roothints.
0xC00017C5	The list of such DNS servers might include the DNS servers this computer isconfigured to use for name resolution and the DNS servers authoritative forthe following zones:_msdcs.%1, %2 and the root zone.	The list of such DNS servers might include the DNS servers this computer isconfigured to use for name resolution and the DNS servers authoritative forthe following zones:_msdcs.%1, %2 and the root zone.
0xC00017C6	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%2is not registered in DNS, or some zone from the following list of DNS zonesdoes not include delegation to its child zone. The list of such zones mightinclude the following:	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because either the DNS SRV record for _ldap._tcp.dc._msdcs.%2is not registered in DNS, or some zone from the following list of DNS zonesdoes not include delegation to its child zone. The list of such zones mightinclude the following:
0xC00017C7	%1 and the root zone.	%1 and the root zone.
0xC00017C9	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because some of the DNS servers are configured to refusequeries from this computer or another DNS server that attempted a nameresolution. The list of DNS servers configured to refuse queries mightinclude the DNS servers that this computer is configured to use for nameresolution and the DNS servers responsible authoritative for the followingzones:	This computer cannot be promoted as a first domain controller of the domainnamed %1. This is because some of the DNS servers are configured to refusequeries from this computer or another DNS server that attempted a nameresolution. The list of DNS servers configured to refuse queries mightinclude the DNS servers that this computer is configured to use for nameresolution and the DNS servers responsible authoritative for the followingzones:
0xC00017CA	_msdcs.%1, %2 and the root zone.	_msdcs.%1, %2 and the root zone.
0xC00017CB	Contact your network/DNS administrator to fix this problem.	Contact your network/DNS administrator to fix this problem.
0xC00017CC	This computer cannot be promoted as the first domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%2 do not exist in DNS.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%2 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.	This computer cannot be promoted as the first domain controller of the %1 domainbecause the SRV DNS records for _ldap._tcp.dc._msdcs.%2 do not exist in DNS.Ask your network/DNS administrator to perform the following actions: To findout why the SRV record for _ldap._tcp.dc._msdcs.%2 is not registered in DNS,run the dcdiag command prompt tool with the command RegisterInDNS on thedomain controller that did not perform the registration.
0xC00017CD	Messages logged below this line indicate whether this domain controller willbe able to dynamically register DNS records required for the location of thisDC by other devices on the network. If any misconfiguration is detected, itmight prevent dynamic DNS registration of some records, but does not preventsuccessful completion of the Active Directory Domain Services Installation Wizard. However,we recommend fixing the reported problems now, unless you plan to manuallyupdate the DNS database.	Messages logged below this line indicate whether this domain controller willbe able to dynamically register DNS records required for the location of thisDC by other devices on the network. If any misconfiguration is detected, itmight prevent dynamic DNS registration of some records, but does not preventsuccessful completion of the Active Directory Domain Services Installation Wizard. However,we recommend fixing the reported problems now, unless you plan to manuallyupdate the DNS database.
0xC00017CE	No network connections were found to be configured with a preferred DNS server.This computer cannot be promoted unless the appropriate network connection isconfigured with a preferred DNS server. This configuration can be done manuallyor automatically by using DHCP.	No network connections were found to be configured with a preferred DNS server.This computer cannot be promoted unless the appropriate network connection isconfigured with a preferred DNS server. This configuration can be done manuallyor automatically by using DHCP.
0xC00017CF	If the IP settings are assigned to your computer automatically by using DHCP,contact your network/DNS administrator. The administrator should configure theDHCP server to set up the DHCP clients with the DNS servers used for name resolution. To check whether a network connection is automatically configured, click Start, Control Panel, Network Connections, ( in category view you need to select Network and Internet Connections before you can choose Network connections) Right-click the connection to be configured, click Properties, select Internet Protocol (TCP/IP), and then click Properties.	If the IP settings are assigned to your computer automatically by using DHCP,contact your network/DNS administrator. The administrator should configure theDHCP server to set up the DHCP clients with the DNS servers used for name resolution. To check whether a network connection is automatically configured, click Start, Control Panel, Network Connections, ( in category view you need to select Network and Internet Connections before you can choose Network connections) Right-click the connection to be configured, click Properties, select Internet Protocol (TCP/IP), and then click Properties.
0xC00017D0	You can also configure the network connections with the preferred DNS serverto be used for DNS name resolution. To do so, click Start, point to Settings,and then click Network and Dial-up connections. Right-click the connection tobe configured, click Properties, click Internet Protocol (TCP/IP), and thenclick Properties. Select Use the following DNS server addresses, and thentype the IP address of the preferred DNS server.	You can also configure the network connections with the preferred DNS serverto be used for DNS name resolution. To do so, click Start, point to Settings,and then click Network and Dial-up connections. Right-click the connection tobe configured, click Properties, click Internet Protocol (TCP/IP), and thenclick Properties. Select Use the following DNS server addresses, and thentype the IP address of the preferred DNS server.
0xC00017D1	This computer is configured with a primary DNS suffix different from theDNS name of the Active Directory domain. If this configuration is desired,disregard this message. After the computer is promoted to domain controller,you cannot modify the primary DNS suffix. To modify it before the promotion,right-click My Computer, click Properties, click the Network Identificationtab, click Properties, click More, and then update the primary DNS suffix.	This computer is configured with a primary DNS suffix different from theDNS name of the Active Directory domain. If this configuration is desired,disregard this message. After the computer is promoted to domain controller,you cannot modify the primary DNS suffix. To modify it before the promotion,right-click My Computer, click Properties, click the Network Identificationtab, click Properties, click More, and then update the primary DNS suffix.
0xC00017D2	The registry open operation failed with error %1!d!.	The registry open operation failed with error %1!d!.
0xC00017D3	The registry read operation failed with error %1!d!.	The registry read operation failed with error %1!d!.
0xC00017D4	This domain controller will not be able to dynamically register the DNSrecords necessary for the domain controller Locator. Please either enabledynamic DNS registration of all DNS records on this computer by settingDisableDynamicUpdate to 0x0 to the HKLM/System/CCS/Services/Tcpip/Parametersregkey, or allow registration of the domain controller specific records bysetting to REG_DWORD value DnsUpdateOnAllAdapters to 0x1 under theHKLM/CCS/Services/Netlogon/Parameters regkey or manually update the DNS withthe records specified after the reboot in the file%SystemRoot%\\System32\\Config\ etlogon.dns.	This domain controller will not be able to dynamically register the DNSrecords necessary for the domain controller Locator. Please either enabledynamic DNS registration of all DNS records on this computer by settingDisableDynamicUpdate to 0x0 to the HKLM/System/CCS/Services/Tcpip/Parametersregkey, or allow registration of the domain controller specific records bysetting to REG_DWORD value DnsUpdateOnAllAdapters to 0x1 under theHKLM/CCS/Services/Netlogon/Parameters regkey or manually update the DNS withthe records specified after the reboot in the file%SystemRoot%\\System32\\Config\ etlogon.dns.
0xC00017D5	This domain controller will not be able to dynamically register the DNSrecords necessary for the domain controller Locator. Please either enabledynamic DNS registration of all DNS records on this computer by checkingthe checkbox \"Register this connections addresses in DNS\" which you can findby going to Start - Settings - Network and Dial-up connections - right-clickthe connection to be configured - Properties - Advanced - DNS tab, or allowregistration of the domain controller specific records by setting to REG_DWORDvalue DnsUpdateOnAllAdapters to 0x1 under theHKLM/CCS/Services/Netlogon/Parameters regkey or manually update the DNS withthe records specified after the reboot in the file%SystemRoot%\\System32\\Config\ etlogon.dns.	This domain controller will not be able to dynamically register the DNSrecords necessary for the domain controller Locator. Please either enabledynamic DNS registration of all DNS records on this computer by checkingthe checkbox \"Register this connections addresses in DNS\" which you can findby going to Start - Settings - Network and Dial-up connections - right-clickthe connection to be configured - Properties - Advanced - DNS tab, or allowregistration of the domain controller specific records by setting to REG_DWORDvalue DnsUpdateOnAllAdapters to 0x1 under theHKLM/CCS/Services/Netlogon/Parameters regkey or manually update the DNS withthe records specified after the reboot in the file%SystemRoot%\\System32\\Config\ etlogon.dns.
0xC00017D6	DNS configuration is sufficient to allow this domain controller to dynamicallyregister the domain controller Locator records in DNS.	DNS configuration is sufficient to allow this domain controller to dynamicallyregister the domain controller Locator records in DNS.
0xC00017D7	Please verify that the network connections of this computer are configured withcorrect IP addresses of the DNS servers to be used for name resolution.If the DNS resolver is configured with its own IP address and the DNS serveris not running locally the DcPromo will be able to install and configurelocal DNS server, but it will be isolated from the existing DNS infrastructure(if any). To prevent this either configure local DNS resolver to point toexisting DNS server or manually configure the local DNS server (when running)with correct root hints.	Please verify that the network connections of this computer are configured withcorrect IP addresses of the DNS servers to be used for name resolution.If the DNS resolver is configured with its own IP address and the DNS serveris not running locally the DcPromo will be able to install and configurelocal DNS server, but it will be isolated from the existing DNS infrastructure(if any). To prevent this either configure local DNS resolver to point toexisting DNS server or manually configure the local DNS server (when running)with correct root hints.
0xC00017D8	This computer's Computer Name is set to the pre-Windows 2000 NetBIOS name.The Computer Name is the first label ofthe full DNS name of this computer. This DNS name cannot be added to the DNSdatabase because the Computer Name contains a space or dot.You must rename the computer so it can be registered in DNS. To do so,right-click My Computer, click Properties, click the NetworkIdentification tab, and then click properties and modify the Computer Name.	This computer's Computer Name is set to the pre-Windows 2000 NetBIOS name.The Computer Name is the first label ofthe full DNS name of this computer. This DNS name cannot be added to the DNSdatabase because the Computer Name contains a space or dot.You must rename the computer so it can be registered in DNS. To do so,right-click My Computer, click Properties, click the NetworkIdentification tab, and then click properties and modify the Computer Name.
0xC00017D9	This computer's Computer Name is set to the pre-Windows 2000 NetBIOS name.The Computer Name is the first label of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the Computer Namecontains a dot and is not valid.	This computer's Computer Name is set to the pre-Windows 2000 NetBIOS name.The Computer Name is the first label of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the Computer Namecontains a dot and is not valid.
0xC00017DA	It is crucial that the DNS computer name of this computer is registered.Since this computer was a domain controller, you cannot rename it. If thisis not a primary domain controller, you can cancel the Active Directory Domain ServicesInstallation Wizard, rename the computer, and then promote it to a domaincontroller, if necessary. To rename the computer, right-click My Computer,click Properties, click the Network Identification tab, and then clickProperties and modify the Computer Name.	It is crucial that the DNS computer name of this computer is registered.Since this computer was a domain controller, you cannot rename it. If thisis not a primary domain controller, you can cancel the Active Directory Domain ServicesInstallation Wizard, rename the computer, and then promote it to a domaincontroller, if necessary. To rename the computer, right-click My Computer,click Properties, click the Network Identification tab, and then clickProperties and modify the Computer Name.
0xC00017DB	If this is a primary domain controller you must promote it to a DomainController and after there is at least one more replica domain controller inthe domain, demote this computer to a non-DC server, rename it, and thenpromote it back to a domain controller by using the Active Directory Domain ServicesInstallation Wizard. On other domain controllers running Windows NT 4.0,modify the name, if necessary, prior to upgrading to Windows 2000.	If this is a primary domain controller you must promote it to a DomainController and after there is at least one more replica domain controller inthe domain, demote this computer to a non-DC server, rename it, and thenpromote it back to a domain controller by using the Active Directory Domain ServicesInstallation Wizard. On other domain controllers running Windows NT 4.0,modify the name, if necessary, prior to upgrading to Windows 2000.
0xC00017DC	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first portion of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the computer namecontains one or more of the following characters and is not valid:{|}~[\\]^':;?@!\"#$%^`()+/,* or a space. You must rename the computer so that it canbe registered in DNS. To do so, right-click My Computer, click Properties,click the Network Identification tab, and then click Properties and modifythe Computer Name	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first portion of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the computer namecontains one or more of the following characters and is not valid:{|}~[\\]^':;?@!\"#$%^`()+/,* or a space. You must rename the computer so that it canbe registered in DNS. To do so, right-click My Computer, click Properties,click the Network Identification tab, and then click Properties and modifythe Computer Name
0xC00017DD	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the computer namecontains one or more of the following characters and is not valid:{|}~[\\]^':;?@!\"#$%^`()+/,* or a space.	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.This DNS name cannot be added to the DNS database because the computer namecontains one or more of the following characters and is not valid:{|}~[\\]^':;?@!\"#$%^`()+/,* or a space.
0xC00017DE	It is crucial that you register the DNS computer name of this computer.Because this computer is a domain controller, you cannot rename it. If thisis not a primary domain controller, you can cancel the Active Directory Domain ServicesInstallation Wizard, rename the computer, and then promote it to a domaincontroller, if necessary. To rename the computer, right-click My Computer,click Properties, click the Network Identification tab, and then clickProperties and modify the Computer Name.	It is crucial that you register the DNS computer name of this computer.Because this computer is a domain controller, you cannot rename it. If thisis not a primary domain controller, you can cancel the Active Directory Domain ServicesInstallation Wizard, rename the computer, and then promote it to a domaincontroller, if necessary. To rename the computer, right-click My Computer,click Properties, click the Network Identification tab, and then clickProperties and modify the Computer Name.
0xC00017DF	If this is a primary domain controller you must promote it to a DomainController and after there is at least one more replica domain controllerin the domain, demote this computer to a non-DC server, rename it, and thenpromote it back to a domain controller by using the Active Directory Domain ServicesInstallation Wizard. On other domain controllers running Windows NT 4.0,modify the name, if necessary, prior to upgrading to Windows 2000.	If this is a primary domain controller you must promote it to a DomainController and after there is at least one more replica domain controllerin the domain, demote this computer to a non-DC server, rename it, and thenpromote it back to a domain controller by using the Active Directory Domain ServicesInstallation Wizard. On other domain controllers running Windows NT 4.0,modify the name, if necessary, prior to upgrading to Windows 2000.
0xC00017E0	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.Depending on the implementation and configuration of the DNS servers used inyour infrastructure, this DNS name might not be added to the DNS databasebecause the computer name contains the underscore character. Verify that theDNS server allows host DNS names (A records owner names) to contain theunderscore character, or rename the computer so that it can be registered inDNS. To do so, right-click My Computer, click Properties, click the NetworkIdentification tab, and then click Properties and modify the Computer Name.	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.Depending on the implementation and configuration of the DNS servers used inyour infrastructure, this DNS name might not be added to the DNS databasebecause the computer name contains the underscore character. Verify that theDNS server allows host DNS names (A records owner names) to contain theunderscore character, or rename the computer so that it can be registered inDNS. To do so, right-click My Computer, click Properties, click the NetworkIdentification tab, and then click Properties and modify the Computer Name.
0xC00017E1	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.Depending on the implementation and configuration of the DNS servers used inyour infrastructure, this DNS name might not be added to the DNS databasebecause the computer name contains the underscore character. Verify that theDNS server allows host DNS names (A records owner names) to contain theunderscore character, or rename the computer so that it can be registeredin DNS. To do so, right-click My Computer, click Properties, click the NetworkIdentification tab, and then click Properties and modify the Computer Name.	This computer's Computer Name is set to the pre-Windows NetBIOS name. TheComputer Name is the first label portion of the full DNS name of this computer.Depending on the implementation and configuration of the DNS servers used inyour infrastructure, this DNS name might not be added to the DNS databasebecause the computer name contains the underscore character. Verify that theDNS server allows host DNS names (A records owner names) to contain theunderscore character, or rename the computer so that it can be registeredin DNS. To do so, right-click My Computer, click Properties, click the NetworkIdentification tab, and then click Properties and modify the Computer Name.
0xC00017E2	Note: Default configuration of the Windows 2000 DNS server allows host namesto contain the underscore character.	Note: Default configuration of the Windows 2000 DNS server allows host namesto contain the underscore character.
0xC00017E3	If the DNS server cannot be configured to allow underscore characters in thehost names, then the computer name must be modified. Since this computer wasa domain controller, you cannot rename it. If this is not a primary domaincontroller, you can cancel the Active Directory Domain Services Installation Wizard, renamethe computer, and then promote it to a domain controller, if necessary. Torename the computer, right-click My Computer, click Properties, click theNetwork Identification tab, and then click Properties and modify the ComputerName.	If the DNS server cannot be configured to allow underscore characters in thehost names, then the computer name must be modified. Since this computer wasa domain controller, you cannot rename it. If this is not a primary domaincontroller, you can cancel the Active Directory Domain Services Installation Wizard, renamethe computer, and then promote it to a domain controller, if necessary. Torename the computer, right-click My Computer, click Properties, click theNetwork Identification tab, and then click Properties and modify the ComputerName.
0xC00017E5	This domain controller cannot register domain controller Locator DNS records.This is because either the DNS server with IP address %1 does not supportdynamic updates or the zone %2 is configured to prevent dynamic updates.	This domain controller cannot register domain controller Locator DNS records.This is because either the DNS server with IP address %1 does not supportdynamic updates or the zone %2 is configured to prevent dynamic updates.
0xC00017E6	In order for this domain controller to be located by other domain members anddomain controllers, the domain controller Locator DNS records must be addedto DNS. You have the following options:	In order for this domain controller to be located by other domain members anddomain controllers, the domain controller Locator DNS records must be addedto DNS. You have the following options:
0xC00017E7	1. Configure the %1 zone and the DNS server with IP address %2 to allow dynamicupdates. If the DNS server does not support dynamic updates, you might need toupgrade it.	1. Configure the %1 zone and the DNS server with IP address %2 to allow dynamicupdates. If the DNS server does not support dynamic updates, you might need toupgrade it.
0xC00017E8	2. Migrate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server).	2. Migrate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server).
0xC00017E9	2. Delegate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server).	2. Delegate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server).
0xC00017EA	3. Delegate the zones %1, %2, %3, and %4 to a DNS server that supportsdynamic updates (for example, a Windows 2000 DNS server); or	3. Delegate the zones %1, %2, %3, and %4 to a DNS server that supportsdynamic updates (for example, a Windows 2000 DNS server); or
0xC00017EB	4. Manually add to the DNS records specified in the%systemroot%\\system32\\config\ etlogon.dns file.	4. Manually add to the DNS records specified in the%systemroot%\\system32\\config\ etlogon.dns file.
0xC00017EC	Dcdiag detected that the DNS database contains the following zones:%1, %2, %3, and %4Dcdiag also detected that the following zones are configured to preventdynamic registration of DNS records:%5Following successful promotion of the domain controller, restart your computer.Then, allow dynamic updates to these zones or manually add the recordsspecified in the %systemroot%\\system32\\config\ etlogon.dns file.	Dcdiag detected that the DNS database contains the following zones:%1, %2, %3, and %4Dcdiag also detected that the following zones are configured to preventdynamic registration of DNS records:%5Following successful promotion of the domain controller, restart your computer.Then, allow dynamic updates to these zones or manually add the recordsspecified in the %systemroot%\\system32\\config\ etlogon.dns file.
0xC00017ED	Dcdiag detected that the DNS database contains the following zones: %1	Dcdiag detected that the DNS database contains the following zones: %1
0xC00017EE	Dcdiag also detected that the following zones are configured to preventdynamic registration of DNS records: %1	Dcdiag also detected that the following zones are configured to preventdynamic registration of DNS records: %1
0xC00017EF	Following successful promotion of the domain controller, restart your computer.Then allow dynamic updates to these zones or manually add the records specifiedin the %systemroot%\\system32\\config\ etlogon.dns file.	Following successful promotion of the domain controller, restart your computer.Then allow dynamic updates to these zones or manually add the records specifiedin the %systemroot%\\system32\\config\ etlogon.dns file.
0xC00017F1	We strongly recommend that you also create and configure the following zonesto allow dynamic DNS updates: %1	We strongly recommend that you also create and configure the following zonesto allow dynamic DNS updates: %1
0xC00017F2	If these zones cannot be created, restart your computer following successfulpromotion of the domain controller. Then, manually add the records specifiedin the %systemroot%\\system32\\config\ etlogon.dns file.	If these zones cannot be created, restart your computer following successfulpromotion of the domain controller. Then, manually add the records specifiedin the %systemroot%\\system32\\config\ etlogon.dns file.
0xC00017F3	If the DNS resolver is configured with its own IP address and the DNS serveris not running locally, the Active Directory Domain Services Installation Wizard can installand configure the local DNS server. However, if this server is not connectedto the network during domain controller promotion then admin needs toappropriately configure root hints of the local DNS server after thecompletion of the domain controller promotion.	If the DNS resolver is configured with its own IP address and the DNS serveris not running locally, the Active Directory Domain Services Installation Wizard can installand configure the local DNS server. However, if this server is not connectedto the network during domain controller promotion then admin needs toappropriately configure root hints of the local DNS server after thecompletion of the domain controller promotion.
0xC00017F4	This domain controller cannot register domain controller Locator DNS recordsbecause it cannot locate a DNS server authoritative for the zone %1. This isbecause:	This domain controller cannot register domain controller Locator DNS recordsbecause it cannot locate a DNS server authoritative for the zone %1. This isbecause:
0xC00017F5	1. One or more DNS servers involved in the name resolution of the %1 name arenot responding or contain incorrect delegation of the DNS zones; or	1. One or more DNS servers involved in the name resolution of the %1 name arenot responding or contain incorrect delegation of the DNS zones; or
0xC00017F7	The list of such DNS servers might include the DNS servers that this computeris configured to use for name resolution and the DNS servers authoritativefor the following zones: %1	The list of such DNS servers might include the DNS servers that this computeris configured to use for name resolution and the DNS servers authoritativefor the following zones: %1
0xC00017F8	Contact your networknetwork/DNS administrator to fix the problem. You can alsomanually add the records specified in the %systemroot%\\system32\\config\ etlogon.dnsfile.	Contact your networknetwork/DNS administrator to fix the problem. You can alsomanually add the records specified in the %systemroot%\\system32\\config\ etlogon.dnsfile.
0xC00017F9	The DNS configuration is sufficient to allow this computer to dynamicallyregister the A record corresponding to its DNS name.	The DNS configuration is sufficient to allow this computer to dynamicallyregister the A record corresponding to its DNS name.
0xC00017FA	This computer cannot register A type DNS records corresponding to its computerDNS name. This is because either the responsible authoritative DNS server withIP address %1 does not support dynamic updates or the zone %2 is configured toprevent dynamic updates.	This computer cannot register A type DNS records corresponding to its computerDNS name. This is because either the responsible authoritative DNS server withIP address %1 does not support dynamic updates or the zone %2 is configured toprevent dynamic updates.
0xC00017FB	In order for this domain controller to be located by other domain membersand domain controllers, the A record corresponding to its computer name mustbe added to DNS. You have the following options:	In order for this domain controller to be located by other domain membersand domain controllers, the A record corresponding to its computer name mustbe added to DNS. You have the following options:
0xC00017FC	1. Configure the %1 zone and the DNS server with IP address %2 to allowdynamic updates. If the DNS server does not support dynamic updates, youmight need to upgrade it;	1. Configure the %1 zone and the DNS server with IP address %2 to allowdynamic updates. If the DNS server does not support dynamic updates, youmight need to upgrade it;
0xC00017FD	2. Migrate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server); or	2. Migrate the %1 zone to a DNS server that supports dynamic updates (forexample, a Windows 2000 DNS server); or
0xC00017FE	3. Manually add to the DNS zone an A record that maps the computer's DNS nameto its IP address.	3. Manually add to the DNS zone an A record that maps the computer's DNS nameto its IP address.
0xC00017FF	This domain controller cannot register domain controller Locator DNS records.This is because it cannot locate a DNS server authoritative for the zone thatis responsible for the name %1. This is due to one of the following:	This domain controller cannot register domain controller Locator DNS records.This is because it cannot locate a DNS server authoritative for the zone thatis responsible for the name %1. This is due to one of the following:
0xC0001802	The list of such DNS servers might include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers responsible forthe following zones: %1	The list of such DNS servers might include the DNS servers with which thiscomputer is configured for name resolution and the DNS servers responsible forthe following zones: %1
0xC0001803	Contact your network/DNS administrator to fix this problem. You can alsomanually add the A record that maps the computer DNS name to its IP address.	Contact your network/DNS administrator to fix this problem. You can alsomanually add the A record that maps the computer DNS name to its IP address.
0xC0001804	The domain DNS name '%1' does not have a matching NS record. Please add thisrecord to your DNS server.	The domain DNS name '%1' does not have a matching NS record. Please add thisrecord to your DNS server.
0xC0001805	This domain controller cannot register domain controller Locator DNS records.This is because it cannot locate a DNS server authoritative for the zone %1.This is due to one of the following:	This domain controller cannot register domain controller Locator DNS records.This is because it cannot locate a DNS server authoritative for the zone %1.This is due to one of the following:
0xC0001806	Verify the correctness of the specified domain name and contact your network/DNSadministrator to fix the problem.	Verify the correctness of the specified domain name and contact your network/DNSadministrator to fix the problem.
0xC0001807	You can also manually add the records specified in the%%systemroot%%\\system32\\config\ etlogon.dns file.	You can also manually add the records specified in the%%systemroot%%\\system32\\config\ etlogon.dns file.
0xC0001808	Encountered exception 0x%1!x! attempting to format the event record! The event record data is bad!	Encountered exception 0x%1!x! attempting to format the event record! The event record data is bad!
0xC0001809	DnsUpdateTest returned %1!d!. The A record test is thus inconclusive.	DnsUpdateTest returned %1!d!. The A record test is thus inconclusive.
0xC000180A	It appears this partition (%1) failed to get completely created. This cross-ref (%2)is dead and should be removed from the directory.	It appears this partition (%1) failed to get completely created. This cross-ref (%2)is dead and should be removed from the directory.
0xC000180B	Currently the authoritative information for this cross-ref lies out of scope; Try running dcdiag with the /e option.	Currently the authoritative information for this cross-ref lies out of scope; Try running dcdiag with the /e option.
0xC000180C	LDAP Error 0x%1!x! (%1!d!).	LDAP Error 0x%1!x! (%1!d!).
0xC000180D	An unknown error occured.	An unknown error occured.
0xC000180E	The application directory partition %1 is missing a security descriptor reference domain. The administratorshould set the msDS-SD-Reference-Domain attribute on the cross reference object %2 to the DN of a domain.	The application directory partition %1 is missing a security descriptor reference domain. The administratorshould set the msDS-SD-Reference-Domain attribute on the cross reference object %2 to the DN of a domain.
0xC000180F	Kerberos Error.%nThe KDC could not find the SPN for the server %1.%nThis can be for several reasons:%0	Kerberos Error.%nThe KDC could not find the SPN for the server %1.%nThis can be for several reasons:%0
0xC0001810	%n(1) - The SPN is not registered on the KDC (usually %2). Check that the SPN is registered on at least one other server besides %1, and that replication is progressing between thisserver and the KDC. The tool repadmin/syncall can be used for this purpose.%n(2) - This server could be a deleted server (and deleted DSA object), and this deletionhas not replicated across the enterprise yet. This will rectify itself within the generalreplication latency plus the latency of the KCC. Should be less than a day.%n(3) - It's possible that this server was reclaimed, but it's DSA object was not deletedand an old DNS record representing the server is present. This can result in this errorfor the duration of a DNS record lease. Often about 2 weeks. To fix this, pleaseclean up the DSA's metadata with ntdsutil.%n(4) - Finally, it's possible that this server has acquired a new IP address, the server'sold IP address has been reused, and DNS hasn't been updated to reflect the new IP address.If this problem persists, stop and restart the \"Net Logon\" service on %1, and delete theold DNS record.	%n(1) - The SPN is not registered on the KDC (usually %2). Check that the SPN is registered on at least one other server besides %1, and that replication is progressing between thisserver and the KDC. The tool repadmin/syncall can be used for this purpose.%n(2) - This server could be a deleted server (and deleted DSA object), and this deletionhas not replicated across the enterprise yet. This will rectify itself within the generalreplication latency plus the latency of the KCC. Should be less than a day.%n(3) - It's possible that this server was reclaimed, but it's DSA object was not deletedand an old DNS record representing the server is present. This can result in this errorfor the duration of a DNS record lease. Often about 2 weeks. To fix this, pleaseclean up the DSA's metadata with ntdsutil.%n(4) - Finally, it's possible that this server has acquired a new IP address, the server'sold IP address has been reused, and DNS hasn't been updated to reflect the new IP address.If this problem persists, stop and restart the \"Net Logon\" service on %1, and delete theold DNS record.
0xC0001811	Kerberos Error.%nIt appears that server %1 has a stale DNS entry for %3. This is causing %2 to be unable toreplicate with server %1. If this problem persists please ensure that server %1 is still anactive DC. If so please stop and restart the \"Net Logon\" service on %1, and delete the oldDNS record for %3.	Kerberos Error.%nIt appears that server %1 has a stale DNS entry for %3. This is causing %2 to be unable toreplicate with server %1. If this problem persists please ensure that server %1 is still anactive DC. If so please stop and restart the \"Net Logon\" service on %1, and delete the oldDNS record for %3.
0xC0001812	It appears this partition (%1) has an empty replica set. This partition should be re-instantiatedon the last replica to hold this NC, or removed from the directory.	It appears this partition (%1) has an empty replica set. This partition should be re-instantiatedon the last replica to hold this NC, or removed from the directory.
0xC0001813	[%1!d!] Problem: Delete Mangled Value	[%1!d!] Problem: Delete Mangled Value
0xC0001814	[%1!d!] Problem: Conflict Mangled Value	[%1!d!] Problem: Conflict Mangled Value
0xC0001815	Base Object: %1%nBase Object Description: \"Server Object\"%nValue Object Attribute: %2%nValue Object Description: \"DC Account Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one DC Account Objects forthis DC, and if so clean up the older duplicates.%n	Base Object: %1%nBase Object Description: \"Server Object\"%nValue Object Attribute: %2%nValue Object Description: \"DC Account Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one DC Account Objects forthis DC, and if so clean up the older duplicates.%n
0xC0001816	Base Object: %1%nBase Object Description: \"DC Account Object\"%nValue Object Attribute: %2%nValue Object Description: \"SYSVOL FRS Member Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one SYSVOL FRS Member Object forthis DC, and if so clean up the older duplicates.%n	Base Object: %1%nBase Object Description: \"DC Account Object\"%nValue Object Attribute: %2%nValue Object Description: \"SYSVOL FRS Member Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one SYSVOL FRS Member Object forthis DC, and if so clean up the older duplicates.%n
0xC0001817	Base Object: %1%nBase Object Description: \"DSA Object\"%nValue Object Attribute: %2%nValue Object Description: \"SYSVOL FRS Member Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one SYSVOL FRS Member Object forthis DC, and if so clean up the older duplicates.%n	Base Object: %1%nBase Object Description: \"DSA Object\"%nValue Object Attribute: %2%nValue Object Description: \"SYSVOL FRS Member Object\"%nMangled Value: %3%nRecommended Action: Check that there is not more than one SYSVOL FRS Member Object forthis DC, and if so clean up the older duplicates.%n
0xC0001818	Some objects relating to the DC %1 have problems:	Some objects relating to the DC %1 have problems:
0xC0001819	The system object reference attribute %1 on object %2 did not point to an object that had a valid back link.	The system object reference attribute %1 on object %2 did not point to an object that had a valid back link.
0xC000181A	LDAP Error 0x%1!x! (%1!d!) - %2.	LDAP Error 0x%1!x! (%1!d!) - %2.
0xC000181B	The following problems were found while verifying various important DN references. Note, that these problems can be reported because of latency in replication. So follow up to resolve thefollowing problems, only if the same problem is reported on all DCs for a given domain or if the problem persists after replication has had reasonable time to replicate changes.	The following problems were found while verifying various important DN references. Note, that these problems can be reported because of latency in replication. So follow up to resolve thefollowing problems, only if the same problem is reported on all DCs for a given domain or if the problem persists after replication has had reasonable time to replicate changes.
0xC000181C	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"Server Object\"%nValue Object Attribute: %3%nValue Object Description: \"DC Account Object\"%nRecommended Action: This could hamper authentication (and thus replication, etc). Check if this server is deleted, and if so clean up this DCs Account Object. If the problem persists and this is not a deleted DC, authorativelyrestore the DSA object from a good copy, for example the DSA on the DSA'shome server.%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"Server Object\"%nValue Object Attribute: %3%nValue Object Description: \"DC Account Object\"%nRecommended Action: This could hamper authentication (and thus replication, etc). Check if this server is deleted, and if so clean up this DCs Account Object. If the problem persists and this is not a deleted DC, authorativelyrestore the DSA object from a good copy, for example the DSA on the DSA'shome server.%n
0xC000181D	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DC Account Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"Server Object\"%nRecommended Action: Check if this server is deleted, and if so clean up this DCsAccount Object.%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DC Account Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"Server Object\"%nRecommended Action: Check if this server is deleted, and if so clean up this DCsAccount Object.%n
0xC000181E	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DC Account Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"SYSVOL FRS Member Object\"%nRecommended Action: See Knowledge Base Article: Q312862%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DC Account Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"SYSVOL FRS Member Object\"%nRecommended Action: See Knowledge Base Article: Q312862%n
0xC000181F	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DSA Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"SYSVOL FRS Member Object\"%nRecommended Action: See Knowledge Base Article: Q312862%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"DSA Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"SYSVOL FRS Member Object\"%nRecommended Action: See Knowledge Base Article: Q312862%n
0xC0001820	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"SYSVOL FRS Member Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"DC Account Object\"%nRecommended Action: Check if this server is deleted, and if so cleanup this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"SYSVOL FRS Member Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"DC Account Object\"%nRecommended Action: Check if this server is deleted, and if so cleanup this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article: Q312862%n
0xC0001821	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"SYSVOL FRS Member Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"DSA Object\"%nRecommended Action: Check if this server is deleted, and if so cleanup this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862%n	[%1!d!] Problem: Missing Expected Value%nBase Object: %2%nBase Object Description: \"SYSVOL FRS Member Object\"%nValue Object Attribute Name: %3%nValue Object Description: \"DSA Object\"%nRecommended Action: Check if this server is deleted, and if so cleanup this DCs SYSVOL FRS Member Object. Also see Knowledge Base Article Q312862%n
0xC0001822	There are two FRS SysVol Replica sets! This error should be resolved.	There are two FRS SysVol Replica sets! This error should be resolved.
0xC0001823	[%1!d!] Problem: Not enough master NCs%nDSA Object: %2%nRecommended Action: Every DSA object should have 3 Master NCs (Partitions). If the problem persists, authoratively restore the DSA object from a goodcopy, for example the DSA on the DSA's home server.%n	[%1!d!] Problem: Not enough master NCs%nDSA Object: %2%nRecommended Action: Every DSA object should have 3 Master NCs (Partitions). If the problem persists, authoratively restore the DSA object from a goodcopy, for example the DSA on the DSA's home server.%n
0xC0001824	The corresponding flag bits are missing from the computer object'sUser-Account-Control attribute. You can re-run this command andinclude the /FixMachineAccount option to attempt a repair.	The corresponding flag bits are missing from the computer object'sUser-Account-Control attribute. You can re-run this command andinclude the /FixMachineAccount option to attempt a repair.
0xC0001825	* %1 is not a server trust account	* %1 is not a server trust account
0xC0001826	* %1 is not trusted for account delegation	* %1 is not trusted for account delegation
0xC0001827	* %1 does not have computer as its objectClass	* %1 does not have computer as its objectClass
0xC0001828	Computer account flags repaired.	Computer account flags repaired.
0xC0001829	Cannot repair the computer account flags. The error is %1!d!	Cannot repair the computer account flags. The error is %1!d!
0xC000182A	A cross-ref has a delete mangled nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThis condition is caused by a partition with the same name being demoted and promoted rapidly on Windows 2000 systems. This condition may be fixed by booting to DS Repairmode and running the Windows 2000 SP3 ntdsutil semantic database analysis tool.	A cross-ref has a delete mangled nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThis condition is caused by a partition with the same name being demoted and promoted rapidly on Windows 2000 systems. This condition may be fixed by booting to DS Repairmode and running the Windows 2000 SP3 ntdsutil semantic database analysis tool.
0xC000182B	A cross-ref has a conflict mangled nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThis condition is caused by a partition with the same name being demoted and promoted rapidly on Windows 2000 systems. This condition may be fixed by booting to DS Repairmode and running the Windows 2000 SP3 ntdsutil semantic database analysis tool.	A cross-ref has a conflict mangled nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThis condition is caused by a partition with the same name being demoted and promoted rapidly on Windows 2000 systems. This condition may be fixed by booting to DS Repairmode and running the Windows 2000 SP3 ntdsutil semantic database analysis tool.
0xC000182C	This cross-ref has a non-standard dNSRoot attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nBad dNSRoot attribute: %3%nCheck with your network administrator to make sure this dNSRoot attribute is correct, andif not please change the attribute to the value below.%n dNSRoot should be: %4	This cross-ref has a non-standard dNSRoot attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nBad dNSRoot attribute: %3%nCheck with your network administrator to make sure this dNSRoot attribute is correct, andif not please change the attribute to the value below.%n dNSRoot should be: %4
0xC000182D	This cross-ref has an invalid nETBIOSName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nBad nETBIOSName attribute: %3%nCheck with your network administrator to make sure this nETBIOSName attribute is correct, andif consider correcting the attribute, or remove this partition.	This cross-ref has an invalid nETBIOSName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nBad nETBIOSName attribute: %3%nCheck with your network administrator to make sure this nETBIOSName attribute is correct, andif consider correcting the attribute, or remove this partition.
0xC000182E	A cross-ref has a NULL GUID in it's nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nIf this Partition is not a new tree partition, then consider removing this partitionand/or cross-ref from the enterprise. It is normal for a separate-tree root domaincrossref ncName to not have a guid temporarily after dcpromo of a Windows 2000 domaincontroller. A Windows Server 2003 domain always has a guid. Without the guid,the KCC will not honor the cross ref and replicate in a replica of the new domain.Please allow time for knowledge of the guid to replicate out to the forest. If the guid is still missing, please verify that a replication path exists from the recentlypromoted domain controller to the rest of the forest.	A cross-ref has a NULL GUID in it's nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nIf this Partition is not a new tree partition, then consider removing this partitionand/or cross-ref from the enterprise. It is normal for a separate-tree root domaincrossref ncName to not have a guid temporarily after dcpromo of a Windows 2000 domaincontroller. A Windows Server 2003 domain always has a guid. Without the guid,the KCC will not honor the cross ref and replicate in a replica of the new domain.Please allow time for knowledge of the guid to replicate out to the forest. If the guid is still missing, please verify that a replication path exists from the recentlypromoted domain controller to the rest of the forest.
0xC000182F	A domain cross-ref has no SID in it's nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThe SID has not replicated into this DC. Check that replication is succeeding betweenthe first DC in the Domain who's SID is missing and this DC.If the Domain was created with a Windows 2000 DC and all member DCs of the domain areunable to replicate outbound because of Schema Mismatch errors, then all member DCs will needto have Window's re-installed and the Domain will need to be manually removed using meta data cleanup in ntdsutil.exe.If the Domain was created with a Windows 2000 DC, then replication can be blocked from one DCto another with \"Replication Access Denied\". If replication isn't succeeding between the first DCin the Domain who's SID is missing and this DC due to a different domain cross-ref missinga domain SID in it's nCName somewhere else in the forest, then you may need to manuallyreconfigure the topology to bypass the blocking replication.	A domain cross-ref has no SID in it's nCName attribute.%nCross-ref DN: %2%nnCName attribute (Partition name): %1%nThe SID has not replicated into this DC. Check that replication is succeeding betweenthe first DC in the Domain who's SID is missing and this DC.If the Domain was created with a Windows 2000 DC and all member DCs of the domain areunable to replicate outbound because of Schema Mismatch errors, then all member DCs will needto have Window's re-installed and the Domain will need to be manually removed using meta data cleanup in ntdsutil.exe.If the Domain was created with a Windows 2000 DC, then replication can be blocked from one DCto another with \"Replication Access Denied\". If replication isn't succeeding between the first DCin the Domain who's SID is missing and this DC due to a different domain cross-ref missinga domain SID in it's nCName somewhere else in the forest, then you may need to manuallyreconfigure the topology to bypass the blocking replication.
0xC0001830	There are warning or error events within the last 24 hours after the SYSVOL has beenshared. Failing SYSVOL replication problems may cause Group Policy problems.	There are warning or error events within the last 24 hours after the SYSVOL has beenshared. Failing SYSVOL replication problems may cause Group Policy problems.
0xC0001831	Dcdiag could not locate %1 in the dcdiag's cache of servers. Try running this dcdiag test against this server, to avoid any problems caused by replication latency.	Dcdiag could not locate %1 in the dcdiag's cache of servers. Try running this dcdiag test against this server, to avoid any problems caused by replication latency.
0xC0001832	The registry lookup failed to determine the state of the SYSVOL. The error returned was 0x%1!x! \"%2\". Check the FRS event log to see if the SYSVOL has successfully beenshared.	The registry lookup failed to determine the state of the SYSVOL. The error returned was 0x%1!x! \"%2\". Check the FRS event log to see if the SYSVOL has successfully beenshared.
0xC0001833	The SysVol is not ready. This can cause the DC to not advertise itself as a DC fornetlogon after dcpromo. Also trouble with FRS SysVol replication can cause GroupPolicy problems. Check the FRS event log on this DC.	The SysVol is not ready. This can cause the DC to not advertise itself as a DC fornetlogon after dcpromo. Also trouble with FRS SysVol replication can cause GroupPolicy problems. Check the FRS event log on this DC.
0xC0001834	Could not find any Sites in the directory, dcdiag could not continue.	Could not find any Sites in the directory, dcdiag could not continue.
0xC0001835	REPLICATION-RECEIVED LATENCY WARNING%nSource site: %1%nCurrent time: %2!S!%nLast update time: %3!S!%nCheck if source site has an elected ISTG running.%nCheck replication from source site to this server.	REPLICATION-RECEIVED LATENCY WARNING%nSource site: %1%nCurrent time: %2!S!%nLast update time: %3!S!%nCheck if source site has an elected ISTG running.%nCheck replication from source site to this server.
0xC0001836	***Error: Couldn't retreive the Up-to-dateness vector data from %1 for site %2, error 0x%3!x! \"%4\"%nMust abandon inbound intersite replication test for this site.	***Error: Couldn't retreive the Up-to-dateness vector data from %1 for site %2, error 0x%3!x! \"%4\"%nMust abandon inbound intersite replication test for this site.
0xC0001837	***[Message tring is truncated because of large size].	***[Message tring is truncated because of large size].
0xC0001838	Syntax Error: Please use /DnsDomain:to specify the domain.See the help screen (/?) for more information.	Syntax Error: Please use /DnsDomain:to specify the domain.See the help screen (/?) for more information.
0xC0001839	Checks whether each DSA is advertising itself, and whetherit is advertising itself as having the capabilities of a DSA.	Checks whether each DSA is advertising itself, and whetherit is advertising itself as having the capabilities of a DSA.
0xC000183A	This test checks that all application directorypartitions have appropriate security descriptor referencedomains.	This test checks that all application directorypartitions have appropriate security descriptor referencedomains.
0xC000183B	Locates security errors (or those possibly security related)and performs the initial diagnosis of the problem.Optional Arguments:/ReplSource: to target a specific source,regardless of it's error status. Need not be a current partner.	Locates security errors (or those possibly security related)and performs the initial diagnosis of the problem.Optional Arguments:/ReplSource: to target a specific source,regardless of it's error status. Need not be a current partner.
0xC000183C	Tests whether DSAs are DNS registered, pingeable, and have LDAP/RPC connectivity.	Tests whether DSAs are DNS registered, pingeable, and have LDAP/RPC connectivity.
0xC000183D	This test looks for cross-refs that are in someway invalid.	This test looks for cross-refs that are in someway invalid.
0xC000183E	Check for servers that won't receive replicationsbecause its partners are down	Check for servers that won't receive replicationsbecause its partners are down
0xC000183F	Tests the existing DNS infrastructure for promotion to domaincontroller. If the infrastructure is sufficient, the computercan be promoted to domain controller in a domain specified in. Reports whether anymodifications to the existing DNS infrastructure are required.Required argument:/DnsDomain:One of the following arguments is required:/NewForest/NewTree/ChildDomain/ReplicaDCIf NewTree is specified, then the ForestRoot argument isrequired:/ForestRoot:	Tests the existing DNS infrastructure for promotion to domaincontroller. If the infrastructure is sufficient, the computercan be promoted to domain controller in a domain specified in. Reports whether anymodifications to the existing DNS infrastructure are required.Required argument:/DnsDomain:One of the following arguments is required:/NewForest/NewTree/ChildDomain/ReplicaDCIf NewTree is specified, then the ForestRoot argument isrequired:/ForestRoot:
0xC0001840	This test checks the health of DNS settings on a DC.It just gathers data for the DnsValidationEnterprise test,so it doesn't print anything.	This test checks the health of DNS settings on a DC.It just gathers data for the DnsValidationEnterprise test,so it doesn't print anything.
0xC0001841	This test checks the health of DNS settingsfor the whole enterprise. Sub tests can be run individuallyusing the switches below. By default, all tests exceptexternal name resolution are run) /DnsBasic (basic tests, can't be skipped) /DnsForwarders (forwarders and root hints tests) /DnsDelegation (delegations tests) /DnsDynamicUpdate (dynamic update tests) /DnsRecordRegistration (records registration tests) /DnsResolveExtName (external name resolution test) /DnsAll (includes all tests above) /DnsInternetName: (for test /DnsResolveExtName) (default is www.microsoft.com)	This test checks the health of DNS settingsfor the whole enterprise. Sub tests can be run individuallyusing the switches below. By default, all tests exceptexternal name resolution are run) /DnsBasic (basic tests, can't be skipped) /DnsForwarders (forwarders and root hints tests) /DnsDelegation (delegations tests) /DnsDynamicUpdate (dynamic update tests) /DnsRecordRegistration (records registration tests) /DnsResolveExtName (external name resolution test) /DnsAll (includes all tests above) /DnsInternetName: (for test /DnsResolveExtName) (default is www.microsoft.com)
0xC0001842	This test checks to see if there are any operation errorsin the file replication system (FRS). Failing replicationof the SYSVOL share, can cause Policy problems.	This test checks to see if there are any operation errorsin the file replication system (FRS). Failing replicationof the SYSVOL share, can cause Policy problems.
0xC0001843	This test checks to see if there are any operation errorsin the DFS.	This test checks to see if there are any operation errorsin the DFS.
0xC0001844	This test checks that the SYSVOL is ready.	This test checks that the SYSVOL is ready.
0xC0001845	This is the same test as SysVolCheck. Keep it for backward compatibility.	This is the same test as SysVolCheck. Keep it for backward compatibility.
0xC0001846	Checks that global role-holders are known, can belocated, and are responding.	Checks that global role-holders are known, can belocated, and are responding.
0xC0001847	This is the same test as LocatorCheck. Keep it for backward compatibility.	This is the same test as LocatorCheck. Keep it for backward compatibility.
0xC0001848	Checks for failures that would prevent or temporarilyhold up intersite replication.	Checks for failures that would prevent or temporarilyhold up intersite replication.
0xC0001849	This test checks that the Knowledge Consistency Checkeris completing without errors.	This test checks that the Knowledge Consistency Checkeris completing without errors.
0xC000184A	Check whether the DSA thinks it knows the roleholders, and prints these roles out in verbose mode.	Check whether the DSA thinks it knows the roleholders, and prints these roles out in verbose mode.
0xC000184B	Check to see if the Machine Account has the properinformation. Use /RecreateMachineAccount to attempt a repairif the local machine account is missing. Use /FixMachineAccountif the machine account flags are incorrect.	Check to see if the Machine Account has the properinformation. Use /RecreateMachineAccount to attempt a repairif the local machine account is missing. Use /FixMachineAccountif the machine account flags are incorrect.
0xC000184C	Checks that the security descriptosrs on the namingcontext heads have appropriate permissions for replication.	Checks that the security descriptosrs on the namingcontext heads have appropriate permissions for replication.
0xC000184D	Checks that the appropriate logon priviledges allowreplication to proceed.	Checks that the appropriate logon priviledges allowreplication to proceed.
0xC000184E	Check that Machine Account (AD only) and DSA objects havereplicated. Use /objectdn: with /n: to specify anadditional object to check.	Check that Machine Account (AD only) and DSA objects havereplicated. Use /objectdn: with /n: to specify anadditional object to check.
0xC000184F	See if we have secure channels from all of theDC's in the domain the domains specified by /testdomain:./nositerestriction will prevent the test frombeing limited to the DC's in the site.	See if we have secure channels from all of theDC's in the domain the domains specified by /testdomain:./nositerestriction will prevent the test frombeing limited to the DC's in the site.
0xC0001850	Tests whether this directory server can register thedirectory Server Locator DNS records. These records must bepresent in DNS in order for other computers to locate thisdirectory server for the domain. Reports whether any modifications to the existing DNSinfrastructure are required.Required argument:/DnsDomain:	Tests whether this directory server can register thedirectory Server Locator DNS records. These records must bepresent in DNS in order for other computers to locate thisdirectory server for the domain. Reports whether any modifications to the existing DNSinfrastructure are required.Required argument:/DnsDomain:
0xC0001851	Checks for timely replication between directory servers.	Checks for timely replication between directory servers.
0xC0001852	Check to see if RID master is accessable and to see ifit contains the proper information.	Check to see if RID master is accessable and to see ifit contains the proper information.
0xC0001853	Check to see if appropriate supporting services are running.	Check to see if appropriate supporting services are running.
0xC0001854	This test checks that the system is running without errors.	This test checks that the system is running without errors.
0xC0001855	Checks that the generated topology is fully connected forall DSAs.	Checks that the generated topology is fully connected forall DSAs.
0xC0001856	This test verifys that certain systemreferences are intact for the FRS and Replicationinfrastructure across all objects in the enterpriseon each DSA.	This test verifys that certain systemreferences are intact for the FRS and Replicationinfrastructure across all objects in the enterpriseon each DSA.
0xC0001857	This test verifys that certain system referencesare intact for the FRS and Replication infrastructure.	This test verifys that certain system referencesare intact for the FRS and Replication infrastructure.
0xC0001858	This test verifys that all application directorypartitions are fully instantiated on all replica servers.	This test verifys that all application directorypartitions are fully instantiated on all replica servers.
0xC0001859	dump internal info.	dump internal info.

File Name:	dcdiag.exe.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-d..ne-dsdiag.resources_31bf3856ad364e35_10.0.15063.0_en-us_5674d7963632ea6c\
File Size:	179 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	182784
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Executable application
File Subtype:	0
Language Code:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	Active Directory Domain Services / Lightweight Directory Services diagnosis utility
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	dcdiag.exe
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	dcdiag.exe.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Directory:	%WINDIR%\WinSxS\x86_microsoft-windows-d..ne-dsdiag.resources_31bf3856ad364e35_10.0.15063.0_en-us_fa563c127dd57936\

dcdiag.exe.mui is Multilingual User Interface resource file that contain English (U.S.) language for file dcdiag.exe (Active Directory Domain Services / Lightweight Directory Services diagnosis utility).

File Description:	Active Directory Domain Services / Lightweight Directory Services diagnosis utility
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	dcdiag.exe
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	dcdiag.exe.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x409, 1200