It has a different parent object on the target server than the parent object on the source server.-699 FFFFFD45 FATAL
Source
NDS® or Novell® eDirectoryTM
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 NDS or eDirectory (DS.NLM).
Action
These errors are handled during the normal operation of NDS or eDirectory and are considered transitory errors.
Possible Cause
This error could occur during the background process of NDS or eDirectory 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 NDS or eDirectory (DS.NLM).
Action
Contact a Novell support provider.
Possible Cause
This error could occur during the background process for NDS or eDirectory 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 NDS or eDirectory 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:
It has a different parent object on the target server than the parent object on the source server.
It is an external reference on the target server.
Action
Run a local database repair using DSREPAIR.
Possible Cause
If this error occurs during the background process for NDS or eDirectory 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 NDS or eDirectory Janitor background process, while processing the NDS or eDirectory object obituaries, it can indicate the following:
An attempt was made to process an unidentified type 1 obituary. Standard type obituaries are Restored (0), Dead, Moved, New RDN.
The obituary received by the target server was a type 1 (Dead) obituary and specified a zero creation timestamp for the targeted NDS or eDirectory object.
If using DSTRACE on the target server with the Backlinker flag set, the following message will be displayed:
*Backlink: END DSASyncExternalReference request from [SourceServerEntryID] <SourceServerName> failed, error -699
Action
Contact a Novell support provider.
Possible Cause
This error could occur during the NDS or eDirectory 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 NDS or eDirectory 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 NDS or eDirectory 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 NDS or eDirectory Janitor background process, while purging the local NDS or eDirectory database and after successfully completing the NDS or eDirectory 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 NDS or eDirectory 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 NDS or eDirectory. Monitor NDS or eDirectory using SET DSTRACE=*.
Possible Cause
This error could occur when NDS or eDirectory is attempting to initiate an NDS or eDirectory 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.
The NDS or eDirectory partition merge operation is in preparation to advance the replica state to Join State 1.
DSTRACE is being used on the source server with the Synchronization or the Partition Operation flags set.
The message displayed is "JOINING UP: <ChildPartition> Child's ring did not match parent's. Wait for parent replica."
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:
An attempt was made to initialize the NDS or eDirectory schema cache.
DSTRACE is being used on the source server with the Schema Synchronization flag set and the following message is displayed:
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 NDS or eDirectory 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 NDS or eDirectory 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 NDS or eDirectory 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 NDS or eDirectory Change Replica Type operation under the following conditions:
The source server does not hold a replica of the specified NDS or eDirectory partition.
The source server does not have a replica attribute value in its copy of the replica ring for the specified NDS or eDirectory partition that identifies the NDS or eDirectory server holding the master replica.
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 NDS or eDirectory partition under the following conditions:
The partition does not exist on the source server.
The partition came from an NDS or eDirectory server that does not exist in the replica ring on the source server for the specified NDS or eDirectory partition.
Action
Verify the consistency of the replica rings.
Possible Cause
A request was received to begin processing the NDS or eDirectory partition operation Move Subtree, and the source server was unable to locate the master replica in the replica ring for the specified NDS or eDirectory 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 NetWare® Loadable ModuleTM (NLMTM) program for an NDS or eDirectory 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 NDS or eDirectory (DS.NLM), an internal problem with the DSLoader could exist.
Action
Reload NDS or eDirectory (DS.NLM).
Possible Cause
If this error occurs during the initialization of NDS or eDirectory (DS.NLM), the DS.NLM could be corrupted.
Action
Replace DS.NLM with a new copy and reload NDS or eDirectory.
Possible Cause
If this error occurs continuously during the initialization of NDS or eDirectory (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.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.