Error code search

The replication operation was preempted.

The replication synchronization attempt was abandoned because of a lack of updates.

The replication operation was terminated because the system is shutting down.

Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.

The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.

The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.

The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.

Schema update failed: An attribute with the same link identifier already exists.

Name translation: Generic processing error.

Name translation: Could not find the name or insufficient right to see name.

Name translation: Input name mapped to more than one output name.

Name translation: Input name found, but not the associated output format.

Name translation: Unable to resolve completely, only the domain was found.

Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.

Modification of a constructed attribute is not allowed.

The OM-Object-Class specified is incorrect for an attribute with the specified syntax.

The replication request has been posted; waiting for reply.

The requested operation requires a directory service, and none was available.

The LDAP display name of the class or attribute contains non-ASCII characters.

The requested search operation is only supported for base searches.

The search failed to retrieve attributes from the database.

The schema update operation tried to add a backward link attribute that has no corresponding forward link.

Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.

Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.

Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.

Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.

Destination of a cross-domain move is not authoritative for the destination naming context.

Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.

Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.

Another operation which requires exclusive access to the PDC FSMO is already in progress.

A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.

This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move.

Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.

A naming context head must be the immediate child of another naming context head, not of an interior node.

The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters.)

Destination domain must be in native mode.

The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.

Cross-domain move of non-empty account groups is not allowed.

Cross-domain move of non-empty resource groups is not allowed.

The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.