0 |
Ldap_success |
Indicates the requested client operation completed successfully. |
1 |
Ldap_operations_error |
Indicates an internal error. The server is unable to respond with a more specific error and was also unable to properly respond to a request. It does not indicate that the client had sent an erroneous message. In NDS 8.3x through NDS 7.xx, this is the default error for NDS errors, which does not map to an LDAP error code. To conform to the new LDAP drafts, NDS 8.5 uses (0x50) for such errors. |
2 |
Ldap_protocol_error |
Indicates the server has received a invalid or malformed request from the client. |
3 |
ldap_timelimit_exceeded |
Indicates that the operation's time limit specified by either the client or the server has been exceeded. On search operations, incomplete results is returned. |
4 |
ldap_sizelimit_exceeded |
Indicates in a search operation, the size limit specified by the client or the server have been exceeded. Incomplete results is returned. |
5 |
Ldap_compare_false |
Does not indicate an error condition. Indicates that the results of a compare operation is false. |
6 |
Ldap_compare_true |
Does not indicate an error condition. Indicates that the results of a compare operation is true. |
7 |
ldap_auth_method_not_supported |
Indicates that during a bind operation the client requested an authentication method not supported by the LDAP server. |
8 |
Ldap_strong_auth_required |
Indicates one of the following:in bind requests, the LDAP server accepts only strong authentication. In a client request, the client requested an operation such as delete that requires strong authentication. 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. |
9 |
|
Reserved. |
10 |
Ldap_referral |
Does not indicate an error condition. In LDAPv3, indicates that the server does is not on hold the target entry of the request, but that the servers in the referral F Ield May. |
11 |
ldap_adminlimit_exceeded |
Indicates that a LDAP server limit set by a administrative authority has been exceeded. |
12 |
Ldap_unavailable_critical_extension |
Indicates that the LDAP server is unable to satisfy a request because one or more critical extensions were not available. Either the server does not the control or the control was not appropriate for the operation type. |
13 |
Ldap_confidentiality_required |
Indicates the session is not protected by a protocol such as Transport Layer Security (TLS), which provides session C Onfidentiality. |
14 |
Ldap_sasl_bind_in_progress |
Does not indicate a error condition, but indicates that the server was ready for the next step in the process. The client must send the server the same SASL mechanism to continue the process. |
15 |
|
Not used. |
16 |
Ldap_no_such_attribute |
Indicates the attribute specified in the Modify or compare operation does not exist in the entry. |
17 |
Ldap_undefined_type |
Indicates the attribute specified in the Modify or add operation does isn't exist in the LDAP server ' s schema. |
18 |
Ldap_inappropriate_matching |
Indicates the matching rule specified in the search filter does not match a rule defined for the attribute ' s syntax. |
19 |
Ldap_constraint_violation |
Indicates the attribute value specified in a modify, add, or modify DN operation violates constraints placed on the A Ttribute. The constraint can be a size or content (string only, no binary). |
20 |
Ldap_type_or_value_exists |
Indicates the attribute value specified in a modify or add operation already exists as a value for that attribute. |
21st |
Ldap_invalid_syntax |
Indicates the attribute value specified in an Add, compare, or modify operation are an unrecognized or invalid syntax For the attribute. |
22-31 |
|
Not used. |
32 |
Ldap_no_such_object |
Indicates the target object cannot be found. This code isn't returned on following operations:search operations it find the Search base but cannot find any entries That match the search filter. Bind operations. |
33 |
Ldap_alias_problem |
Indicates that a error occurred when a alias was dereferenced. |
34 |
Ldap_invalid_dn_syntax |
Indicates the syntax of the DN is incorrect. (If the DN syntax is correct, but the LDAP server ' s structure rules does not permit the operation, the server returns Ldap_u Nwilling_to_perform.) |
35 |
Ldap_is_leaf |
Indicates that the specified operation cannot is performed on a leaf entry. (This code was not a currently in the LDAP specifications, but was reserved for this constant.) |
36 |
Ldap_alias_deref_problem |
Indicates that during a search operation, either the client does not has access rights to read the Aliased object ' s name Or dereferencing is not allowed. |
37-47 |
|
Not used. |
48 |
Ldap_inappropriate_auth |
Indicates that during a bind operation, the client was attempting to use an authentication method that the client cannot us E correctly. For example, either of the following cause this Error:the client returns simple credentials when strong credentials is R Equired ... OR ... The client returns a DN and a password for a simple bind when the entry does not has a password defined. |
49 |
Ldap_invalid_credentials |
Indicates that during a bind operation one of the following Occurred:the client passed either an incorrect DN or password , or the password is incorrect because it has expired, intruder detection have locked the account, or another similar Reaso N. See the data code for more information. |
49/52e |
Ad_invalid CREDENTIALS |
Indicates an Active Directoryacceptsecuritycontext error, which was returned when the username was valid but T He combination of password and user credential is invalid. This is the AD equivalent of LDAP error code 49. |
49/525 |
USER not FOUND |
Indicates an Active Directory (AD)acceptsecuritycontext data error, which is returned when the username is invalid. |
49/530 |
Not_permitted_to_logon_at_this_time |
Indicates an Active Directoryacceptsecuritycontext data error which is the logon failure caused because the user Is isn't permitted to log on at this time. Returns presented with a valid username and valid password credential. |
49/531 |
Restricted_to_specific_machines |
Indicates an Active Directoryacceptsecuritycontext data error which is the logon failure caused because the user Is isn't permitted to log on from this computer. Returns presented with a valid username and valid password credential. |
49/532 |
Password_expired |
Indicates an Active Directory (AD)acceptsecuritycontext data error, which is a logon failure. The specified account password have expired. Returns presented with valid username and password credential. |
49/533 |
Account_disabled |
Indicates an Active Directory (AD)acceptsecuritycontext data error, which is a logon failure. The account is currently disabled. Returns presented with valid username and password credential. |
49/568 |
Error_too_many_context_ids |
Indicates that during a log-on attempt, the user's security context accumulated too many security IDs. This is a issue with the specific LDAP user Object/account which should being investigated by the LDAP administrator. |
49/701 |
Account_expired |
Indicates an Active Directory (AD)acceptsecuritycontext data error, which is a logon failure. The user's account has expired. Returns presented with valid username and password credential. |
49/773 |
USER must RESET PASSWORD |
Indicates an Active Directory (AD)acceptsecuritycontext data error. The user ' s password must is changed before logging on the first time. Returns presented with valid user-name and password credential. |
50 |
Ldap_insufficient_access |
Indicates the caller does not having sufficient rights to perform the requested operation. |
51 |
Ldap_busy |
Indicates that the LDAP server was too busy to process the client request at this time if the client waits and resubmit s the request, the server is able to process it then. |
52 |
Ldap_unavailable |
Indicates that the LDAP server cannot process the client's bind request, usually because it's shutting down. |
53 |
Ldap_unwilling_to_perform |
Indicates that the LDAP server cannot process the request because of server-defined restrictions. This error was returned for the following Reasons:the add entry request violates the server ' s structure rules ... OR ... The Modify attribute request specifies attributes that users cannot modify ... OR ... Password restrictions prevent the action ... OR ... Connection restrictions prevent the action. |
54 |
Ldap_loop_detect |
Indicates that the client discovered a alias or referral loop, and is thus unable to complete this request. |
55-63 |
|
Not used. |
64 |
Ldap_naming_violation |
Indicates that the Add or modify DN operation violates the schema ' s structure rules. For example, The request places the entry subordinate to an alias. The request places the entry subordinate to a container that's forbidden by the containment rules. The RDN for the entry uses a forbidden attribute type. |
65 |
Ldap_object_class_violation |
Indicates the add, modify, or modify DN operation violates the object class rules for the entry. For example, the following types's request return this error: The Add or modify operation tries to add an entry without a value for a required attribute. The Add or modify operation tries to add an entry with a value for a attribute which the class definition does not Contai N. The modify operation tries to remove a required attribute without removing the auxiliary class that defines the Attribu Te as required. |
66 |
Ldap_not_allowed_on_nonleaf |
Indicates that the requested operation are permitted only on leaf entries. For example, the following types of requests return this error: The client requests a delete operation on a parent entry. The client request a modify DN operation on a parent entry. |
67 |
Ldap_not_allowed_on_rdn |
Indicates that the modify operation attempted to remove a attribute value that forms the entry ' s relative distinguished n Ame. |
68 |
Ldap_already_exists |
Indicates that the add operation attempted to add a entry that already exists, or so the modify operation attempted to Rename an entry to the name of a entry that already exists. |
69 |
Ldap_no_object_class_mods |
Indicates the modify operation attempted to modify the structure rules of an object class. |
70 |
Ldap_results_too_large |
Reserved for CLDAP. |
71 |
Ldap_affects_multiple_dsas |
Indicates the Modify DN operation moves the entry from one LDAP server to another and requires more than one LDAP ser Ver. |
72-79 |
|
Not used. |
80 |
Ldap_other |
Indicates an unknown error condition. The the default value for NDS error codes which does not map to other LDAP error codes. |