staticint INAPPROPRIATE_AUTHENTICATION Indicates that during a bind operation, the client is attempting to use an authentication method that the client cannot use correctly. INSUFFICIENT_ACCESS_RIGHTS = 50 See Also:Constant Field Values BUSY public static final int BUSY Indicates that the LDAP server is too busy to process the client request at this time, but In NDS 8.3x through NDS 7.xx, this was the default error for eDirectory errors that did not map to an LDAP error code. fix Restart the LDAP server and NAS. Source
See also TID 10067376. INVALID_ATTRIBUTE_SYNTAX = 21 See Also:Constant Field Values NO_SUCH_OBJECT public static final int NO_SUCH_OBJECT Indicates the target object cannot be found. See our new home at SUSE.com Services & Support + Services Overview Help Yourself Knowledgebase Support Forums Documentation Product Support Lifecycle Let Us Help Open Service Request Maintenance and Support Plans NOT_ALLOWED_ON_NONLEAF = 66 See Also:Constant Field Values NOT_ALLOWED_ON_RDN public static final int NOT_ALLOWED_ON_RDN Indicates that the modify operation attempted to remove an attribute value that forms the entry's relative distinguished http://www.novell.com/documentation/developer/ldapover/ldap_enu/data/a3zxc1a.html
The attribute is not defined in the tabledef.conf file. In a client request, the client requested an operation such as delete that requires strong authentication. staticint INVALID_DN_SYNTAX Indicates that the syntax of the DN is incorrect.
fix Check to ensure the LDAP server is running. LDAP Error 49 - Invalid credentials Cause/Fix: The user has input the incorrect password. cause Connection to the directory server has been lost. All Rights Reserved.
The String is used either as a message key to obtain a localized messsage from ExceptionMessages, or if there is no key in the resource matching the text, it is used LDAP Error 12 - Criticial extension is unavailable Cause/Fix: GroupWise requires eDirectory LDAP Services version 85.12 or greater when using the LDAP Username and Password options. ENTRY_ALREADY_EXISTS = 68 See Also:Constant Field Values OBJECT_CLASS_MODS_PROHIBITED public static final int OBJECT_CLASS_MODS_PROHIBITED Indicates that the modify operation attempted to modify the structure rules of an object class. LDAP Error 81 - Can't contact LDAP server Cause/Fix: The POA can't contact the LDAP Server.
cause Wrong LDAP DN syntax. In this situation, the POA must know the full distinguished name of the user in the LDAP directory it is querying. PASSWORD_TOO_SHORT -216 SYNTAX_VIOLATION -613 DN_TOO_LONG -353 CANT_HAVE_MULITPLE_VALUES -612 TYPE_OR_VALUE_EXISTS 20 DUPLICATE_VALUE -614 The value must be unique and the one specified is not. LOOP_DETECT = 54 See Also:Constant Field Values NAMING_VIOLATION public static final int NAMING_VIOLATION Indicates that the add or modify DN operation violates the schema's structure rules.
Connection restrictions prevent the action. 0x36 54 LDAP_LOOP_DETECT: Indicates that the client discovered an alias or referral loop, and is thus unable to complete this request. 55-63 Not used. 0x40 https://www.novell.com/coolsolutions/tip/18470.html The message in the default locale is built with the supplied arguments, which are saved to be used for building messages for other locales. disclaimer The Origin of this information may be internal or external to Novell. ENCODING_ERROR = 83 See Also:Constant Field Values DECODING_ERROR public static final int DECODING_ERROR Indicates that the LDAP client encountered errors when decoding an LDAP response from the LDAP server.
The user's e-mail address field may not match the internet addressing domain name (e.g., the user's e-mail address field = [email protected] and the internet domain name = anythingelse.com. this contact form staticint BUSY Indicates that the LDAP server is too busy to process the client request at this time, but if the client waits and resubmits the request, the server may serverMsg - Error message specifying additional information from the server rootException - A throwable which is the underlying cause of the LDAPException. LDAPException public LDAPException(java.lang.StringmessageOrKey, java.lang.Objectarguments, intresultCode, java.lang.StringserverMsg, java.lang.ThrowablerootException) Constructs an fix Administrator should check the billxpert.conf file to ensure that the server name and port number are correct.
Parameters:code - The result code for which a message is to be returned. Error code = [@[email protected]] Error Message = [@[email protected]] Detail Message = [@[email protected]]. LDAP Error 34 - Invalid DN syntax Cause/Fix: This error occurs when you use the LDAP User Name Option, and the User Name has been entered with an invalid Syntax. have a peek here The default hop limit is ten.
For example, if an LDAP add operation fails because of a duplicate entry, the server returns a result code. You may need use use Forward PARTITION_ALREADY_EXISTS -679 References. staticint AUTH_METHOD_NOT_SUPPORTED Indicates that during a bind operation the client requested an authentication method not supported by the LDAP server.
serverMsg - Error message specifying additional information from the server resultCode - The result code returned. LDAPException public LDAPException(java.lang.StringmessageOrKey, intresultCode, java.lang.StringserverMsg, java.lang.ThrowablerootException) Constructs an exception with a detailed message obtained from Indicates that the results of a compare operation are false. This error is returned for the following reasons: The add entry request violates the server's structure rules. staticint INVALID_RESPONSE Indicates that the server response to a request is invalid.
ldap-user-name and ldap-user-pwd should match the directory server's root DN and password. Methods inherited from class java.lang.Throwable fillInStackTrace, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace Methods inherited from class java.lang.Object clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait Field Detail For example, either of the following cause this error: The client returns simple credentials when strong credentials are required. Check This Out ALIAS_PROBLEM = 33 See Also:Constant Field Values INVALID_DN_SYNTAX public static final int INVALID_DN_SYNTAX Indicates that the syntax of the DN is incorrect.
For example, suppose the following conditions: Suppose the hop limit is two. java.lang.String getMessage() int getResultCode() Returns the result code from the exception. Otherwise, a local error code is returned. staticjava.lang.String resultCodeToString(intcode, java.util.Localelocale) Returns a string representing the specified error code in the specified locale.
Returns:The message for the result code in the LDAPException object. It does not indicate that the client has sent an erroneous message. Table 2-2 LDAP Server Return Codes Hex Decimal Constant: Description 0x00 0 LDAP_SUCCESS: Indicates the requested client operation completed successfully. 0x01 1 LDAP_OPERATIONS_ERROR: Indicates an internal error. The RDN for the entry uses a forbidden attribute type.
This code is not currently in the LDAP specifications, but is reserved for this constant. java.lang.String resultCodeToString() Returns a string representing the result code in the default locale. The add or modify operation tries to add an entry with a value for an attribute which the class definition does not contain. resultCodeToString public static java.lang.String resultCodeToString(intcode, java.util.Localelocale) Returns a string representing the specified error code in the specified locale.
The modify attribute request specifies attributes that users cannot modify. fix Use the console to check if the entry's ACI is set correctly. It could earn you a nano! cause 1.
If you do not use the LDAP Username then NDS 8 is sufficient.