Chapter 5. eDirectory/NDS Error Codes Explained DS errors occur during the processing of a directory services (DS) request or the execution of a DS background process. These errors can happen as a result of a hardware or software failure, data inconsistency, or unexpected responses received; therefore, when you're troubleshooting a problem, it is essential that you know where the error originated, the condition that caused the error, and what the error code or message means. Unfortunately, computer-generated error messages are notoriously cryptic at best and frequently don't easily provide the source of the error. For example, a DS error can be generated from one of three possible sources: -
The DS service running on the server -
The client application (workstation based or server based) -
The DS agent (DSA) running on the server. It gets even more frustrating if multiple causes can result in the same error code. NOTE Each DS -capable server runs both DS service (which processes DS requests locally) and the DSA service. The DSA tree-walks and queries other DS servers on behalf of the requesting client ”which can be either a workstation or another server ”if the local server doesn't have the requested information.
By examining the code number returned or associated with an error message, you can determine the most likely source (the server, the client, or the DSA) and the possible cause of the DS error. Keep in mind that the information provided here does not necessarily give remedies; this chapter provides developers' explanations of the errors. Several factors can help you to identify the root cause of an error and then eliminate or correct the error, including the following: -
An understanding of DS processes (see Chapter 6, "Understanding Common eDirectory Processes") -
An understanding of DS error code definitions and possible conditions under which they can occur (see Appendix A, "eDirectory Error Codes") -
Familiarity with the DS tree that is experiencing the error -
Familiarity with the placement of the replicas -
Familiarity with various DS diagnostic and repair tools, such as DSTrace, DSBrowse, DSRepair, and the eDirectory Maintenance Tool Box (eMBox) included with eDirectory 8.7 and higher (see Chapter 7, "Diagnostic and Repair Tools"). This chapter provides information to help you understand the most commonly encountered DS error codes. You can use this as a starting point to further determine the actual cause of a problem and then formulate a corrective action plan. An exhaustive list and explanation of all the published DS error codes is presented in Appendix A. REAL WORLD: Lightweight Directory Accoess Protocol (LDAP) You can access an NDS /eDirectory tree by using Lightweight Directory Access Protocol ( LDAP ). Because LDAP is an Internet standard, the error codes returned by the LDAP client and server applications are not those used by NDS or eDirectory, but they are a set of standardized values. Error codes from an LDAP server ranges from 0 (0x00) through 80 (0x50), and LDAP clients may return error codes between 81 (0x51) and 137 (0x89). Sometimes a Novell-supplied LDAP application shows an LDAP error as well as a DS error code, if appropriate. For instance, if an object is not found, the application may report an LDAP error of 32 (0x20), meaning the target object cannot be found, and also the DS error code -601. You can find a list of LDAP error codes in Novell TID #10018955 and on the Internet. The following are some useful URLs: http://nimbus.ocis.temple.edu/ldap/error.htm#1915315 http://help.netscape.com/kb/corporate/19970303-9.html www.opus1.com/www/iii/SDK/errors.html
|
|
