LDAP server error codes are described in RFC 4511.
Client's error codes (>80) are declared in SecureBlackbox.
[.NET] [Pascal] [C++]
The requested client operation completed successfully.
Indicates an internal server error.
The server has received an invalid or malformed request from the client.
Time limit exceeded. Incomplete results are returned if search operations were requested.
Size limit exceeded during a search operation; incomplete results are returned.
Does not indicate an error condition. Indicates that the results of a compare operation are False.
Does not indicate an error condition. Indicates that the results of a compare operation are true.
The client has requested an unsupported authentication method during a bind operation.
Indicates one of the following:
In a bind request, the LDAP server accepts only strong authentication.
In a client request, the client requested an operation that requires strong authentication (e.g., delete).
In an unsolicited notice of disconnection, the LDAP server discovers the security protecting the communication between the client and server has unexpectedly failed or been compromised.
Does not indicate an error condition. In LDAPv3, indicates that a referral needs to be chased to complete the operation.
Indicates that an administrative limit has been exceeded.
A critical control is unrecognized.
Indicates that data confidentiality protections are required.
The server requires the client to send a new bind request, with the same SASL mechanism, to continue the authentication process.
The named entry does not contain the specified attribute or attribute value.
A request field contains an unrecognized attribute description.
Indicates that an attempt was made (e.g., in an assertion) to use a matching rule not defined for the attribute type concerned.
Indicates that the client supplied an attribute value that does not conform to the constraints placed upon it by the data model. For example, this code is returned when multiple values are supplied to an attribute that has a SINGLE-VALUE constraint.
The client supplied an attribute or value to be added to an entry, but the attribute or value already exists.
Indicates that a purported attribute value does not conform to the syntax of the attribute.
Indicates that the object does not exist in the DIT (directory information tree).
Indicates that an alias problem has occurred. For example, the code may be used to indicate an alias has been dereferenced that names no object.
Indicates that an LDAPDN or RelativeLDAPDN field (e.g., search base, target entry, ModifyDN newrdn, etc.) of a request does not conform to the required syntax or contains attribute values that do not conform to the syntax of the attribute's type.
Indicates that a problem occurred while dereferencing an alias. Typically, an alias was encountered in a situation where it was not allowed or where the access was denied.
The server requires the client that had attempted to bind anonymously or without supplying credentials to provide some form of credentials.
Indicates that the provided credentials (e.g., the user name and password) are invalid.
The client does not have sufficient access rights to perform the operation.
The serveris too busy to service the requested operation.
Indicates that the server is shutting down or a subsystem necessary to complete the operation is offline.
Indicates that the server is unwilling to perform the operation.
The server has detected an internal loop (e.g., while dereferencing aliases or chaining an operation).
The entry's name violates naming restrictions.
The entry violates object class restrictions.
Indicates that the operation is inappropriately acting upon a non-leaf entry.
Indicates that the operation is inappropriately attempting to remove a value that forms the entry's relative distinguished name.
Indicates that the request cannot be fulfilled (added, moved, or renamed) as the target entry already exists.
Indicates that an attempt to modify the object class(es) of an entry's 'objectClass' attribute is prohibited. For example, this code is returned when a client attempts to modify the structural object class of an entry.
Indicates that the operation cannot be performed as it would affect multiple servers (DSAs).
Indicates the server has encountered an internal error.
Indicates that a received message has wrong format.
An error occured during bind.
Does not necessarily mean an error condition. Indicates that search has returned zero results.
Reserved for future use.
Reserved for future use.
Inidicates that client has received a response of unknown type.
Indicates an error during SASL authentication.
Wrong URL provided by the client.
Indicates an invalid response received from the server on the client's request to remove an entry.
Indicates an invalid response received from the server on the client's request to add an entry.
Indicates an invalid response received from the server on the client's request to modify an entry.