Active Directory has detected that the replication epoch (as indicated by the msDS-ReplicationEpoch attribute of the following object) of the local domain controller has been changed. This typically occurs as part of the domain rename process. Object: %1 Old replication epoch: %2 New replication epoch: %3 As a result, replication between this domain controller and domain controllers that are using the old replication epoch is no longer allowed. Replication can occur only with those domain controllers using the new replication epoch.
Active Directory has completed the verification of lingering objects on the local domain controller in advisory mode. All ...
Active directory has detected a missing parent or a loop in parent chain for the following object. The object has been moved. ...
Active Directory has detected and deleted some possibly corrupted indices as part of initialization. These deleted indices ...
Active Directory has detected that the quota-tracking table is either missing or not completely built. The table will be ...
Active Directory has detected that the replication epoch (as indicated by the msDS-ReplicationEpoch attribute of the following ...
Active Directory has encountered a temporary cache inconsistency. Therefore, the application directory partition was not ...
Active Directory has failed to upgrade a critical index as part of initialization. Please contact Microsoft Product Support ...
Active Directory has identified the following lingering object on the local domain controller in advisory mode. The object ...
Active Directory has raised the domain functional level for this domain to be compatible with the current forest functional ...