-699 FFFFFD45   FATAL

Source:  eDirectory or NDS

Explanation:  An unrecoverable error has occurred and the operation cannot be completed.

WARNING:  Applying all solutions mentioned in this topic could make the problem worse if the actual cause of the problem is not known. Before following a course of action, make sure that you understand the cause of the error and the consequences for the actions suggested.

Possible Cause:  Sometimes this error can occur during the normal operation of eDirectory or NDS (ds.nlm).

Action:  These errors are handled during the normal operation of eDirectory or NDS and are considered transitory errors.

Possible Cause:  This error could occur during the background process of eDirectory or NDS Schema Synchronization in response to the request to start schema synchronization. If it does, the source and target server are the same server or the target server is the special identity "Public."

When using DSTRACE on the source server with the Schema flag set, the following message will be displayed:

WARNING! rejecting DSStartUpdateSchema client <TargetServerName>

Action:  Use DSREPAIR to run a local database repair.

Possible Cause:  An internal or unexpected error occurred in eDirectory or NDS (ds.nlm).

Action:  Contact a Novell Support Provider.

Possible Cause:  This error could occur during the background process for eDirectory or NDS Replica Synchronization in response to the request to start replica synchronization. If it does, the source and the target server could be the same server. If this is the case, duplicate replica attribute values could exist in the replica ring for the partition root object.

Action:  Use DSREPAIR to run a local database repair.

Possible Cause:  This error could occur during the background process for eDirectory or NDS Replica Synchronization in response to an update request. Check to see if DSTRACE is displaying the following message on the target server while the Schema Synchronization flag is set:

SKULKER: invalid replica root

If that message is displayed, this can indicate the following about the specified root partition object:

Action:  Run a local database repair using DSREPAIR.

Possible Cause:  If this error occurs during the background process for eDirectory or NDS Replica Synchronization in response to an update request, it can indicate that the source and target server are the same server. Occurrences in this case can indicate that there are duplicate replica attribute values in the replica ring for the partition root object.

Action:  Use DSREPAIR to run a local database repair.

Possible Cause:  If this error occurs during the eDirectory or NDS Janitor background process, while processing the eDirectory or NDS object obituaries, it can indicate the following:

Action:  Contact a Novell Support Provider.

Possible Cause:  This error could occur during the eDirectory or NDS partition operation Move Subtree. If it does, the server that holds the master replica of the parent partition of the partition being moved was not found in the replica ring of the master replica.

If DSTRACE is being used on the eDirectory or NDS server that holds the master replica of the partition being moved, the following message will be displayed:

CNTL: Partition <SourcePartitionRoot> entry not found on server <SourcePartitionRootParent'sMasterReplicaServerName>

Action:  A server that holds a nonsubordinate reference replica of an eDirectory or NDS partition must have a subordinate reference replica of each of the child partitions. Handle this condition as a Replica Ring Discrepancy.

Possible Cause:  This error could occur during the eDirectory or NDS Janitor background process, while purging the local eDirectory or NDS database and after successfully completing the eDirectory or NDS Replica Synchronization background process. If it does, an attempt was made to purge an invalid entry record.

Action:  If this error occurs continuously in the circumstances described, use DSREPAIR to run a local database repair.

Possible Cause:  This error could occur during the eDirectory or NDS Limber background process. If it does, the server could have been out of available memory when the Limber process was attempting to update the referral information of the source server on the master replica of each of the partitions held by the source server.

Action:  Reinitialize eDirectory or NDS. Monitor eDirectory or NDS using set DSTRACE=*.

Possible Cause:  This error could occur when eDirectory or NDS is attempting to initiate an eDirectory or NDS partition merge operation. In this case, you would see this error as a response from the server holding the master replica of the parent partition of the partition being merged. If it does occur, the child partition root object on the server holding the master replica of the parent partition is not a partition root object.

Action:  Verify the replica ring consistency and the parent/child relationships of the partitions.

Possible Cause:  If this error occurs under the following conditions, then the source server has not received a readable replica, or better, of the parent partition.

Action:  Check the replica ring consistency and fix the discrepancy.

Possible Cause:  If this error occurs under the following conditions, then an unspecified error occurred during the initialization routines:

Unable to initialize schema cache. opSchema is now invalid.

Action:  Use DSREPAIR with the Rebuild Operational Schema option selected to run a local database repair.

Possible Cause:  Packet corruption is occurring, or an eDirectory or NDS server or client made an attempt to use an unknown packet format. This might be caused by faulty LAN drivers, LAN cards, or other LAN/WAN equipment existing between the source and target servers.

Action:  Make sure that any LAN/WAN equipment, cards, and drivers that exist between the source and target server are functioning properly.

Possible Cause:  An attempt was made to open the local database while it was already open.

Action:  Contact the developer of the application that issued the request.

Possible Cause:  An attempt was made during the eDirectory or NDS Merge Tree operation to assign a replica of the [Root] partition using replica number zero.

Action:  Use DSREPAIR to run a local database repair on the server with the master of [Root].

Possible Cause:  An attempt was made to request a subordinate reference replica without being able to identify the server holding the master replica of the eDirectory or NDS partition being requested.

The request to receive a subordinate reference replica can occur while processing a dying replica if the replica's parent partition exists on the server holding the dying replica or while receiving a replica if the new replica has child partitions.

When DSTRACE is being used on the source server with the Schema Synchronization flag set, the following message will be displayed:

SYNC: ProcessDyingReplica - <PartitionRootObjectName>. Master not found in local ring.

Action:  Ensure that a master replica of the partition exists and that the servers are communicating.

Possible Cause:  An attempt was made to assign a new master replica using the eDirectory or NDS Change Replica Type operation under the following conditions:

Action:  Verify the consistency of the replica rings. Make sure that the server with the master of the partition exists.

Possible Cause:  A request was received to synchronize an eDirectory or NDS partition under the following conditions:

Action:  Verify the consistency of the replica rings.

Possible Cause:  A request was received to begin processing the eDirectory or NDS partition operation Move Subtree, and the source server was unable to locate the master replica in the replica ring for the specified eDirectory or NDS partition.

When DSTRACE is being used with the Schema Synchronization or the Partition Operation flags set, the following message will be displayed:

MoveTree: End Notify for [PartitionRootObjectEntryID] <PartitionRootObjectName> failed, error - 699

Action:  Verify that a master replica exists.

Possible Cause:  A request was received to register a NLM program for an eDirectory or NDS event where the requester specified an invalid priority.

Action:  Contact the developer of the application.

Possible Cause:  If this error occurs during the initialization of eDirectory or NDS (ds.nlm), an internal problem with the DSLoader could exist.

Action:  Reload eDirectory or NDS (ds.nlm).

Possible Cause:  If this error occurs during the initialization of eDirectory or NDS (ds.nlm), the ds.nlm could be corrupted.

Action:  Replace ds.nlm with a new copy and reload eDirectory or NDS.

Possible Cause:  If this error occurs continuously during the initialization of eDirectory or NDS (ds.nlm), and the ds.nlm and DSLoader files have been replaced, an internal error could have occurred in these files.

Action:  Contact a Novell Support Provider.