Windows Exit Codes
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.
As always, it is a pleasure doing business with you. We are very happy with the capabilities of the new version of Automize and are looking forward with moving ahead with our first production system based on this software. –Automize Enterprise User
Thanks for your timely response. You make a great product, and we're integrating it more and more into our daily production activities. I will try out these FTP suggestions as you've outlined. –JaSFTP User
Just wanted to compliment you folks on a great product. your product is working flawlessly! I'll definitely be purchasing it, and telling every other "IT type" I know about it! Thanks so much. –Automize User
Your program was exactly what I was looking for...you have all the features that I require; all in one program!!–AbleFTP user