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 attr

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

The server specified for this replication operation was contacted, but that server was unable to contact an ad

The version of the directory service schema of the source forest is not compatible with the version of directo

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 dest

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

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

Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Eith

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

Object being moved across-domains is already known to be deleted by the destination server. The source server

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

This object may not be moved across domain boundaries either because cross-domain moves for this class are dis

Can't move objects with memberships across domain boundaries as once moved, this would violate the membership

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 namin

Destination domain must be in native mode.

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

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

Tree deletions starting at an object which has an NC head as a descendant are not allowed.

The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.

The directory service failed to identify the list of objects to delete while attempting a tree deletion.

Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please

Only an administrator can modify the membership list of an administrative group.

Cannot change the primary group ID of a domain controller account.

An attempt is made to modify the base schema.

Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class,

Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.

An object of this class cannot be created under the schema container. You can only create attribute-schema and