Home | Recovery | Cisco How To Net How To | Blog | Search | Forums | Services | Setup Guide | Chicagotech MVP | IT Exam Practice  |  About Us | Contact Us|

Chicago Area Laptop for rent: $35 per day plus $10 for additional day
rental

 

Windows System Exit Code Description - 2000 to 9999

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. 

Related Topics

Windows System Exit Code Description - 1 to 999

Windows System Exit Code
Description - 1000 to 1999

Windows System Exit Code
Description - 2000 to 9999

Windows System Exit Code
Description - 10000 and above

 

Bob Lin Photography services

Real Estate Photography services 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.