-666 FFFFFD66   INCOMPATIBLE NDS VERSION

Source:  eDirectory or NDS

Explanation:  The version of eDirectory or NDS (ds.nlm) on the target server is incompatible with the version on the source server or is on the restricted version list of the source server.

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:  If this error occurs during communication with the server, the version on the target server is incompatible with the version on the source server or is on the restricted version list of the source server.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  If this error occurs during an eDirectory or NDS background process, the version on the target server is incompatible with the version on the source server or is on the restricted version list of the source server.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  The version of eDirectory or NDS (ds.nlm) running on the source server is v5.01 or later, and an attempt was made to add a replica to an eDirectory or NDS server running ds.nlm v3.50 or earlier.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  The version of eDirectory or NDS (ds.nlm) running on the source server is v5.01 or later, and an attempt was made to assign the master replica to an eDirectory or NDS server running ds.nlm v4.40 or earlier when the master is currently held by an eDirectory or NDS server is running ds.nlm v4.63 or later.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  The version of eDirectory or NDS (ds.nlm) running on the source server is v5.01 or later, and an attempt was made to perform a Move Subtree eDirectory or NDS partition operation when one of the servers involved is running ds.nlm v4.62 or earlier.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  The version of eDirectory or NDS (ds.nlm) running on the source server is v5.01 or later, and the eDirectory or NDS server that holds the master replica of the eDirectory or NDS partition that will become the new parent partition reports that one of the servers involved is running ds.nlm v4.62 or earlier.

Action:  Upgrade the server to a compatible version of eDirectory or NDS.

Possible Cause:  This error could occur if

Action:  If the server holding the master replica is a NetWare 4.1 (or later version) server, most partition operations that involve updating replicas on NetWare 4.0x servers cannot be completed.

To be able to complete the partition operations, upgrade the NetWare 4.0x servers in the replica list to NetWare 4.1 (or later versions).

NOTE:  If the master replica is on a NetWare 4.02 server, you will not have this problem.

If this error is seen in DSREPAIR during a remote to local ID check, perform the set DSTRACE=!v command on the NetWare 4.1 (or later version) server. This resets a list that is maintained for restricting use of certain versions of eDirectory or NDS.

Make sure the Set NDS Synchronization Restrictions parameter is used correctly. See the online help for this parameter.

Possible Cause:  If encrypted replication is enabled at a partition level and you are trying to add a replica of this partition to an eDirectory server, the eDirectory version on this server is incompatible with the version on the source server.

Action:  Upgrade the server to a compatible version of eDirectory.

Possible Cause:  If the source server has the replica containing encrypted attributes configured to be accessed only over a secure channel and you are trying to add this replica to a target eDirectory server, the eDirectory version on the target server is not compatible with the version on the source server.

Action:  Upgrade the target server to a compatible version of eDirectory or change the encrypted attributes policy in the source server to allow access through insecure channels.