Description of Windows System Error Codes

599

Description of Windows System Error Codes – This post is a basically a description of Windows System Error Codes. Sometimes all you get is the system error code but nothing about what the code means. If you the description of that error code then troubleshooting becomes easy. The Windows System Error Codes are very broad. Each one can occur in one of many hundreds of locations in the system. If you are installing an third party application you should contact customer support of that software to know what error codes mean. To obtain support for a Microsoft product, go to http://support.microsoft.com. Please note that the descriptions of these codes cannot be very specific. Use of these codes requires some amount of investigation and analysis.

Description of Windows System Error Codes

The table below describes system Exit or Error codes when a task is executed. The description of codes may help in identifying and troubleshooting the issues.

CodeDescription
0The operation completed successfully.
1Incorrect function.
2The system cannot find the file specified.
3The system cannot find the path specified.
4The system cannot open the file.
5Access is denied.
6The handle is invalid.
7The storage control blocks were destroyed.
8Not enough storage is available to process this command.
9The storage control block address is invalid.
10The environment is incorrect.
11An attempt was made to load a program with an incorrect format.
12The access code is invalid.
13The data is invalid.
14Not enough storage is available to complete this operation.
15The system cannot find the drive specified.
16The directory cannot be removed.
17The system cannot move the file to a different disk drive.
18There are no more files.
19The media is write protected.
20The system cannot find the device specified.
21The device is not ready.
22The device does not recognize the command.
23Data error (cyclic redundancy check).
24The program issued a command but the command length is incorrect.
25The drive cannot locate a specific area or track on the disk.
26The specified disk or diskette cannot be accessed.
27The drive cannot find the sector requested.
28The printer is out of paper.
29The system cannot write to the specified device.
30The system cannot read from the specified device.
31A device attached to the system is not functioning.
32The process cannot access the file because it is being used by another process.
33The process cannot access the file because another process has locked a portion of the file.
34The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1.
36Too many files opened for sharing.
38Reached the end of the file.
39The disk is full.
50The request is not supported.
51Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.
52You were not connected because a duplicate name exists on the network. Go to System in the Control Panel to change the computer name and try again.
53The network path was not found.
54The network is busy.
55The specified network resource or device is no longer available.
56The network BIOS command limit has been reached.
57A network adapter hardware error occurred.
58The specified server cannot perform the requested operation.
59An unexpected network error occurred.
60The remote adapter is not compatible.
61The printer queue is full.
62Space to store the file waiting to be printed is not available on the server.
63Your file waiting to be printed was deleted.
64The specified network name is no longer available.
65Network access is denied.
66The network resource type is not correct.
67The network name cannot be found.
68The name limit for the local computer network adapter card was exceeded.
69The network BIOS session limit was exceeded.
70The remote server has been paused or is in the process of being started.
71No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
72The specified printer or disk device has been paused.
80The file exists.
82The directory or file cannot be created.
83Fail on INT 24.
84Storage to process this request is not available.
85The local device name is already in use.
86The specified network password is not correct.
87The parameter is incorrect.
88A write fault occurred on the network.
89The system cannot start another process at this time.
100Cannot create another system semaphore.
101The exclusive semaphore is owned by another process.
102The semaphore is set and cannot be closed.
103The semaphore cannot be set again.
104Cannot request exclusive semaphores at interrupt time.
105The previous ownership of this semaphore has ended.
106Insert the diskette for drive %1.
107The program stopped because an alternate diskette was not inserted.
108The disk is in use or locked by another process.
109The pipe has been ended.
110The system cannot open the device or file specified.
111The file name is too long.
112There is not enough space on the disk.
113No more internal file identifiers available.
114The target internal file identifier is incorrect.
117The IOCTL call made by the application program is not correct.
118The verify-on-write switch parameter value is not correct.
119The system does not support the command requested.
120This function is not supported on this system.
121The semaphore timeout period has expired.
122The data area passed to a system call is too small.
123The filename, directory name, or volume label syntax is incorrect.
124The system call level is not correct.
125The disk has no volume label.
126The specified module could not be found.
127The specified procedure could not be found.
128There are no child processes to wait for.
129The %1 application cannot be run in Win32 mode.
130Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.
131An attempt was made to move the file pointer before the beginning of the file.
132The file pointer cannot be set on the specified device or file.
133A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
134An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.
135An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted.
136The system tried to delete the JOIN of a drive that is not joined.
137The system tried to delete the substitution of a drive that is not substituted.
138The system tried to join a drive to a directory on a joined drive.
139The system tried to substitute a drive to a directory on a substituted drive.
140The system tried to join a drive to a directory on a substituted drive.
141The system tried to SUBST a drive to a directory on a joined drive.
142The system cannot perform a JOIN or SUBST at this time.
143The system cannot join or substitute a drive to or for a directory on the same drive.
144The directory is not a subdirectory of the root directory.
145The directory is not empty.
146The path specified is being used in a substitute.
147Not enough resources are available to process this command.
148The path specified cannot be used at this time.
149An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute.
150System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.
151The number of specified semaphore events for DosMuxSemWait is not correct.
152DosMuxSemWait did not execute; too many semaphores are already set.
153The DosMuxSemWait list is not correct.
154The volume label you entered exceeds the label character limit of the target file system.
155Cannot create another thread.
156The recipient process has refused the signal.
157The segment is already discarded and cannot be locked.
158The segment is already unlocked.
159The address for the thread ID is not correct.
160The argument string passed to DosExecPgm is not correct.
161The specified path is invalid.
162A signal is already pending.
164No more threads can be created in the system.
167Unable to lock a region of a file.
170The requested resource is in use.
173A lock request was not outstanding for the supplied cancel region.
174The file system does not support atomic changes to the lock type.
180The system detected a segment number that was not correct.
182The operating system cannot run %1.
183Cannot create a file when that file already exists.
186The flag passed is not correct.
187The specified system semaphore name was not found.
188The operating system cannot run %1.
189The operating system cannot run %1.
190The operating system cannot run %1.
191Cannot run %1 in Win32 mode.
192The operating system cannot run %1.
193%1 is not a valid Win32 application.
194The operating system cannot run %1.
195The operating system cannot run %1.
196The operating system cannot run this application program.
197The operating system is not presently configured to run this application.
198The operating system cannot run %1.
199The operating system cannot run this application program.
200The code segment cannot be greater than or equal to 64K.
201The operating system cannot run %1.
202The operating system cannot run %1.
203The system could not find the environment option that was entered.
205No process in the command subtree has a signal handler.
206The filename or extension is too long.
207The ring 2 stack is in use.
208The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
209The signal being posted is not correct.
210The signal handler cannot be set.
212The segment is locked and cannot be reallocated.
214Too many dynamic-link modules are attached to this program or dynamic-link module.
215Cannot nest calls to LoadModule.
216The image file %1 is valid, but is for a machine type other than the current machine.
230The pipe state is invalid.
231All pipe instances are busy.
232The pipe is being closed.
233No process is on the other end of the pipe.
234More data is available.
240The session was canceled.
254The specified extended attribute name was invalid.
255The extended attributes are inconsistent.
258The wait operation timed out.
259No more data is available.
266The copy functions cannot be used.
267The directory name is invalid.
275The extended attributes did not fit in the buffer.
276The extended attribute file on the mounted file system is corrupt.
277The extended attribute table file is full.
278The specified extended attribute handle is invalid.
282The mounted file system does not support extended attributes.
288Attempt to release mutex not owned by caller.
298Too many posts were made to a semaphore.
299Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
300The oplock request is denied.
301An invalid oplock acknowledgment was received by the system.
302The volume is too fragmented to complete this operation.
303The file cannot be opened because it is in the process of being deleted.
317The system cannot find message text for message number 0x%1 in the message file for %2.
487Attempt to access invalid address.
534Arithmetic result exceeded 32 bits.
535There is a process on other end of the pipe.
536Waiting for a process to open the other end of the pipe.
994Access to the extended attribute was denied.
995The I/O operation has been aborted because of either a thread exit or an application request.
996Overlapped I/O event is not in a signaled state.
997Overlapped I/O operation is in progress.
998Invalid access to memory location.
999Error performing inpage operation.
1001Recursion too deep; the stack overflowed.
1002The window cannot act on the sent message.
1003Cannot complete this function.
1004Invalid flags.
1005The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
1006The volume for a file has been externally altered so that the opened file is no longer valid.
1007The requested operation cannot be performed in full-screen mode.
1008An attempt was made to reference a token that does not exist.
1009The configuration registry database is corrupt.
1010The configuration registry key is invalid.
1011The configuration registry key could not be opened.
1012The configuration registry key could not be read.
1013The configuration registry key could not be written.
1014One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.
1015The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system’s memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.
1016An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system’s image of the registry.
1017The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.
1018Illegal operation attempted on a registry key that has been marked for deletion.
1019System could not allocate the required space in a registry log.
1020Cannot create a symbolic link in a registry key that already has subkeys or values.
1021Cannot create a stable subkey under a volatile parent key.
1022A notify change request is being completed and the information is not being returned in the caller’s buffer. The caller now needs to enumerate the files to find the changes.
1051A stop control has been sent to a service that other running services are dependent on.
1052The requested control is not valid for this service.
1053The service did not respond to the start or control request in a timely fashion.
1054A thread could not be created for the service.
1055The service database is locked.
1056An instance of the service is already running.
1057The account name is invalid or does not exist, or the password is invalid for the account name specified.
1058The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
1059Circular service dependency was specified.
1060The specified service does not exist as an installed service.
1061The service cannot accept control messages at this time.
1062The service has not been started.
1063The service process could not connect to the service controller.
1064An exception occurred in the service when handling the control request.
1065The database specified does not exist.
1066The service has returned a service-specific error code.
1067The process terminated unexpectedly.
1068The dependency service or group failed to start.
1069The service did not start due to a logon failure.
1070After starting, the service hung in a start-pending state.
1071The specified service database lock is invalid.
1072The specified service has been marked for deletion.
1073The specified service already exists.
1074The system is currently running with the last-known-good configuration.
1075The dependency service does not exist or has been marked for deletion.
1076The current boot has already been accepted for use as the last-known-good control set.
1077No attempts to start the service have been made since the last boot.
1078The name is already in use as either a service name or a service display name.
1079The account specified for this service is different from the account specified for other services running in the same process.
1080Failure actions can only be set for Win32 services, not for drivers.
1081This service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service’s process terminates unexpectedly.
1082No recovery program has been configured for this service.
1083The executable program that this service is configured to run in does not implement the service.
1084This service cannot be started in Safe Mode.
1100The physical end of the tape has been reached.
1101A tape access reached a filemark.
1102The beginning of the tape or a partition was encountered.
1103A tape access reached the end of a set of files.
1104No more data is on the tape.
1105Tape could not be partitioned.
1106When accessing a new tape of a multivolume partition, the current block size is incorrect.
1107Tape partition information could not be found when loading a tape.
1108Unable to lock the media eject mechanism.
1109Unable to unload the media.
1110The media in the drive may have changed.
1111The I/O bus was reset.
1112No media in drive.
1113No mapping for the Unicode character exists in the target multi-byte code page.
1114A dynamic link library (DLL) initialization routine failed.
1115A system shutdown is in progress.
1116Unable to abort the system shutdown because no shutdown was in progress.
1117The request could not be performed because of an I/O device error.
1118No serial device was successfully initialized. The serial driver will unload.
1119Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.
1120A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
1121A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
1122No ID address mark was found on the floppy disk.
1123Mismatch between the floppy disk sector ID field and the floppy disk controller track address.
1124The floppy disk controller reported an error that is not recognized by the floppy disk driver.
1125The floppy disk controller returned inconsistent results in its registers.
1126While accessing the hard disk, a recalibrate operation failed, even after retries.
1127While accessing the hard disk, a disk operation failed even after retries.
1128While accessing the hard disk, a disk controller reset was needed, but even that failed.
1129Physical end of tape encountered.
1130Not enough server storage is available to process this command.
1131A potential deadlock condition has been detected.
1132The base address or the file offset specified does not have the proper alignment.
1140An attempt to change the system power state was vetoed by another application or driver.
1141The system BIOS failed an attempt to change the system power state.
1142An attempt was made to create more links on a file than the file system supports.
1150The specified program requires a newer version of Windows.
1151The specified program is not a Windows or MS-DOS program.
1152Cannot start more than one instance of the specified program.
1153The specified program was written for an earlier version of Windows.
1154One of the library files needed to run this application is damaged.
1155No application is associated with the specified file for this operation.
1156An error occurred in sending the command to the application.
1157One of the library files needed to run this application cannot be found.
1158The current process has used all of its system allowance of handles for Window Manager objects.
1159The message can be used only with synchronous operations.
1160The indicated source element has no media.
1161The indicated destination element already contains media.
1162The indicated element does not exist.
1163The indicated element is part of a magazine that is not present.
1164The indicated device requires reinitialization due to hardware errors.
1165The device has indicated that cleaning is required before further operations are attempted.
1166The device has indicated that its door is open.
1167The device is not connected.
1168Element not found.
1169There was no match for the specified key in the index.
1170The property set specified does not exist on the object.
1171The point passed to GetMouseMovePointsEx is not in the buffer.
1172The tracking (workstation) service is not running.
1173The Volume ID could not be found.
1175Unable to remove the file to be replaced.
1176Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.
1177Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.
1178The volume change journal is being deleted.
1179The volume change journal is not active.
1180A file was found, but it may not be the correct file.
1181The journal entry has been deleted from the journal.
1200The specified device name is invalid.
1201The device is not currently connected but it is a remembered connection.
1202The local device name has a remembered connection to another network resource.
1203No network provider accepted the given network path.
1204The specified network provider name is invalid.
1205Unable to open the network connection profile.
1206The network connection profile is corrupted.
1207Cannot enumerate a noncontainer.
1208An extended error has occurred.
1209The format of the specified group name is invalid.
1210The format of the specified computer name is invalid.
1211The format of the specified event name is invalid.
1212The format of the specified domain name is invalid.
1213The format of the specified service name is invalid.
1214The format of the specified network name is invalid.
1215The format of the specified share name is invalid.
1216The format of the specified password is invalid.
1217The format of the specified message name is invalid.
1218The format of the specified message destination is invalid.
1219Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
1220An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.
1221The workgroup or domain name is already in use by another computer on the network.
1222The network is not present or not started.
1223The operation was canceled by the user.
1224The requested operation cannot be performed on a file with a user-mapped section open.
1225The remote system refused the network connection.
1226The network connection was gracefully closed.
1227The network transport endpoint already has an address associated with it.
1228An address has not yet been associated with the network endpoint.
1229An operation was attempted on a nonexistent network connection.
1230An invalid operation was attempted on an active network connection.
1231The network location cannot be reached. For information about network troubleshooting, see Windows Help.
1232The network location cannot be reached. For information about network troubleshooting, see Windows Help.
1233The network location cannot be reached. For information about network troubleshooting, see Windows Help.
1234No service is operating at the destination network endpoint on the remote system.
1235The request was aborted.
1236The network connection was aborted by the local system.
1237The operation could not be completed. A retry should be performed.
1238A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.
1239Attempting to log in during an unauthorized time of day for this account.
1240The account is not authorized to log in from this station.
1241The network address could not be used for the operation requested.
1242The service is already registered.
1243The specified service does not exist.
1244The operation being requested was not performed because the user has not been authenticated.
1245The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.
1246Continue with work in progress.
1247An attempt was made to perform an initialization operation when initialization has already been completed.
1248No more local devices.
1249The specified site does not exist.
1250A domain controller with the specified name already exists.
1251This operation is supported only when you are connected to the server.
1252The group policy framework should call the extension even if there are no changes.
1253The specified user does not have a valid profile.
1254This operation is not supported on a Microsoft Small Business Server.
1255The server machine is shutting down.
1256The remote system is not available. For information about network troubleshooting, see Windows Help.
1257The security identifier provided is not from an account domain.
1258The security identifier provided does not have a domain component.
1259AppHelp dialog canceled thus preventing the application from starting.
1260Windows cannot open this program because it has been prevented by a software restriction policy. For more information, open Event Viewer or contact your system administrator.
1261A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific.
1262The share is currently offline or does not exist.
1263The kerberos protocol encountered an error while validating the KDC certificate during smartcard logon.
1264The kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.
1265The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.
1266The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log.
1267An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator.
1268The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator.
1269The smartcard certificate used for authentication was not trusted. Please contact your system administrator.
1270The smartcard certificate used for authentication has expired. Please contact your system administrator.
1271The machine is locked and cannot be shut down without the force option.
1273An application-defined callback gave invalid data when called.
1274The group policy framework should call the extension in the synchronous foreground policy refresh.
1275This driver has been blocked from loading.
1276A dynamic link library (DLL) referenced a module that was neither a DLL nor the process’s executable image.
1300Not all privileges referenced are assigned to the caller.
1301Some mapping between account names and security IDs was not done.
1302No system quota limits are specifically set for this account.
1303No encryption key is available. A well-known encryption key was returned.
1304The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.
1305The revision level is unknown.
1306Indicates two revision levels are incompatible.
1307This security ID may not be assigned as the owner of this object.
1308This security ID may not be assigned as the primary group of an object.
1309An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
1310The group may not be disabled.
1311There are currently no logon servers available to service the logon request.
1312A specified logon session does not exist. It may already have been terminated.
1313A specified privilege does not exist.
1314A required privilege is not held by the client.
1315The name provided is not a properly formed account name.
1316The specified user already exists.
1317The specified user does not exist.
1318The specified group already exists.
1319The specified group does not exist.
1320Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.
1321The specified user account is not a member of the specified group account.
1322The last remaining administration account cannot be disabled or deleted.
1323Unable to update the password. The value provided as the current password is incorrect.
1324Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.
1325Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirement of the domain.
1326Logon failure: unknown user name or bad password.
1327Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced.
1328Logon failure: account logon time restriction violation.
1329Logon failure: user not allowed to log on to this computer.
1330Logon failure: the specified account password has expired.
1331Logon failure: account currently disabled.
1332No mapping between account names and security IDs was done.
1333Too many local user identifiers (LUIDs) were requested at one time.
1334No more local user identifiers (LUIDs) are available.
1335The subauthority part of a security ID is invalid for this particular use.
1336The access control list (ACL) structure is invalid.
1337The security ID structure is invalid.
1338The security descriptor structure is invalid.
1340The inherited access control list (ACL) or access control entry (ACE) could not be built.
1341The server is currently disabled.
1342The server is currently enabled.
1343The value provided was an invalid value for an identifier authority.
1344No more memory is available for security information updates.
1345The specified attributes are invalid, or incompatible with the attributes for the group as a whole.
1346Either a required impersonation level was not provided, or the provided impersonation level is invalid.
1347Cannot open an anonymous level security token.
1348The validation information class requested was invalid.
1349The type of the token is inappropriate for its attempted use.
1350Unable to perform a security operation on an object that has no associated security.
1351Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
1352The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.
1353The domain was in the wrong state to perform the security operation.
1354This operation is only allowed for the Primary Domain Controller of the domain.
1355The specified domain either does not exist or could not be contacted.
1356The specified domain already exists.
1357An attempt was made to exceed the limit on the number of domains per server.
1358Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.
1359An internal error occurred.
1360Generic access types were contained in an access mask which should already be mapped to nongeneric types.
1361A security descriptor is not in the right format (absolute or self-relative).
1362The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.
1363Cannot start a new logon session with an ID that is already in use.
1364A specified authentication package is unknown.
1365The logon session is not in a state that is consistent with the requested operation.
1366The logon session ID is already in use.
1367A logon request contained an invalid logon type value.
1368Unable to impersonate using a named pipe until data has been read from that pipe.
1369The transaction state of a registry subtree is incompatible with the requested operation.
1370An internal security database corruption has been encountered.
1371Cannot perform this operation on built-in accounts.
1372Cannot perform this operation on this built-in special group.
1373Cannot perform this operation on this built-in special user.
1374The user cannot be removed from a group because the group is currently the user’s primary group.
1375The token is already in use as a primary token.
1376The specified local group does not exist.
1377The specified account name is not a member of the local group.
1378The specified account name is already a member of the local group.
1379The specified local group already exists.
1380Logon failure: the user has not been granted the requested logon type at this computer.
1381The maximum number of secrets that may be stored in a single system has been exceeded.
1382The length of a secret exceeds the maximum length allowed.
1383The local security authority database contains an internal inconsistency.
1384During a logon attempt, the user’s security context accumulated too many security IDs.
1385Logon failure: the user has not been granted the requested logon type at this computer.
1386A cross-encrypted password is necessary to change a user password.
1387A new member could not be added to or removed from the local group because the member does not exist.
1388A new member could not be added to a local group because the member has the wrong account type.
1389Too many security IDs have been specified.
1390A cross-encrypted password is necessary to change this user password.
1391Indicates an ACL contains no inheritable components.
1392The file or directory is corrupted and unreadable.
1393The disk structure is corrupted and unreadable.
1394There is no user session key for the specified logon session.
1395The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.
1396Logon Failure: The target account name is incorrect.
1397Mutual Authentication failed. The server’s password is out of date at the domain controller.
1398There is a time and/or date difference between the client and server.
1399This operation cannot be performed on the current domain.
1400Invalid window handle.
1401Invalid menu handle.
1402Invalid cursor handle.
1403Invalid accelerator table handle.
1404Invalid hook handle.
1405Invalid handle to a multiple-window position structure.
1406Cannot create a top-level child window.
1407Cannot find window class.
1408Invalid window; it belongs to other thread.
1409Hot key is already registered.
1410Class already exists.
1411Class does not exist.
1412Class still has open windows.
1413Invalid index.
1414Invalid icon handle.
1415Using private DIALOG window words.
1416The list box identifier was not found.
1417No wildcards were found.
1418Thread does not have a clipboard open.
1419Hot key is not registered.
1420The window is not a valid dialog window.
1421Control ID not found.
1422Invalid message for a combo box because it does not have an edit control.
1423The window is not a combo box.
1424Height must be less than 256.
1425Invalid device context (DC) handle.
1426Invalid hook procedure type.
1427Invalid hook procedure.
1428Cannot set nonlocal hook without a module handle.
1429This hook procedure can only be set globally.
1430The journal hook procedure is already installed.
1431The hook procedure is not installed.
1432Invalid message for single-selection list box.
1433LB_SETCOUNT sent to non-lazy list box.
1434This list box does not support tab stops.
1435Cannot destroy object created by another thread.
1436Child windows cannot have menus.
1437The window does not have a system menu.
1438Invalid message box style.
1439Invalid system-wide (SPI_*) parameter.
1440Screen already locked.
1441All handles to windows in a multiple-window position structure must have the same parent.
1442The window is not a child window.
1443Invalid GW_* command.
1444Invalid thread identifier.
1445Cannot process a message from a window that is not a multiple document interface (MDI) window.
1446Popup menu already active.
1447The window does not have scroll bars.
1448Scroll bar range cannot be greater than MAXLONG.
1449Cannot show or remove the window in the way specified.
1450Insufficient system resources exist to complete the requested service.
1451Insufficient system resources exist to complete the requested service.
1452Insufficient system resources exist to complete the requested service.
1453Insufficient quota to complete the requested service.
1454Insufficient quota to complete the requested service.
1455The paging file is too small for this operation to complete.
1456A menu item was not found.
1457Invalid keyboard layout handle.
1458Hook type not allowed.
1459This operation requires an interactive window station.
1460This operation returned because the timeout period expired.
1461Invalid monitor handle.
1500The event log file is corrupted.
1501No event log file could be opened, so the event logging service did not start.
1502The event log file is full.
1503The event log file has changed between read operations.
1601The Windows Installer service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
1602User cancelled installation.
1603Fatal error during installation.
1604Installation suspended, incomplete.
1605This action is only valid for products that are currently installed.
1606Feature ID not registered.
1607Component ID not registered.
1608Unknown property.
1609Handle is in an invalid state.
1610The configuration data for this product is corrupt. Contact your support personnel.
1611Component qualifier not present.
1612The installation source for this product is not available. Verify that the source exists and that you can access it.
1613This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
1614Product is uninstalled.
1615SQL query syntax invalid or unsupported.
1616Record field does not exist.
1617The device has been removed.
1618Another installation is already in progress. Complete that installation before proceeding with this install.
1619This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.
1620This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
1621There was an error starting the Windows Installer service user interface. Contact your support personnel.
1622Error opening installation log file. Verify that the specified log file location exists and that you can write to it.
1623The language of this installation package is not supported by your system.
1624Error applying transforms. Verify that the specified transform paths are valid.
1625This installation is forbidden by system policy. Contact your system administrator.
1626Function could not be executed.
1627Function failed during execution.
1628Invalid or unknown table specified.
1629Data supplied is of wrong type.
1630Data of this type is not supported.
1631The Windows Installer service failed to start. Contact your support personnel.
1632The Temp folder is on a drive that is full or inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder.
1633This installation package is not supported by this processor type. Contact your product vendor.
1634Component not used on this computer.
1635This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
1636This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package.
1637This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
1638Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
1639Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
1640Only administrators have permission to add, remove, or configure server software during a Terminal Services remote session. If you want to install or configure software on the server, contact your network administrator.
1641The requested operation completed successfully. The system will be restarted so the changes can take effect.
1642The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
1643The patch package is not permitted by software restriction policy.
1644One or more customizations are not permitted by software restriction policy.
1700The string binding is invalid.
1701The binding handle is not the correct type.
1702The binding handle is invalid.
1703The RPC protocol sequence is not supported.
1704The RPC protocol sequence is invalid.
1705The string universal unique identifier (UUID) is invalid.
1706The endpoint format is invalid.
1707The network address is invalid.
1708No endpoint was found.
1709The timeout value is invalid.
1710The object universal unique identifier (UUID) was not found.
1711The object universal unique identifier (UUID) has already been registered.
1712The type universal unique identifier (UUID) has already been registered.
1713The RPC server is already listening.
1714No protocol sequences have been registered.
1715The RPC server is not listening.
1716The manager type is unknown.
1717The interface is unknown.
1718There are no bindings.
1719There are no protocol sequences.
1720The endpoint cannot be created.
1721Not enough resources are available to complete this operation.
1722The RPC server is unavailable.
1723The RPC server is too busy to complete this operation.
1724The network options are invalid.
1725There are no remote procedure calls active on this thread.
1726The remote procedure call failed.
1727The remote procedure call failed and did not execute.
1728A remote procedure call (RPC) protocol error occurred.
1730The transfer syntax is not supported by the RPC server.
1732The universal unique identifier (UUID) type is not supported.
1733The tag is invalid.
1734The array bounds are invalid.
1735The binding does not contain an entry name.
1736The name syntax is invalid.
1737The name syntax is not supported.
1739No network address is available to use to construct a universal unique identifier (UUID).
1740The endpoint is a duplicate.
1741The authentication type is unknown.
1742The maximum number of calls is too small.
1743The string is too long.
1744The RPC protocol sequence was not found.
1745The procedure number is out of range.
1746The binding does not contain any authentication information.
1747The authentication service is unknown.
1748The authentication level is unknown.
1749The security context is invalid.
1750The authorization service is unknown.
1751The entry is invalid.
1752The server endpoint cannot perform the operation.
1753There are no more endpoints available from the endpoint mapper.
1754No interfaces have been exported.
1755The entry name is incomplete.
1756The version option is invalid.
1757There are no more members.
1758There is nothing to unexport.
1759The interface was not found.
1760The entry already exists.
1761The entry is not found.
1762The name service is unavailable.
1763The network address family is invalid.
1764The requested operation is not supported.
1765No security context is available to allow impersonation.
1766An internal error occurred in a remote procedure call (RPC).
1767The RPC server attempted an integer division by zero.
1768An addressing error occurred in the RPC server.
1769A floating-point operation at the RPC server caused a division by zero.
1770A floating-point underflow occurred at the RPC server.
1771A floating-point overflow occurred at the RPC server.
1772The list of RPC servers available for the binding of auto handles has been exhausted.
1773Unable to open the character translation table file.
1774The file containing the character translation table has fewer than 512 bytes.
1775A null context handle was passed from the client to the host during a remote procedure call.
1777The context handle changed during a remote procedure call.
1778The binding handles passed to a remote procedure call do not match.
1779The stub is unable to get the remote procedure call handle.
1780A null reference pointer was passed to the stub.
1781The enumeration value is out of range.
1782The byte count is too small.
1783The stub received bad data.
1784The supplied user buffer is not valid for the requested operation.
1785The disk media is not recognized. It may not be formatted.
1786The workstation does not have a trust secret.
1787The security database on the server does not have a computer account for this workstation trust relationship.
1788The trust relationship between the primary domain and the trusted domain failed.
1789The trust relationship between this workstation and the primary domain failed.
1790The network logon failed.
1791A remote procedure call is already in progress for this thread.
1792An attempt was made to logon, but the network logon service was not started.
1793The user’s account has expired.
1794The redirector is in use and cannot be unloaded.
1795The specified printer driver is already installed.
1796The specified port is unknown.
1797The printer driver is unknown.
1798The print processor is unknown.
1799The specified separator file is invalid.
1800The specified priority is invalid.
1801The printer name is invalid.
1802The printer already exists.
1803The printer command is invalid.
1804The specified datatype is invalid.
1805The environment specified is invalid.
1806There are no more bindings.
1807The account used is an interdomain trust account. Use your global user account or local user account to access this server.
1808The account used is a computer account. Use your global user account or local user account to access this server.
1809The account used is a server trust account. Use your global user account or local user account to access this server.
1810The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
1811The server is in use and cannot be unloaded.
1812The specified image file did not contain a resource section.
1813The specified resource type cannot be found in the image file.
1814The specified resource name cannot be found in the image file.
1815The specified resource language ID cannot be found in the image file.
1816Not enough quota is available to process this command.
1817No interfaces have been registered.
1818The remote procedure call was cancelled.
1819The binding handle does not contain all required information.
1820A communications failure occurred during a remote procedure call.
1821The requested authentication level is not supported.
1822No principal name registered.
1823The error specified is not a valid Windows RPC error code.
1824A UUID that is valid only on this computer has been allocated.
1825A security package specific error occurred.
1826Thread is not canceled.
1827Invalid operation on the encoding/decoding handle.
1828Incompatible version of the serializing package.
1829Incompatible version of the RPC stub.
1830The RPC pipe object is invalid or corrupted.
1831An invalid operation was attempted on an RPC pipe object.
1832Unsupported RPC pipe version.
1898The group member was not found.
1899The endpoint mapper database entry could not be created.
1900The object universal unique identifier (UUID) is the nil UUID.
1901The specified time is invalid.
1902The specified form name is invalid.
1903The specified form size is invalid.
1904The specified printer handle is already being waited on
1905The specified printer has been deleted.
1906The state of the printer is invalid.
1907The user’s password must be changed before logging on the first time.
1908Could not find the domain controller for this domain.
1909The referenced account is currently locked out and may not be logged on to.
1910The object exporter specified was not found.
1911The object specified was not found.
1912The object resolver set specified was not found.
1913Some data remains to be sent in the request buffer.
1914Invalid asynchronous remote procedure call handle.
1915Invalid asynchronous RPC call handle for this operation.
1916The RPC pipe object has already been closed.
1917The RPC call completed before all pipes were processed.
1918No more data is available from the RPC pipe.
1919No site name is available for this machine.
1920The file cannot be accessed by the system.
1921The name of the file cannot be resolved by the system.
1922The entry is not of the expected type.
1923Not all object UUIDs could be exported to the specified entry.
1924Interface could not be exported to the specified entry.
1925The specified profile entry could not be added.
1926The specified profile element could not be added.
1927The specified profile element could not be removed.
1928The group element could not be added.
1929The group element could not be removed.
1930The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.
1931The context has expired and can no longer be used.
2000The pixel format is invalid.
2001The specified driver is invalid.
2002The window style or class attribute is invalid for this operation.
2003The requested metafile operation is not supported.
2004The requested transformation operation is not supported.
2005The requested clipping operation is not supported.
2010The specified color management module is invalid.
2011The specified color profile is invalid.
2012The specified tag was not found.
2013A required tag is not present.
2014The specified tag is already present.
2015The specified color profile is not associated with any device.
2016The specified color profile was not found.
2017The specified color space is invalid.
2018Image Color Management is not enabled.
2019There was an error while deleting the color transform.
2020The specified color transform is invalid.
2021The specified transform does not match the bitmap’s color space.
2022The specified named color index is not present in the profile.
2108The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified.
2109The network connection was made successfully using default credentials.
2202The specified username is invalid.
2250This network connection does not exist.
2401This network connection has files open or requests pending.
2402Active connections still exist.
2404The device is in use by an active process and cannot be disconnected.
3000The specified print monitor is unknown.
3001The specified printer driver is currently in use.
3002The spool file was not found.
3003A StartDocPrinter call was not issued.
3004An AddJob call was not issued.
3005The specified print processor has already been installed.
3006The specified print monitor has already been installed.
3007The specified print monitor does not have the required functions.
3008The specified print monitor is currently in use.
3009The requested operation is not allowed when there are jobs queued to the printer.
3010The requested operation is successful. Changes will not be effective until the system is rebooted.
3011The requested operation is successful. Changes will not be effective until the service is restarted.
3012No printers were found.
3013The printer driver is known to be unreliable.
3014The printer driver is known to harm the system.
4000WINS encountered an error while processing the command.
4001The local WINS cannot be deleted.
4002The importation from the file failed.
4003The backup failed. Was a full backup done before?
4004The backup failed. Check the directory to which you are backing the database.
4005The name does not exist in the WINS database.
4006Replication with a nonconfigured partner is not allowed.
4100The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
4200The GUID passed was not recognized as valid by a WMI data provider.
4201The instance name passed was not recognized as valid by a WMI data provider.
4202The data item ID passed was not recognized as valid by a WMI data provider.
4203The WMI request could not be completed and should be retried.
4204The WMI data provider could not be located.
4205The WMI data provider references an instance set that has not been registered.
4206The WMI data block or event notification has already been enabled.
4207The WMI data block is no longer available.
4208The WMI data service is not available.
4209The WMI data provider failed to carry out the request.
4210The WMI MOF information is not valid.
4211The WMI registration information is not valid.
4212The WMI data block or event notification has already been disabled.
4213The WMI data item or data block is read only.
4214The WMI data item or data block could not be changed.
4300The media identifier does not represent a valid medium.
4301The library identifier does not represent a valid library.
4302The media pool identifier does not represent a valid media pool.
4303The drive and medium are not compatible or exist in different libraries.
4304The medium currently exists in an offline library and must be online to perform this operation.
4305The operation cannot be performed on an offline library.
4306The library, drive, or media pool is empty.
4307The library, drive, or media pool must be empty to perform this operation.
4308No media is currently available in this media pool or library.
4309A resource required for this operation is disabled.
4310The media identifier does not represent a valid cleaner.
4311The drive cannot be cleaned or does not support cleaning.
4312The object identifier does not represent a valid object.
4313Unable to read from or write to the database.
4314The database is full.
4315The medium is not compatible with the device or media pool.
4316The resource required for this operation does not exist.
4317The operation identifier is not valid.
4318The media is not mounted or ready for use.
4319The device is not ready for use.
4320The operator or administrator has refused the request.
4321The drive identifier does not represent a valid drive.
4322Library is full. No slot is available for use.
4323The transport cannot access the medium.
4324Unable to load the medium into the drive.
4325Unable to retrieve status about the drive.
4326Unable to retrieve status about the slot.
4327Unable to retrieve status about the transport.
4328Cannot use the transport because it is already in use.
4329Unable to open or close the inject/eject port.
4330Unable to eject the media because it is in a drive.
4331A cleaner slot is already reserved.
4332A cleaner slot is not reserved.
4333The cleaner cartridge has performed the maximum number of drive cleanings.
4334Unexpected on-medium identifier.
4335The last remaining item in this group or resource cannot be deleted.
4336The message provided exceeds the maximum size allowed for this parameter.
4337The volume contains system or paging files.
4338The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.
4339This offline media cannot be mounted on this system since no enabled drives are present which can be used.
4340A cleaner cartridge is present in the tape library.
4350The remote storage service was not able to recall the file.
4351The remote storage service is not operational at this time.
4352The remote storage service encountered a media error.
4390The file or directory is not a reparse point.
4391The reparse point attribute cannot be set because it conflicts with an existing attribute.
4392The data present in the reparse point buffer is invalid.
4393The tag present in the reparse point buffer is invalid.
4394There is a mismatch between the tag specified in the request and the tag present in the reparse point.
4500Single Instance Storage is not available on this volume.
5001The cluster resource cannot be moved to another group because other resources are dependent on it.
5002The cluster resource dependency cannot be found.
5003The cluster resource cannot be made dependent on the specified resource because it is already dependent.
5004The cluster resource is not online.
5005A cluster node is not available for this operation.
5006The cluster resource is not available.
5007The cluster resource could not be found.
5008The cluster is being shut down.
5009A cluster node cannot be evicted from the cluster unless the node is down.
5010The object already exists.
5011The object is already in the list.
5012The cluster group is not available for any new requests.
5013The cluster group could not be found.
5014The operation could not be completed because the cluster group is not online.
5015The cluster node is not the owner of the resource.
5016The cluster node is not the owner of the group.
5017The cluster resource could not be created in the specified resource monitor.
5018The cluster resource could not be brought online by the resource monitor.
5019The operation could not be completed because the cluster resource is online.
5020The cluster resource could not be deleted or brought offline because it is the quorum resource.
5021The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
5022The cluster software is shutting down.
5023The group or resource is not in the correct state to perform the requested operation.
5024The properties were stored but not all changes will take effect until the next time the resource is brought online.
5025The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
5026The cluster resource could not be deleted since it is a core resource.
5027The quorum resource failed to come online.
5028The quorum log could not be created or mounted successfully.
5029The cluster log is corrupt.
5030The record could not be written to the cluster log since it exceeds the maximum size.
5031The cluster log exceeds its maximum size.
5032No checkpoint record was found in the cluster log.
5033The minimum required disk space needed for logging is not available.
5034The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
5035A cluster network is not available for this operation.
5036A cluster node is not available for this operation.
5037All cluster nodes must be running to perform this operation.
5038A cluster resource failed.
5039The cluster node is not valid.
5040The cluster node already exists.
5041A node is in the process of joining the cluster.
5042The cluster node was not found.
5043The cluster local node information was not found.
5044The cluster network already exists.
5045The cluster network was not found.
5046The cluster network interface already exists.
5047The cluster network interface was not found.
5048The cluster request is not valid for this object.
5049The cluster network provider is not valid.
5050The cluster node is down.
5051The cluster node is not reachable.
5052The cluster node is not a member of the cluster.
5053A cluster join operation is not in progress.
5054The cluster network is not valid.
5056The cluster node is up.
5057The cluster IP address is already in use.
5058The cluster node is not paused.
5059No cluster security context is available.
5060The cluster network is not configured for internal cluster communication.
5061The cluster node is already up.
5062The cluster node is already down.
5063The cluster network is already online.
5064The cluster network is already offline.
5065The cluster node is already a member of the cluster.
5066The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.
5067One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
5068This operation cannot be performed on the cluster resource as it the quorum resource. You may not bring the quorum resource offline or modify its possible owners list.
5069The cluster quorum resource is not allowed to have any dependencies.
5070The cluster node is paused.
5071The cluster resource cannot be brought online. The owner node cannot run this resource.
5072The cluster node is not ready to perform the requested operation.
5073The cluster node is shutting down.
5074The cluster join operation was aborted.
5075The cluster join operation failed due to incompatible software versions between the joining node and its sponsor.
5076This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
5077The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
5078The specified resource type was not found.
5079The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
5080The specified resource name is supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.
5081No authentication package could be registered with the RPC server.
5082You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.
5083The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.
5084The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.
5085A non locker code got a request to reserve the lock for making global updates.
5086The quorum disk could not be located by the cluster service.
5087The backup up cluster database is possibly corrupt.
5088A DFS root already exists in this cluster node.
5089An attempt to modify a resource property failed because it conflicts with another existing property.
5890An operation was attempted that is incompatible with the current membership state of the node.
5891The quorum resource does not contain the quorum log.
5892The membership engine requested shutdown of the cluster service on this node.
5893The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
5894A matching network for the specified IP address could not be found. Please also specify a subnet mask and a cluster network.
5895The actual data type of the property did not match the expected data type of the property.
5896The cluster node was evicted from the cluster successfully, but the node was not cleaned up. Extended status information explaining why the node was not cleaned up is available.
5897Two or more parameter values specified for a resource’s properties are in conflict.
5898This computer cannot be made a member of a cluster.
5899This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
5900A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.
6000The specified file could not be encrypted.
6001The specified file could not be decrypted.
6002The specified file is encrypted and the user does not have the ability to decrypt it.
6003There is no valid encryption recovery policy configured for this system.
6004The required encryption driver is not loaded for this system.
6005The file was encrypted with a different encryption driver than is currently loaded.
6006There are no EFS keys defined for the user.
6007The specified file is not encrypted.
6008The specified file is not in the defined EFS export format.
6009The specified file is read only.
6010The directory has been disabled for encryption.
6011The server is not trusted for remote encryption operation.
6012Recovery policy configured for this system contains invalid recovery certificate.
6013The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.
6014The disk partition does not support file encryption.
6015This machine is disabled for file encryption.
6016A newer system is required to decrypt this encrypted file.
6118The list of servers for this workgroup is not currently available.
6200The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.
7001The specified session name is invalid.
7002The specified protocol driver is invalid.
7003The specified protocol driver was not found in the system path.
7004The specified terminal connection driver was not found in the system path.
7005A registry key for event logging could not be created for this session.
7006A service with the same name already exists on the system.
7007A close operation is pending on the session.
7008There are no free output buffers available.
7009The MODEM.INF file was not found.
7010The modem name was not found in MODEM.INF.
7011The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
7012The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
7013Carrier detect has failed or carrier has been dropped due to disconnect.
7014Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.
7015Busy signal detected at remote site on callback.
7016Voice detected at remote site on callback.
7017Transport driver error
7022The specified session cannot be found.
7023The specified session name is already in use.
7024The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation.
7025An attempt has been made to connect to a session whose video mode is not supported by the current client.
7035The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
7037Your interactive logon privilege has been disabled. Please contact your administrator.
7038The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access.
7040The client failed to respond to the server connect message.
7041Disconnecting the console session is not supported.
7042Reconnecting a disconnected session to the console is not supported.
7044The request to control another session remotely was denied.
7045The requested session access is denied.
7049The specified terminal connection driver is invalid.
7050The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on.
7051The requested session is not configured to allow remote control.
7052Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.
7053Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator.
7054The system has reached its licensed logon limit. Please try again later.
7055The client you are using is not licensed to use this system. Your logon request is denied.
7056The system license has expired. Your logon request is denied.
7057Remote control could not be terminated because the specified session is not currently being remotely controlled.
7058The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported.
8001The file replication service API was called incorrectly.
8002The file replication service cannot be started.
8003The file replication service cannot be stopped.
8004The file replication service API terminated the request. The event log may have more information.
8005The file replication service terminated the request. The event log may have more information.
8006The file replication service cannot be contacted. The event log may have more information.
8007The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
8008The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
8009The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information.
8010The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information.
8011The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
8012The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information.
8013The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
8014The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
8015The file replication service cannot process the request. The system volume is busy with a previous request.
8016The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
8017The file replication service detected an invalid parameter.
8200An error occurred while installing the directory service. For more information, see the event log.
8201The directory service evaluated group memberships locally.
8202The specified directory service attribute or value does not exist.
8203The attribute syntax specified to the directory service is invalid.
8204The attribute type specified to the directory service is not defined.
8205The specified directory service attribute or value already exists.
8206The directory service is busy.
8207The directory service is unavailable.
8208The directory service was unable to allocate a relative identifier.
8209The directory service has exhausted the pool of relative identifiers.
8210The requested operation could not be performed because the directory service is not the master for that type of operation.
8211The directory service was unable to initialize the subsystem that allocates relative identifiers.
8212The requested operation did not satisfy one or more constraints associated with the class of the object.
8213The directory service can perform the requested operation only on a leaf object.
8214The directory service cannot perform the requested operation on the RDN attribute of an object.
8215The directory service detected an attempt to modify the object class of an object.
8216The requested cross-domain move operation could not be performed.
8217Unable to contact the global catalog server.
8218The policy object is shared and can only be modified at the root.
8219The policy object does not exist.
8220The requested policy information is only in the directory service.
8221A domain controller promotion is currently active.
8222A domain controller promotion is not currently active
8224An operations error occurred.
8225A protocol error occurred.
8226The time limit for this request was exceeded.
8227The size limit for this request was exceeded.
8228The administrative limit for this request was exceeded.
8229The compare response was false.
8230The compare response was true.
8231The requested authentication method is not supported by the server.
8232A more secure authentication method is required for this server.
8233Inappropriate authentication.
8234The authentication mechanism is unknown.
8235A referral was returned from the server.
8236The server does not support the requested critical extension.
8237This request requires a secure connection.
8238Inappropriate matching.
8239A constraint violation occurred.
8240There is no such object on the server.
8241There is an alias problem.
8242An invalid dn syntax has been specified.
8243The object is a leaf object.
8244There is an alias dereferencing problem.
8245The server is unwilling to process the request.
8246A loop has been detected.
8247There is a naming violation.
8248The result set is too large.
8249The operation affects multiple DSAs
8250The server is not operational.
8251A local error has occurred.
8252An encoding error has occurred.
8253A decoding error has occurred.
8254The search filter cannot be recognized.
8255One or more parameters are illegal.
8256The specified method is not supported.
8257No results were returned.
8258The specified control is not supported by the server.
8259A referral loop was detected by the client.
8260The preset referral limit was exceeded.
8261The search requires a SORT control.
8262The search results exceed the offset range specified.
8301The root object must be the head of a naming context. The root object cannot have an instantiated parent.
8302The add replica operation cannot be performed. The naming context must be writable in order to create the replica.
8303A reference to an attribute that is not defined in the schema occurred.
8304The maximum size of an object has been exceeded.
8305An attempt was made to add an object to the directory with a name that is already in use.
8306An attempt was made to add an object of a class that does not have an RDN defined in the schema.
8307An attempt was made to add an object using an RDN that is not the RDN defined in the schema.
8308None of the requested attributes were found on the objects.
8309The user buffer is too small.
8310The attribute specified in the operation is not present on the object.
8311Illegal modify operation. Some aspect of the modification is not permitted.
8312The specified object is too large.
8313The specified instance type is not valid.
8314The operation must be performed at a master DSA.
8315The object class attribute must be specified.
8316A required attribute is missing.
8317An attempt was made to modify an object to include an attribute that is not legal for its class
8318The specified attribute is already present on the object.
8320The specified attribute is not present, or has no values.
8321Multiple values were specified for an attribute that can have only one value.
8322A value for the attribute was not in the acceptable range of values.
8323The specified value already exists.
8324The attribute cannot be removed because it is not present on the object.
8325The attribute value cannot be removed because it is not present on the object.
8326The specified root object cannot be a subref.
8327Chaining is not permitted.
8328Chained evaluation is not permitted.
8329The operation could not be performed because the object’s parent is either uninstantiated or deleted.
8330Having a parent that is an alias is not permitted. Aliases are leaf objects.
8331The object and parent must be of the same type, either both masters or both replicas.
8332The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.
8333Directory object not found.
8334The aliased object is missing.
8335The object name has bad syntax.
8336It is not permitted for an alias to refer to another alias.
8337The alias cannot be dereferenced.
8338The operation is out of scope.
8339The operation cannot continue because the object is in the process of being removed.
8340The DSA object cannot be deleted.
8341A directory service error has occurred.
8342The operation can only be performed on an internal master DSA object.
8343The object must be of class DSA.
8344Insufficient access rights to perform the operation.
8345The object cannot be added because the parent is not on the list of possible superiors.
8346Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).
8347The name has too many parts.
8348The name is too long.
8349The name value is too long.
8350The directory service encountered an error parsing a name.
8351The directory service cannot get the attribute type for a name.
8352The name does not identify an object; the name identifies a phantom.
8353The security descriptor is too short.
8354The security descriptor is invalid.
8355Failed to create name for deleted object.
8356The parent of a new subref must exist.
8357The object must be a naming context.
8358It is not permitted to add an attribute which is owned by the system.
8359The class of the object must be structural; you cannot instantiate an abstract class.
8360The schema object could not be found.
8361A local object with this GUID (dead or alive) already exists.
8362The operation cannot be performed on a back link.
8363The cross reference for the specified naming context could not be found.
8364The operation could not be performed because the directory service is shutting down.
8365The directory service request is invalid.
8366The role owner attribute could not be read.
8367The requested FSMO operation failed. The current FSMO holder could not be reached.
8368Modification of a DN across a naming context is not permitted.
8369The attribute cannot be modified because it is owned by the system.
8370Only the replicator can perform this function.
8371The specified class is not defined.
8372The specified class is not a subclass.
8373The name reference is invalid.
8374A cross reference already exists.
8375It is not permitted to delete a master cross reference.
8376Subtree notifications are only supported on NC heads.
8377Notification filter is too complex.
8378Schema update failed: duplicate RDN.
8379Schema update failed: duplicate OID
8380Schema update failed: duplicate MAPI identifier.
8381Schema update failed: duplicate schema-id GUID.
8382Schema update failed: duplicate LDAP display name.
8383Schema update failed: range-lower less than range upper
8384Schema update failed: syntax mismatch
8385Schema deletion failed: attribute is used in must-contain
8386Schema deletion failed: attribute is used in may-contain
8387Schema update failed: attribute in may-contain does not exist
8388Schema update failed: attribute in must-contain does not exist
8389Schema update failed: class in aux-class list does not exist or is not an auxiliary class
8390Schema update failed: class in poss-superiors does not exist
8391Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules
8392Schema update failed: Rdn-Att-Id has wrong syntax
8393Schema deletion failed: class is used as auxiliary class
8394Schema deletion failed: class is used as sub class
8395Schema deletion failed: class is used as poss superior
8396Schema update failed in recalculating validation cache.
8397The tree deletion is not finished.
8398The requested delete operation could not be performed.
8399Cannot read the governs class identifier for the schema record.
8400The attribute schema has bad syntax.
8401The attribute could not be cached.
8402The class could not be cached.
8403The attribute could not be removed from the cache.
8404The class could not be removed from the cache.
8405The distinguished name attribute could not be read.
8406A required subref is missing.
8407The instance type attribute could not be retrieved.
8408An internal error has occurred.
8409A database error has occurred.
8410The attribute GOVERNSID is missing.
8411An expected attribute is missing.
8412The specified naming context is missing a cross reference.
8413A security checking error has occurred.
8414The schema is not loaded.
8415Schema allocation failed. Please check if the machine is running low on memory.
8416Failed to obtain the required syntax for the attribute schema.
8417The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.
8418The replication operation failed because of a schema mismatch between the servers involved.
8419The DSA object could not be found.
8420The naming context could not be found.
8421The naming context could not be found in the cache.
8422The child object could not be retrieved.
8423The modification was not permitted for security reasons.
8424The operation cannot replace the hidden record.
8425The hierarchy file is invalid.
8426The attempt to build the hierarchy table failed.
8427The directory configuration parameter is missing from the registry.
8428The attempt to count the address book indices failed.
8429The allocation of the hierarchy table failed.
8430The directory service encountered an internal failure.
8431The directory service encountered an unknown failure.
8432A root object requires a class of ‘top’.
8433This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.
8434The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.
8435The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.
8436The replication operation failed.
8437An invalid parameter was specified for this replication operation.
8438The directory service is too busy to complete the replication operation at this time.
8439The distinguished name specified for this replication operation is invalid.
8440The naming context specified for this replication operation is invalid.
8441The distinguished name specified for this replication operation already exists.
8442The replication system encountered an internal error.
8443The replication operation encountered a database inconsistency.
8444The server specified for this replication operation could not be contacted.
8445The replication operation encountered an object with an invalid instance type.
8446The replication operation failed to allocate memory.
8447The replication operation encountered an error with the mail system.
8448The replication reference information for the target server already exists.
8449The replication reference information for the target server does not exist.
8450The naming context cannot be removed because it is replicated to another server.
8451The replication operation encountered a database error.
8452The naming context is in the process of being removed or is not replicated from the specified server.
8453Replication access was denied.
8454The requested operation is not supported by this version of the directory service.
8455The replication remote procedure call was cancelled.
8456The source server is currently rejecting replication requests.
8457The destination server is currently rejecting replication requests.
8458The replication operation failed due to a collision of object names.
8459The replication source has been reinstalled.
8460The replication operation failed because a required parent object is missing.
8461The replication operation was preempted.
8462The replication synchronization attempt was abandoned because of a lack of updates.
8463The replication operation was terminated because the system is shutting down.
8464The replication synchronization attempt failed as the destination partial attribute set is not a subset of source partial attribute set.
8465The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
8466The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
8467The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer. You must upgrade the operating system on a domain controller in the source forest before this computer can be added as a domain controller to that forest.
8468Schema update failed: An attribute with the same link identifier already exists.
8469Name translation: Generic processing error.
8470Name translation: Could not find the name or insufficient right to see name.
8471Name translation: Input name mapped to more than one output name.
8472Name translation: Input name found, but not the associated output format.
8473Name translation: Unable to resolve completely, only the domain was found.
8474Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
8475Modification of a constructed att is not allowed.
8476The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
8477The replication request has been posted; waiting for reply.
8478The requested operation requires a directory service, and none was available.
8479The LDAP display name of the class or attribute contains non-ASCII characters.
8480The requested search operation is only supported for base searches.
8481The search failed to retrieve attributes from the database.
8482The schema update operation tried to add a backward link attribute that has no corresponding forward link.
8483Source and destination of a cross domain move do not agree on the object’s epoch number. Either source or destination does not have the latest version of the object.
8484Source and destination of a cross domain move do not agree on the object’s current name. Either source or destination does not have the latest version of the object.
8485Source and destination of a cross domain move operation are identical. Caller should use local move operation instead of cross domain move operation.
8486Source and destination for a cross domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.
8487Destination of a cross domain move is not authoritative for the destination naming context.
8488Source and destination of a cross domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.
8489Object being moved across domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.
8490Another operation which requires exclusive access to the PDC PSMO is already in progress.
8491A cross domain move operation failed such that the two versions of the moved object exist – one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.
8492This object may not be moved across domain boundaries either because cross domain moves for this class are disallowed, or the object has some special characteristics, eg: trust account or restricted RID, which prevent its move.
8493Can’t move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.
8494A naming context head must be the immediate child of another naming context head, not of an interior node.
8495The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)
8496Destination domain must be in native mode.
8497The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.
8498Cross-domain move of non-empty account groups is not allowed.
8499Cross-domain move of non-empty resource groups is not allowed.
8500The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.
8501Tree deletions starting at an object which has an NC head as a descendant are not allowed.
8502The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.
8503The directory service failed to identify the list of objects to delete while attempting a tree deletion.
8504Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Click OK to shut down the system and reboot into Directory Services Restore Mode. Check the event log for detailed information.
8505Only an administrator can modify the membership list of an administrative group.
8506Cannot change the primary group ID of a domain controller account.
8507An attempt is made to modify the base schema.
8508Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.
8509Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
8510An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.
8511The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.
8512The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
8513The specified group type is invalid.
8514Cannot nest global groups in a mixed domain if the group is security-enabled.
8515Cannot nest local groups in a mixed domain if the group is security-enabled.
8516A global group cannot have a local group as a member.
8517A global group cannot have a universal group as a member.
8518A universal group cannot have a local group as a member.
8519A global group cannot have a cross-domain member.
8520A local group cannot have another cross-domain local group as a member.
8521A group with primary members cannot change to a security-disabled group.
8522The schema cache load failed to convert the string default SD on a class-schema object.
8523Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
8524The DSA operation is unable to proceed because of a DNS lookup failure.
8525While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
8526The Security Descriptor attribute could not be read.
8527The object requested was not found, but an object with that key was found.
8528The syntax of the linked attributed being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1.
8529Security Account Manager needs to get the boot password.
8530Security Account Manager needs to get the boot key from floppy disk.
8531Directory Service cannot start.
8532Directory Services could not start.
8533The connection between client and server requires packet privacy or better.
8534The source domain may not be in the same forest as destination.
8535The destination domain must be in the forest.
8536The operation requires that destination domain auditing be enabled.
8537The operation couldn’t locate a DC for the source domain.
8538The source object must be a group or user.
8539The source object’s SID already exists in destination forest.
8540The source and destination object must be of the same type.
8541Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.
8542Schema information could not be included in the replication request.
8543The replication operation could not be completed due to a schema incompatibility.
8544The replication operation could not be completed due to a previous schema incompatibility.
8545The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.
8546The requested domain could not be deleted because there exist domain controllers that still host this domain.
8547The requested operation can be performed only on a global catalog server.
8548A local group can only be a member of other local groups in the same domain.
8549Foreign security principals cannot be members of universal groups.
8550The attribute is not allowed to be replicated to the GC because of security reasons.
8551The checkpoint with the PDC could not be taken because there are too many modifications being processed currently.
8552The operation requires that source domain auditing be enabled.
8553Security principal objects can only be created inside domain naming contexts.
8554A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
8555A Filter was passed that uses constructed attributes.
8556The unicodePwd attribute value must be enclosed in double quotes.
8557Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.
8558For security reasons, the operation must be run on the destination DC.
8559For security reasons, the source DC must be NT4SP4 or greater.
8560Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
8561Directory Services could not start because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.
8562Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.
8563This version of Windows is too old to support the current directory forest behavior. You must upgrade the operating system on this server before it can become a domain controller in this forest.
8564This version of Windows is too old to support the current domain behavior. You must upgrade the operating system on this server before it can become a domain controller in this domain.
8565This version of Windows no longer supports the behavior version in use in this directory forest. You must advance the forest behavior version before this server can become a domain controller in the forest.
8566This version of Windows no longer supports the behavior version in use in this domain. You must advance the domain behavior version before this server can become a domain controller in the domain.
8567The version of Windows is incompatible with the behavior version of the domain or forest.
8568The behavior version cannot be increased to the requested value because Domain Controllers still exist with versions lower than the requested value.
8569The behavior version value cannot be increased while the domain is still in mixed domain mode. You must first change the domain to native mode before increasing the behavior version.
8570The sort order requested is not supported.
8571Found an object with a non unique name.
8572The machine account was created pre-NT4. The account needs to be recreated.
8573The database is out of version store.
8574Unable to continue operation because multiple conflicting controls were used.
8575Unable to find a valid security descriptor reference domain for this partition.
8576Schema update failed: The link identifier is reserved.
8577Schema update failed: There are no link identifiers available.
8578An account group cannot have a universal group as a member.
8579Rename or move operations on naming context heads or read-only objects are not allowed.
8580Move operations on objects in the schema naming context are not allowed.
8581A system flag has been set on the object and does not allow the object to be moved or renamed.
8582This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
8583Unable to resolve completely, a referral to another forest is generated.
8584The requested action is not supported on standard server.
8585Could not access a partition of the Active Directory located on a remote server. Make sure at least one server is running for the partition in question.
8586The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.
8587The thread limit for this request was exceeded.
8588The Global catalog server is not in the closet site.
8589The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.
8590The Directory Service failed to enter single user mode.
8591The Directory Service cannot parse the script because of a syntax error.
8592The Directory Service cannot process the script because of an error.
8593The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).
8594The directory service binding must be renegotiated due to a change in the server extensions information.
8595Operation not allowed on a disabled cross ref.
8596Schema update failed: No values for msDS-IntId are available.
8597Schema update failed: Duplicate msDS-INtId. Retry the operation.
8598Schema deletion failed: attribute is used in rDNAttID.
8599The directory service failed to authorize the request.
8600The Directory Service cannot process the script because it is invalid.
8601The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation’s error is in the extended data.
9001DNS server unable to interpret format.
9002DNS server failure.
9003DNS name does not exist.
9004DNS request not supported by name server.
9005DNS operation refused.
9006DNS name that ought not exist, does exist.
9007DNS RR set that ought not exist, does exist.
9008DNS RR set that ought to exist, does not exist.
9009DNS server not authoritative for zone.
9010DNS name in update or prereq is not in zone.
9016DNS signature failed to verify.
9017DNS bad key.
9018DNS signature validity expired.
9501No records found for given DNS query.
9502Bad DNS packet.
9503No DNS packet.
9504DNS error, check rcode.
9505Unsecured DNS packet.
9551Invalid DNS type.
9552Invalid IP address.
9553Invalid property.
9554Try DNS operation again later.
9555Record for given name and type is not unique.
9556DNS name does not comply with RFC specifications.
9557DNS name is a fully-qualified DNS name.
9558DNS name is dotted (multi-label).
9559DNS name is a single-part name.
9560DSN name contains an invalid character.
9561DNS name is entirely numeric.
9562The operation requested is not permitted on a DNS root server.
9601DNS zone does not exist.
9602DNS zone information not available.
9603Invalid operation for DNS zone.
9604Invalid DNS zone configuration.
9605DNS zone has no start of authority (SOA) record.
9606DNS zone has no name server (NS) record.
9607DNS zone is locked.
9608DNS zone creation failed.
9609DNS zone already exists.
9610DNS automatic zone already exists.
9611Invalid DNS zone type.
9612Secondary DNS zone requires master IP address.
9613DNS zone not secondary.
9614Need secondary IP address.
9615WINS initialization failed.
9616Need WINS servers.
9617NBTSTAT initialization call failed.
9618Invalid delete of start of authority (SOA)
9619A conditional forwarding zone already exists for that name.
9620This zone must be configured with one or more master DNS server IP addresses.
9621The operation cannot be performed because this zone is shutdown.
9651Primary DNS zone requires datafile.
9652Invalid datafile name for DNS zone.
9653Failed to open datafile for DNS zone.
9654Failed to write datafile for DNS zone.
9655Failure while reading datafile for DNS zone.
9701DNS record does not exist.
9702DNS record format error.
9703Node creation failure in DNS.
9704Unknown DNS record type.
9705DNS record timed out.
9706Name not in DNS zone.
9707CNAME loop detected.
9708Node is a CNAME DNS record.
9709A CNAME record already exists for given name.
9710Record only at DNS zone root.
9711DNS record already exists.
9712Secondary DNS zone data error.
9713Could not create DNS cache data.
9714DNS name does not exist.
9715Could not create pointer (PTR) record.
9716DNS domain was undeleted.
9717The directory service is unavailable.
9718DNS zone already exists in the directory service.
9719DNS server not creating or reading the boot file for the directory service integrated DNS zone.
9751DNS AXFR (zone transfer) complete.
9752DNS zone transfer failed.
9753Added local WINS server.
9801Secure update call needs to continue update request.
9851TCP/IP network protocol not installed.
9852No DNS servers configured for local system.
9901The specified directory partition does not exist.
9902The specified directory partition already exists.
9903The DS is not enlisted in the specified directory partition.
9904The DS is already enlisted in the specified directory partition.
10004A blocking operation was interrupted by a call to WSACancelBlockingCall.
10009The file handle supplied is not valid.
10013An attempt was made to access a socket in a way forbidden by its access permissions.
10014The system detected an invalid pointer address in attempting to use a pointer argument in a call.
10022An invalid argument was supplied.
10024Too many open sockets.
10035A non-blocking socket operation could not be completed immediately.
10036A blocking operation is currently executing.
10037An operation was attempted on a non-blocking socket that already had an operation in progress.
10038An operation was attempted on something that is not a socket.
10039A required address was omitted from an operation on a socket.
10040A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
10041A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
10042An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.
10043The requested protocol has not been configured into the system, or no implementation for it exists.
10044The support for the specified socket type does not exist in this address family.
10045The attempted operation is not supported for the type of object referenced.
10046The protocol family has not been configured into the system or no implementation for it exists.
10047An address incompatible with the requested protocol was used.
10048Only one usage of each socket address (protocol/network address/port) is normally permitted.
10049The requested address is not valid in its context.
10050A socket operation encountered a dead network.
10051A socket operation was attempted to an unreachable network.
10052The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
10053An established connection was aborted by the software in your host machine.
10054An existing connection was forcibly closed by the remote host.
10055An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
10056A connect request was made on an already connected socket.
10057A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
10058A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.
10059Too many references to some kernel object.
10060A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
10061No connection could be made because the target machine actively refused it.
10062Cannot translate name.
10063Name component or name was too long.
10064A socket operation failed because the destination host was down.
10065A socket operation was attempted to an unreachable host.
10066Cannot remove a directory that is not empty.
10067A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.
10068Ran out of quota.
10069Ran out of disk quota.
10070File handle reference is no longer available.
10071Item is not available locally.
10091WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.
10092The Windows Sockets version requested is not supported.
10093Either the application has not called WSAStartup, or WSAStartup failed.
10101Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.
10102No more results can be returned by WSALookupServiceNext.
10103A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
10104The procedure call table is invalid.
10105The requested service provider is invalid.
10106The requested service provider could not be loaded or initialized.
10107A system call that should never fail has failed.
10108No such service is known. The service cannot be found in the specified name space.
10109The specified class was not found.
10110No more results can be returned by WSALookupServiceNext.
10111A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
10112A database query failed because it was actively refused.
11001No such host is known.
11002This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
11003A non-recoverable error occurred during a database lookup.
11004The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
11005At least one reserve has arrived.
11006At least one path has arrived.
11007There are no senders.
11008There are no receivers.
11009Reserve has been confirmed.
11010Error due to lack of resources.
11011Rejected for administrative reasons – bad credentials.
11012Unknown or conflicting style.
11013Problem with some part of the filterspec or providerspecific buffer in general.
11014Problem with some part of the flowspec.
11015General QOS error.
11016An invalid or unrecognized service type was found in the flowspec.
11017An invalid or inconsistent flowspec was found in the QOS structure.
11018Invalid QOS provider-specific buffer.
11019An invalid QOS filter style was used.
11020An invalid QOS filter type was used.
11021An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR.
11022An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.
11023An incorrect number of flow descriptors was specified in the QOS structure.
11024An unrecognized object was found in the QOS provider-specific buffer.
11025An invalid policy object was found in the QOS provider-specific buffer.
11026An invalid QOS flow descriptor was found in the flow descriptor list.
11027An invalid or inconsistent flowspec was found in the QOS provider-specific buffer.
11028An invalid FILTERSPEC was found in the QOS provider-specific buffer.
11029An invalid shape discard mode object was found in the QOS provider-specific buffer.
11030An invalid shaping rate object was found in the QOS provider-specific buffer.
11031A reserved policy element was found in the QOS provider-specific buffer.
13000The specified quick mode policy already exists.
13001The specified quick mode policy was not found.
13002The specified quick mode policy is being used.
13003The specified main mode policy already exists.
13004The specified main mode policy was not found.
13005The specified main mode policy is being used.
13006The specified main mode filter already exists.
13007The specified main mode filter was not found.
13008The specified transport mode filter already exists.
13009The specified transport mode filter does not exist.
13010The specified main mode authentication list exists.
13011The specified main mode authentication list was not found.
13012The specified quick mode policy is being used.
13013The specified main mode policy was not found.
13014The specified quick mode policy was not found.
13015The manifest file contains one or more syntax errors.
13016The application attempted to activate a disabled activation context.
13017The requested lookup key was not found in any active activation context.
13018The Main Mode filter is pending deletion.
13019The transport filter is pending deletion.
13020The tunnel filter is pending deletion.
13021The Main Mode policy is pending deletion.
13022The Main Mode authentication bundle is pending deletion.
13023The Quick Mode policy is pending deletion.
13801IKE authentication credentials are unacceptable.
13802IKE security attributes are unacceptable.
13803IKE Negotiation in progress.
13804General processing error.
13805Negotiation timed out.
13806IKE failed to find valid machine certificate.
13807IKE SA deleted by peer before establishment completed.
13808IKE SA deleted before establishment completed.
13809Negotiation request sat in Queue too long.
13810Negotiation request sat in Queue too long.
13811Negotiation request sat in Queue too long.
13812Negotiation request sat in Queue too long.
13813No response from peer.
13814Negotiation took too long.
13815Negotiation took too long.
13816Unknown error occurred.
13817Certificate Revocation Check failed.
13818Invalid certificate key usage.
13819Invalid certificate type.
13820No private key associated with machine certificate.
13822Failure in Diffie-Helman computation.
13824Invalid header.
13825No policy configured.
13826Failed to verify signature.
13827Failed to authenticate using Kerberos.
13828Peer’s certificate did not have a public key.
13829Error processing error payload.
13830Error processing SA payload.
13831Error processing Proposal payload.
13832Error processing Transform payload.
13833Error processing KE payload.
13834Error processing ID payload.
13835Error processing Cert payload.
13836Error processing Certificate Request payload.
13837Error processing Hash payload.
13838Error processing Signature payload.
13839Error processing Nonce payload.
13840Error processing Notify payload.
13841Error processing Delete Payload.
13842Error processing VendorId payload.
13843Invalid payload received.
13844Soft SA loaded.
13845Soft SA torn down.
13846Invalid cookie received..
13847Peer failed to send valid machine certificate.
13848Certification Revocation check of peer’s certificate failed.
13849New policy invalidated SAs formed with old policy.
13850There is no available Main Mode IKE policy.
13851Failed to enabled TCB privilege.
13852Failed to load SECURITY.DLL.
13853Failed to obtain security function table dispatch address from SSPI.
13854Failed to query Kerberos package to obtain max token size.
13855Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.
13856Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).
13857Failed to obtain new SPI for the inbound SA from Ipsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.
13858Given filter is invalid.
13859Memory allocation failed.
13860Failed to add Security Association to IPSec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.
13861Invalid policy.
13862Invalid DOI.
13863Invalid situation.
13864Diffie-Hellman failure.
13865Invalid Diffie-Hellman group.
13866Error encrypting payload.
13867Error decrypting payload.
13868Policy match error.
13869Unsupported ID.
13870Hash verification failed.
13871Invalid hash algorithm.
13872Invalid hash size.
13873Invalid encryption algorithm.
13874Invalid authentication algorithm.
13875Invalid certificate signature.
13876Load failed.
13877Deleted via RPC call.
13878Temporary state created to perform reinit. This is not a real failure.
13879The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.
13881Key length in certificate is too small for configured security requirements.
13882Max number of established MM SAs to peer exceeded.
13883IKE received a policy that disables negotiation.
13884ERROR_IPSEC_IKE_NEG_STATUS_END
14000The requested section was not present in the activation context.
14001This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
14002The application binding data format is invalid.
14003The referenced assembly is not installed on your system.
14004The manifest file does not begin with the required tag and format information.
14005The manifest file contains one or more syntax errors.
14006The application attempted to activate a disabled activation context.
14007The requested lookup key was not found in any active activation context.
14008A component version required by the application conflicts with another component version already active.
14009The type requested activation context section does not match the query API used.
14010Lack of system resources has required isolated activation to be disabled for the current thread of execution.
14011An attempt to set the process default activation context failed because the process default activation context was already set.
14012The encoding group identifier specified is not recognized.
14013The encoding requested is not recognized.
14014The manifest contains a reference to an invalid URI.
14015The application manifest contains a reference to a dependent assembly which is not installed.
14016The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed.
14017The manifest contains an attribute for the assembly identity which is not valid.
14018The manifest is missing the required default namespace specification on the assembly element.
14019The manifest has a default namespace specified on the assembly element but its value is not “urn:schemas-microsoft-com:asm.v1”.
14020The private manifest probe has crossed the reparse-point-associated path.
14021Two or more components referenced directly or indirectly by the application manifest have files by the same name.
14022Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.
14023Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.
14024Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.
14025Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.
14026Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.
14027Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.
14028A component’s file does not match the verification information present in the component manifest.
14029The policy manifest contains one or more syntax errors.
14030Manifest Parse Error : A string literal was expected, but no opening quote character was found.
14031Manifest Parse Error : Incorrect syntax was used in a comment.
14032Manifest Parse Error : A name was started with an invalid character.
14033Manifest Parse Error : A name contained an invalid character.
14034Manifest Parse Error : A string literal contained an invalid character.
14035Manifest Parse Error : Invalid syntax for an XML declaration.
14036Manifest Parse Error : An invalid character was found in text content.
14037Manifest Parse Error : Required white space was missing.
14038Manifest Parse Error : The character ‘>’ was expected.
14039Manifest Parse Error : A semi colon character was expected.
14040Manifest Parse Error : Unbalanced parentheses.
14041Manifest Parse Error : Internal error.
14042Manifest Parse Error : White space is not allowed at this location.
14043Manifest Parse Error : End of file reached in invalid state for current encoding.
14044Manifest Parse Error : Missing parenthesis.
14045Manifest Parse Error : A single or double closing quote character (\’ or \”) is missing.
14046Manifest Parse Error : Multiple colons are not allowed in a name.
14047Manifest Parse Error : Invalid character for decimal digit.
14048Manifest Parse Error : Invalid character for hexadecimal digit.
14049Manifest Parse Error : Invalid Unicode character value for this platform.
14050Manifest Parse Error : Expecting white space or ‘?’.
14051Manifest Parse Error : End tag was not expected at this location.
14052Manifest Parse Error : The following tags were not closed: %1.
14053Manifest Parse Error : Duplicate attribute.
14054Manifest Parse Error : Only one top level element is allowed in an XML document.
14055Manifest Parse Error : Invalid at the top level of the document.
14056Manifest Parse Error : Invalid XML declaration.
14057Manifest Parse Error : XML document must have a top level element.
14058Manifest Parse Error : Unexpected end of file.
14059Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.
14060Manifest Parse Error : Element was not closed.
14061Manifest Parse Error : End element was missing the character ‘>’.
14062Manifest Parse Error : A string literal was not closed.
14063Manifest Parse Error : A comment was not closed.
14064Manifest Parse Error : A declaration was not closed.
14065Manifest Parse Error : A CDATA section was not closed.
14066Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string “xml”.
14067Manifest Parse Error : System does not support the specified encoding.
14068Manifest Parse Error : Switch from current encoding to specified encoding not supported.
14069Manifest Parse Error : The name ‘xml’ is reserved and must be lower case.
14070Manifest Parse Error : The standalone attribute must have the value ‘yes’ or ‘no’.
14071Manifest Parse Error : The standalone attribute cannot be used in external entities.
14072Manifest Parse Error : Invalid version number.
14073Manifest Parse Error : Missing equals sign between attribute and attribute value.
14074Assembly Protection Error: Unable to recover the specified assembly.
14075Assembly Protection Error: The public key for an assembly was too short to be allowed.
14076Assembly Protection Error: The catalog for an assembly is not valid, or does not match the assembly’s manifest.
14077An HRESULT could not be translated to a corresponding Win32 error code.
14078Assembly Protection Error: The catalog for an assembly is missing.
14079The supplied assembly identity is missing one or more attributes which must be present in this context.
14080The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.