Novell Ldap Error Codes
Contents |
Favorite Rating: List of LDAP Error Codes (Last modified: 11Feb2003) This document (10018955) is provided subject to the disclaimer at the end of ldap error 13 confidentiality required this document. goal List of LDAP Error Codes fact NLDAP Version 3.0
Leave Federation Cleanup Failed. Error[13] - Confidentiality Required
These messages can be displayed for both the administrator and the end user. Log files containing information for recovering ldap_bind confidentiality required (13) from the error are identified in the fix where applicable. The administrator may also find information in some of the system trace files. This solution was written to provide the error code, ldap error 53 symptom, cause, and solution for each of the error codes. LDAP_000001 symptom LDAP Failed. Error code = [@LDAP_ERR_CODE@] Error Message = [@LDAP_ERR_MSG@] Detail Message = [@LDAP_DETAIL_ERR@]. cause LDAP server error. fix Administrator should check the kjs* file in the $NAS_HOME/logs directory.) fact LDAP_000002 symptom LDAP bind failed. Can't reuse connection. cause LDAP connection failure. fix Administrator should check the billxpert.conf file to ensure that the server name and port number are correct. fact LDAP_000003 symptom The specified user does not exist. cause Mismatched root DN and password in the billxpert.conf file. fix Use the console to check the ldap_section in the billxpert.conf file. ldap-user-name and ldap-user-pwd should match the directory server's root DN and password. fact LDAP_000004 symptom Invalid password. cause User entered an invalid password. fix Re-enter the password. fact LDAP_000005 symptom The session handle is invalid. cause Internal error. fix Restart the LDAP server and NAS. fact LDAP_000006 symptom The entry you want to add already exists. cause Duplicate entry has been inserted into the database. fix Assign a different name to the entry you want to create. fact LDAP_000007 symptom The distinguished name is invalid. cause Wrong LDAP DN syntax. fix Check the DN to ensure that the syntax is correct. fact LDAP_000008 symptom The specified entry does not exist. cause System could not find the entry in the database. fix Use the console to check if the entry is in the directory server. fact LDAP_000009 symptom Entry served by a different LDAP server. cause Entries
Asset Management ZENworks Configuration Management ZENworks Endpoint Security Management ZENworks Full Disk Encryption ZENworks Patch Management ZENworks Virtual Appliance Learn more about ZENworks File & Networking Services + File Management Suite Business Continuity Clustering Dynamic File Services File Reporter Filr Micro Focus iPrint Open Enterprise Server Storage Manager Looking for Linux? See our new home at SUSE.com Services & Support + Services Overview Help Yourself Knowledgebase Support Forums Documentation Product http://www.novell.com/support/kb/doc.php?id=10018955 Support Lifecycle Let Us Help Open Service Request Entitlement & Access Premium Support Technical Support Handbook Download Patches Drivers Contribute Participate in Beta Report Bug Report Software Vulnerability Share a Tip, Trick, etc. Cool Solutions Consulting Customer Center My Profile My Products My Support My Training Partners Communities + Communities Blog—Expert Views Blog—Technical Free Tools Support Forums https://www.novell.com/coolsolutions/tip/6032.html About Us + About Us Contact Us Our Customers Executive Management Job Search Events Media Gallery Industry Analysts Press Releases Subscribe How to Buy + How to Buy Overview Request a Call Find a Partner Shop for Training Volume Licensing & Buying Programs > cool solutions home Troubleshooting Common LDAP Errors Novell Cool Solutions: Tip Digg This - Slashdot This Posted: 1 Dec 2004 Here are some common LDAP Errors reported by the GroupWise POA, along with recommended solutions. See also TID 10067376. LDAP Error 4 - Size limit exceeded Cause/Fix: The POA is pointing to an LDAP server in a different Tree or directory than the one where GroupWise is installed. In this situation, the POA must know the full distinguished name of the user in the LDAP directory it is querying. If the GroupWise user object does not have this value defined in the user properties, then the POA will do an LDAP lookup on the user's e-mail address. This error is caused by the LDAP server returning two e
Favorite Rating: NMAS error codesThis document (3987489) is provided subject to the disclaimer https://www.novell.com/support/kb/doc.php?id=3987489 at the end of this document. Situation NMAS error codes Resolution Decimal ValueHexadecimal ValueNameDescription-0NMAS_SUCCESSThe requested function completed successfully.-16310xFFFFF9A1NMAS_E_FRAG_FAILUREIndicates that the NMASTM NCPTM handler failed.-16320xFFFFF9A0NMAS_E_BAD_REQUEST_SYNTAXIndicates that the NMAS NCP handler failed.-16330xFFFFF99FNMAS_E_BUFFER_OVERFLOWBuffer passed to MAF_GetAttribute is not large enough to store the requested data.-16340xFFFFF99ENMAS_E_SYSTEM_RESOURCESMessage returned when NMAS server fails to obtain information from NICI about ldap error encryption keys.-16350xFFFFF99DNMAS_E_INSUFFICIENT_MEMORYThe NMAS server failed to allocate memory for some system use.-16360xFFFFF99CNMAS_E_NOT_SUPPORTEDIndicates that the login request operation is not supported by the current configuration of NMAS. The error might be returned if the NMAS Client and the NMAS Server versions are not the same. It also might be returned if a login method that novell ldap error does not support the disconnected login is invoked when in the disconnected mode.-16370xFFFFF99BNMAS_E_BUFFER_UNDERFLOWThe packet size specified in the NMAS packet is larger than the actual size of the packet.-16380xFFFFF99ANMAS_E_NOT_FOUNDThis error might be returned if an object does not exist for the requested username and context.-16390xFFFFF999NMAS_E_INVALID_OPERATIONIndicates that an NMAS internal error has occurred, caused by the NMAS protocol getting out of order.-16400xFFFFF998NMAS_E_ASN1_DECODEFailed to decode NMAS internal structures in a signed module.-16410xFFFFF997NMAS_E_ASN1_ENCODEFailed to encode NMAS internal structures.-16420xFFFFF996NMAS_E_LOGIN_FAILEDIndicates that the secret (for example password) presented by the user is invalid.-16430xFFFFF995NMAS_E_INVALID_PARAMETERAn invalid parameter was passed to the NMAS function.-16440xFFFFF994NMAS_E_TIMED_OUT_RECOVERABLEThe Client or the server failed to respond in a timely manner. The calling software has the option to retry the request if this error occurs.-16450xFFFFF993NMAS_E_TIMED_OUT_NOT_RECOVERABLEThe Client or the server failed to respond in a timely manner. The calling software does not have the option to retry the request if this error occurs.-16460xFFFFF992NMAS_E_TIMED_OUT_UNKNOWNThe Client or the server failed to respond in a timely ma
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 22 Oct 2016 00:36:34 GMT by s_wx1126 (squid/3.5.20)