DSA Error Codes

     

Error codes -601 through -799 and -6001 through -6999 are errors returned by the DSA that is running on the DS server. The DSA errors are what you generally see in the DSTrace screen and reported by various DS utilities, such as NetWare Administrator and ConsoleOne; therefore, you should be well versed in these error codes.

Table 5.4 shows some of the common error codes returned by the DSA. You can find a complete list of all the DSA error codes in Appendix A.

Table 5.4. Common DSA Error Codes

DECIMAL	HEXADECIMAL	CONSTANT
-601	0xFFFFFDA7	ERR_NO_SUCH_ENTRY
-602	0xFFFFFDA6	ERR_NO_SUCH_VALUE
-603	0xFFFFFDA5	ERR_NO_SUCH_ATTRIBUTE
-624	0xFFFFFD90	ERR_REPLICA_ALREADY_EXISTS
-625	0xFFFFFD8F	ERR_TRANSPORT_FAILURE
-626	0xFFFFFD8E	ERR_ALL_REFERRALS_FAILED
-654	0xFFFFFD72	ERR_PARTITION_BUSY
-659	0xFFFFFD6D	ERR_TIME_NOT_SYNCHRONIZED
-666	0xFFFFFD66	ERR_INCOMPATIBLE_DS_VERSION
-672	0xFFFFFD60	ERR_NO_ACCESS
-698	0xFFFFFD46	ERR_REPLICA_IN_SKULK
-715	0xFFFFFD35	ERR_CHECKSUM_FAILURE
-782	0xFFFFFCF2	ERR_ROOT_UNREACHABLE
-785	0xFFFFFCEF	ERR_DIB_ERROR
-6018	0xFFFFE87E	ERR_SERIAL_NUM_MISMATCH
-6024	0xFFFFE878	ERR_RFL_FILE_NOT_FOUND

The -601 error is perhaps the most common DS error code that you will encounter. This error refers to the fact that the specified object is not found on the server replying to the request. The specified object context could be wrong, or the client might not have sufficient DS rights (such as Browse) to the object. If you see this error code in a DSTrace screen, it simply means the server handling the request doesn't have the information and will have to perform a tree-walk; therefore, in most cases, a -601 error is an informational error.

Errors -602 and -603 mean the requested attribute value and attribute, respectively, are not found on the server replying to the request. The client may not have sufficient DS rights to the data. Unlike with the -601 error, however, with -602 and -603, no tree-walking will be performed to look for the information elsewhere.

Next to the -601 error, -625 is probably the second most commonly reported DSA error. Error -625 means the reporting server is unable to communicate with the target server. This is generally a result of the target server being down, a LAN/WAN outage , or some sort of routing problem.

The -698 error code is another nonfatal error. It means an attempt was made to start the NDS replica synchronization process with a target server, but the target server was busy synchronizing with another server. This is a transitory error, and the NDS replica synchronization process will reschedule. You are likely to see this error on partitions that have a large replica ring (say, 10 or more servers) or have slow or busy servers in the replica ring.

NOTE

To prevent data conflicts, a DS server will only receive inbound DS replica synchronization traffic from other servers, in the replica ring, one at a time. When two servers in the same replica ring try to synchronize to the same DS server before one of them completes the synchronization, the second server reports error “698 and retries at a later time.

A routing problem could result in a misleading -715 error code, which means the NDS checksum in the request packet is invalid. We have encountered one instance where a duplicate IPX network address on the network caused DS to erroneously report a -715 error. After removing the duplicate route, DS resolved the -715 error without further intervention, such as the need to run DSRepair.

If you don't have sufficient privileges to modify an object's attribute values, error -672 occurs. Similarly, when a server-based application authenticates to only the local server and not the DS tree, the application also results in a -672 error if the object it tries to modify does not exist in a replica held on that server. Incidentally, performing a send all operation by using eMBox may also result in a -672 error, although it works fine if you use the DSRepair module instead. In this situation, the error is due to the fact that eMBox does not have all the necessary information to perform the task. You must enter two data fields when you send all objects to every replica in the ring by using eMBox:

1. You must select the partition you want to perform the send all operation on. Make sure the radio button is not selected for the partition ID but is on the partition DN.

2. You must select the server object you want to send from (using the Server DN option). It must be a server that holds at least a read/write replica of the partition in question.

If you do not enter the correct information (as illustrated in Figure 5.2) into either of these two fields, you will most likely get a -672 error as a result.

Figure 5.2. Using eMBox to perform a send all operation.

WARNING

Remember that there is no way to do a send all to just one specific server in the replica ring. A send all will send all objects to all other servers in the replica ring. Therefore, with a large replica ring, it could take some time to complete, and a large volume of DS traffic could be generated.

Many of the -6001 through -6999 series of error codes were introduced for eDirectory 8.7 and higher. These error codes are mostly related to the operation of eDirectory Backup eMTool (called eMTool for short) and the roll-forward log (RFL) files. For instance, if RFL files from another server were used when restoring the eDirectory database via eMTool, error -6018 will be reported. If one or more of the required RFL files required for an eDirectory database restoration is missing, eMTool will report a -6024 error.

TIP

There is an interesting bug in the eMBox version 10410.68 (shipped with eDirectory 8.7.1) that occurs when you set the RFL directory name. If the name of the RFL directory is longer than eight characters , the eMBox client reports a “785 error, saying that it was unable to update the backup configuration information. This is misleading because -785 means an internal Directory Information Base error, but there isn't one. The error is due to that the fact that although the eMBox client supports long directory names , the FLAIM engine is rejecting the long name (for some unknown reason). Therefore, the workaround is to use a directory name that is eight or fewer characters.

Also be aware that if the specified directory does not already exist, eMBox will return a -25 error, indicating an invalid directory.