Adprep was unable to extend the schema. [Status/Consequence] There is a schema conflict with Exchange 2000. The schema is not upgraded. [User Action] The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and then run Adprep. For information on resolving the conflict, see Microsoft Knowledge Base article Q325379.
Adprep was unable to create the log file %1. Status/Consequence Adprep has stopped without making changes. Adprep uses the ...
Adprep was unable to create the object %1 in Active Directory. Status/Consequence This Adprep operation failed. User Action ...
Adprep was unable to determine whether Microsoft Windows Services for UNIX (SFU) is installed in this forest or not. Status ...
Adprep was unable to extend the schema. Status/Consequence The schema master did not complete a replication cycle after the ...
Adprep was unable to extend the schema. Status/Consequence There is a schema conflict with Exchange 2000. The schema is not ...
Adprep was unable to initialize global variables. Status/Consequence Usually this means system resources are unavailable. ...
Adprep was unable to make an LDAP connection to the domain controller %1. Status/Consequence Adprep requires connectivity ...
Adprep was unable to modify some attributes on object %1. User Action Check the log file Adprep.log in the system root System32\Debug\Adprep\Logs ...
ADPREP was unable to modify the default security descriptor on object %1. Status/Consequence Adprep attempts to merge the ...