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