| 1 | DS Role Server |
DS Role Server |
| 2 | This service hosts the DS Role Server used for DC promotion, demotion, and cloning. If this service is disabled, these operations will fail. |
This service hosts the DS Role Server used for DC promotion, demotion, and cloning. If this service is disabled, these operations will fail. |
| 0x00007000 | Searching for a domain controller for the domain %1 |
Searching for a domain controller for the domain %1 |
| 0x00007001 | Located domain controller %1 for domain %2 |
Located domain controller %1 for domain %2 |
| 0x00007002 | Using site %1 for server %2 |
Using site %1 for server %2 |
| 0x00007003 | Stopping service %1 |
Stopping service %1 |
| 0x00007004 | Configuring service %1 |
Configuring service %1 |
| 0x00007005 | Starting service %1 |
Starting service %1 |
| 0x00007006 | Installing the Directory Service |
Installing the Directory Service |
| 0x00007008 | Setting the LSA policy information |
Setting the LSA policy information |
| 0x00007009 | Setting the LSA policy information from policy %1 |
Setting the LSA policy information from policy %1 |
| 0x00007010 | Creating a trust relationship with domain %1 |
Creating a trust relationship with domain %1 |
| 0x00007013 | Creating the System Volume %1 |
Creating the System Volume %1 |
| 0x00007015 | Deleting the trust relationship with the domain %1 |
Deleting the trust relationship with the domain %1 |
| 0x00007017 | Configuring the server account |
Configuring the server account |
| 0x00007018 | The attempted domain controller operation has completed |
The attempted domain controller operation has completed |
| 0x00007019 | Creating a parent trust relationship on domain %1 |
Creating a parent trust relationship on domain %1 |
| 0x00007022 | Reading domain policy from the domain controller %1 |
Reading domain policy from the domain controller %1 |
| 0x00007025 | Reading domain policy from the local machine |
Reading domain policy from the local machine |
| 0x00007026 | Preparing the directory service for demotion |
Preparing the directory service for demotion |
| 0x00007027 | Uninstalling the Directory Service |
Uninstalling the Directory Service |
| 0x00007028 | Preparing for system volume replication using root %1 |
Preparing for system volume replication using root %1 |
| 0x00007029 | Copying initial Directory Service database file %1 to %2 |
Copying initial Directory Service database file %1 to %2 |
| 0x00007030 | Searching for a domain controller for the domain %1 that contains the account %2 |
Searching for a domain controller for the domain %1 that contains the account %2 |
| 0x00007031 | Setting security on the domain controller and Directory Service files and registry keys |
Setting security on the domain controller and Directory Service files and registry keys |
| 0x00007033 | Forcing a time sync with %1 |
Forcing a time sync with %1 |
| 0x00007034 | Saving the SAM state for an upgrade |
Saving the SAM state for an upgrade |
| 0x00007035 | Moving the existing logon scripts from %1 to %2 |
Moving the existing logon scripts from %1 to %2 |
| 0x00007036 | Setting the computer's DNS computer name root to %1 |
Setting the computer's DNS computer name root to %1 |
| 0x00007037 | Completed moving the logon scripts |
Completed moving the logon scripts |
| 0x00007039 | Domain Controller Promotion |
Domain Controller Promotion |
| 0x0000703A | Domain Controller Demotion |
Domain Controller Demotion |
| 0x0000703B | DsRole Interface |
DsRole Interface |
| 0x0000703C | Domain Controller cloning is at %1%% completion... |
Domain Controller cloning is at %1%% completion... |
| 0x0000703D | Cloning Domain Controller succeeded. Now rebooting... |
Cloning Domain Controller succeeded. Now rebooting... |
| 0x0000703E | Cloning Domain Controller failed. Now rebooting into DSRM... |
Cloning Domain Controller failed. Now rebooting into DSRM... |
| 0x00007202 | Moving the existing logon scripts from %1 to %2 failed. The return code is the data. |
Moving the existing logon scripts from %1 to %2 failed. The return code is the data. |
| 0x00007203 | Running the Security Configuration Editor over the Domain Controller encountered a non-fatal error. Further details can be obtained by examining the log file %1. The return code is the data. |
Running the Security Configuration Editor over the Domain Controller encountered a non-fatal error. Further details can be obtained by examining the log file %1. The return code is the data. |
| 0x00007204 | An existing, incompatible trust object was found on the parent server for domain %1. It has been removed and replaced with an updated trust. |
An existing, incompatible trust object was found on the parent server for domain %1. It has been removed and replaced with an updated trust. |
| 0x00007220 | Failed to disable auto logon following the successful upgrade of a domain controller. Unable to delete registry key %1. The return code is the data. |
Failed to disable auto logon following the successful upgrade of a domain controller. Unable to delete registry key %1. The return code is the data. |
| 0x00007221 | Failed to set the default logon domain to %1. The return code is the data. |
Failed to set the default logon domain to %1. The return code is the data. |
| 0x00007222 | Virtual domain controller cloning failed. The cloning operation could not be completed and the cloned domain controller was rebooted into Directory Services Restore Mode (DSRM).%n%nPlease check previously logged events and %systemroot%\\debug\\dcpromo.log for more information on errors that correspond to the virtual domain controller cloning attempt and whether or not this clone image can be reused.%n%nIf one or more log entries indicate that the cloning process cannot be retried, the image must be securely destroyed.%n%nOtherwise you may fix the errors, clear the DSRM boot flag, and reboot normally; upon reboot, the cloning operation will be retried.%n%nDetails on virtual domain controller clone errors can be found at http://go.microsoft.com/fwlink/?LinkId=208030. |
Virtual domain controller cloning failed. The cloning operation could not be completed and the cloned domain controller was rebooted into Directory Services Restore Mode (DSRM).%n%nPlease check previously logged events and %systemroot%\\debug\\dcpromo.log for more information on errors that correspond to the virtual domain controller cloning attempt and whether or not this clone image can be reused.%n%nIf one or more log entries indicate that the cloning process cannot be retried, the image must be securely destroyed.%n%nOtherwise you may fix the errors, clear the DSRM boot flag, and reboot normally; upon reboot, the cloning operation will be retried.%n%nDetails on virtual domain controller clone errors can be found at http://go.microsoft.com/fwlink/?LinkId=208030. |
| 0x00007223 | Virtual domain controller cloning succeeded. |
Virtual domain controller cloning succeeded. |
| 0x00007225 | During the demotion operation, the trust object on %1 could not be removed. |
During the demotion operation, the trust object on %1 could not be removed. |
| 0x00007226 | During the demotion operation, the File Replication Service reported a non critical error. |
During the demotion operation, the File Replication Service reported a non critical error. |
| 0x00007227 | This server is now a Domain Controller. |
This server is now a Domain Controller. |
| 0x00007228 | This server is no longer a Domain Controller. |
This server is no longer a Domain Controller. |
| 0x00007237 | This server was force demoted. It is no longer a Domain Controller. |
This server was force demoted. It is no longer a Domain Controller. |
| 0x00007238 | The Netlogon service could not be stopped during force demotion. |
The Netlogon service could not be stopped during force demotion. |
| 0x00007239 | Dcpromo failed to configure the new starttype of %1 for the service %2 during forced demotion. |
Dcpromo failed to configure the new starttype of %1 for the service %2 during forced demotion. |
| 0x0000723A | Dcpromo failed to remove the dependency of %1 on %2 during forced demotion. |
Dcpromo failed to remove the dependency of %1 on %2 during forced demotion. |
| 0x00007240 | Virtual domain controller cloning failed to obtain Winlogon Notification.%nThe returned error code is %1 (%2).%n%nFor more information on this error, please review %systemroot%\\debug\\dcpromo.log for errors that correspond to the virtual domain controller cloning attempt. %n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed to obtain Winlogon Notification.%nThe returned error code is %1 (%2).%n%nFor more information on this error, please review %systemroot%\\debug\\dcpromo.log for errors that correspond to the virtual domain controller cloning attempt. %n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007241 | Virtual domain controller cloning failed to parse virtual domain controller configuration file.%nThe returned HRESULT code is %1.%nThe configuration file is:%n%2%n%nPlease fix the errors in the configuration file and retry the cloning operation. For more information about this error, please see %systemroot%\\debug\\dcpromo.log.%n%nDetails on virtual domain controller clone configuration file can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed to parse virtual domain controller configuration file.%nThe returned HRESULT code is %1.%nThe configuration file is:%n%2%n%nPlease fix the errors in the configuration file and retry the cloning operation. For more information about this error, please see %systemroot%\\debug\\dcpromo.log.%n%nDetails on virtual domain controller clone configuration file can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007242 | Virtual domain controller cloning failed. There are software or services currently enabled on the cloned virtual domain controller that are not present in the allowed application list for virtual domain controller cloning. Following are the missing entries:%n%2%n%1 (if any) was used as the defined inclusion list.%n%nThe cloning operation cannot be completed if there are non-cloneable applications installed.%nPlease run Active Directory Powershell Cmdlet Get-ADDCCloningExcludedApplicationList to check which applications are installed on the cloned machine, but not included in the allow list, and add them to the allow list if they are compatible with virtual domain controller cloning. If any of these applications are not compatible with virtual domain controller cloning, please uninstall them before re-trying the cloning operation.%n%nThe virtual domain controller cloning process searches for the allowed application list file, CustomDCCloneAllowList.xml, based on the following search order; the first file found is used and all others are ignored:%n 1. The registry value name: HKey_Local_Machine\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\AllowListFolder%n 2. The same directory where the DSA Working Directory folder resides%n 3. %windir%\\NTDS%n 4. Removable read/write media in order of drive letter at the root of the drive%n%nDetails on virtual domain controller clone allow list can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed. There are software or services currently enabled on the cloned virtual domain controller that are not present in the allowed application list for virtual domain controller cloning. Following are the missing entries:%n%2%n%1 (if any) was used as the defined inclusion list.%n%nThe cloning operation cannot be completed if there are non-cloneable applications installed.%nPlease run Active Directory Powershell Cmdlet Get-ADDCCloningExcludedApplicationList to check which applications are installed on the cloned machine, but not included in the allow list, and add them to the allow list if they are compatible with virtual domain controller cloning. If any of these applications are not compatible with virtual domain controller cloning, please uninstall them before re-trying the cloning operation.%n%nThe virtual domain controller cloning process searches for the allowed application list file, CustomDCCloneAllowList.xml, based on the following search order; the first file found is used and all others are ignored:%n 1. The registry value name: HKey_Local_Machine\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\AllowListFolder%n 2. The same directory where the DSA Working Directory folder resides%n 3. %windir%\\NTDS%n 4. Removable read/write media in order of drive letter at the root of the drive%n%nDetails on virtual domain controller clone allow list can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007243 | Virtual domain controller cloning failed to reset the IP addresses of the clone machine.%nThe returned error code is %1 (%2).%nThis error might be caused by misconfiguration in network configuration sections in the virtual domain controller configuration file. Please see %systemroot%\\debug\\dcpromo.log for more information about errors that correspond to IP addresses resetting during virtual domain controller cloning attempts.%n%nDetails on resetting machine IP addresses on the cloned machine can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed to reset the IP addresses of the clone machine.%nThe returned error code is %1 (%2).%nThis error might be caused by misconfiguration in network configuration sections in the virtual domain controller configuration file. Please see %systemroot%\\debug\\dcpromo.log for more information about errors that correspond to IP addresses resetting during virtual domain controller cloning attempts.%n%nDetails on resetting machine IP addresses on the cloned machine can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007245 | Virtual domain controller cloning failed. The clone domain controller was unable to locate the primary domain controller (PDC) operations master in the cloned computer's home domain of the cloned machine.%nThe returned error code is %1 (%2).%n Please verify that the primary domain controller in the home domain of the cloned machine is assigned to a live domain controller, is online, and is operational. Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols. %n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed. The clone domain controller was unable to locate the primary domain controller (PDC) operations master in the cloned computer's home domain of the cloned machine.%nThe returned error code is %1 (%2).%n Please verify that the primary domain controller in the home domain of the cloned machine is assigned to a live domain controller, is online, and is operational. Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols. %n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007246 | Virtual domain controller cloning failed to bind to the primary domain controller %1.%nThe returned error code is %2 (%3). %n Please verify that the primary domain controller %1 is online and is operational. Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols.%n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed to bind to the primary domain controller %1.%nThe returned error code is %2 (%3). %n Please verify that the primary domain controller %1 is online and is operational. Verify that the cloned machine has LDAP/RPC connectivity to the primary domain controller over the required ports and protocols.%n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007247 | Virtual domain controller cloning failed. An attempt to create objects on the primary domain controller %1 required for the image being cloned returned error %2 (%3).%nPlease verify that the cloned domain controller has privilege to clone itself. Check for related events in the Directory Service event log on primary domain controller %1.%n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed. An attempt to create objects on the primary domain controller %1 required for the image being cloned returned error %2 (%3).%nPlease verify that the cloned domain controller has privilege to clone itself. Check for related events in the Directory Service event log on primary domain controller %1.%n%nDetails on virtual domain controller cloning can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x00007248 | An attempt to set the Boot into Directory Services Restore Mode flag failed with error code %1.%nPlease see %systemroot%\\debug\\dcpromo.log for more information about errors. |
An attempt to set the Boot into Directory Services Restore Mode flag failed with error code %1.%nPlease see %systemroot%\\debug\\dcpromo.log for more information about errors. |
| 0x00007249 | Virtual domain controller cloning has done. An attempt to reboot the machine failed with error code %1.%nPlease reboot the machine to finish the cloning operation. |
Virtual domain controller cloning has done. An attempt to reboot the machine failed with error code %1.%nPlease reboot the machine to finish the cloning operation. |
| 0x00007250 | An attempt to clear the Boot into Directory Services Restore Mode flag failed with error code %1.%nPlease see %systemroot%\\debug\\dcpromo.log for more information about errors. |
An attempt to clear the Boot into Directory Services Restore Mode flag failed with error code %1.%nPlease see %systemroot%\\debug\\dcpromo.log for more information about errors. |
| 0x00007251 | Virtual domain controller cloning succeeded. The virtual domain controller cloning configuration file %1 has been renamed to %2. |
Virtual domain controller cloning succeeded. The virtual domain controller cloning configuration file %1 has been renamed to %2. |
| 0x00007252 | Virtual domain controller cloning succeeded. The attempt to rename virtual domain controller cloning configuration file %1 failed with error code %2 (%3). |
Virtual domain controller cloning succeeded. The attempt to rename virtual domain controller cloning configuration file %1 failed with error code %2 (%3). |
| 0x00007253 | Virtual domain controller cloning failed to check the virtual domain controller cloning allowed application list.%nThe returned error code is %1 (%2).%nThis error might be caused by a syntax error in the clone allow list file (The currently being checked file is: %3). For more information about this error, please see %systemroot%\\debug\\dcpromo.log.%n%nDetails on virtual domain controller clone allow list can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
Virtual domain controller cloning failed to check the virtual domain controller cloning allowed application list.%nThe returned error code is %1 (%2).%nThis error might be caused by a syntax error in the clone allow list file (The currently being checked file is: %3). For more information about this error, please see %systemroot%\\debug\\dcpromo.log.%n%nDetails on virtual domain controller clone allow list can be found at http://go.microsoft.com/fwlink/?LinkId=208030 |
| 0x40007229 | Starting |
Starting |
| 0x40007230 | The path chosen for the system volume is not accessible. Please either manually delete the contents of the path or choose another location for the system volume. |
The path chosen for the system volume is not accessible. Please either manually delete the contents of the path or choose another location for the system volume. |
| 0x40007231 | The operation was cancelled by the user or a system shutdown was issued. |
The operation was cancelled by the user or a system shutdown was issued. |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0x8000723B | Dcpromo failed because the helper DC %1 couldn't be contacted |
Dcpromo failed because the helper DC %1 couldn't be contacted |
| 0x8000723C | Dcpromo RODC promotion failed because the helper DC %1 is not a Windows Server 2008 DC |
Dcpromo RODC promotion failed because the helper DC %1 is not a Windows Server 2008 DC |
| 0x80007243 | The specified helper DC %1 is a Read Only DC. The helper DC should be a writable DC. Bailing out of DC promotion. |
The specified helper DC %1 is a Read Only DC. The helper DC should be a writable DC. Bailing out of DC promotion. |
| 0x90000001 | System |
System |
| 0xC0007205 | A domain controller could not be contacted for the domain %1 that contained an account for this computer. Make the computer a member of a workgroup then rejoin the domain before retrying the promotion. |
A domain controller could not be contacted for the domain %1 that contained an account for this computer. Make the computer a member of a workgroup then rejoin the domain before retrying the promotion. |
| 0xC0007207 | Managing the network session with %1 failed |
Managing the network session with %1 failed |
| 0xC0007209 | Failed to read the LSA policy information from %1 |
Failed to read the LSA policy information from %1 |
| 0xC0007210 | Failed to read the LSA policy information from the local machine |
Failed to read the LSA policy information from the local machine |
| 0xC0007211 | Failed to write the LSA policy information for the local machine |
Failed to write the LSA policy information for the local machine |
| 0xC0007212 | Failed to upgrade the existing LSA policy into the Directory Service. |
Failed to upgrade the existing LSA policy into the Directory Service. |
| 0xC0007214 | Failed to set the computers DNS computer name base to %1 |
Failed to set the computers DNS computer name base to %1 |
| 0xC0007216 | Failed to determine if domain %1 is a leaf domain |
Failed to determine if domain %1 is a leaf domain |
| 0xC0007217 | Failed to prepare for or remove the sysvol replication |
Failed to prepare for or remove the sysvol replication |
| 0xC0007218 | Failed to complete the demotion of the Directory Service |
Failed to complete the demotion of the Directory Service |
| 0xC0007219 | Failed to configure the service %1 as requested |
Failed to configure the service %1 as requested |
| 0xC000721A | Failed to set the machines product type to %1 |
Failed to set the machines product type to %1 |
| 0xC000721B | A trust with the domain %1 already exists on the parent domain controller %2 |
A trust with the domain %1 already exists on the parent domain controller %2 |
| 0xC000721C | Failed to create a trust with domain %1 on the parent domain controller %2 |
Failed to create a trust with domain %1 on the parent domain controller %2 |
| 0xC000721D | The domain %1 does not have an established trust with this domain. |
The domain %1 does not have an established trust with this domain. |
| 0xC0007223 | Domain %1 was specified as a forest root, when in fact it was not the forest root. |
Domain %1 was specified as a forest root, when in fact it was not the forest root. |
| 0xC0007224 | Failed to create the GPO for the domain %1. |
Failed to create the GPO for the domain %1. |
| 0xC0007233 | The attempt to Install the Active Directory Domain Services failed. The Domain that was specified (%1) was different than the one the backup was taken from (%2). |
The attempt to Install the Active Directory Domain Services failed. The Domain that was specified (%1) was different than the one the backup was taken from (%2). |
| 0xC0007234 | The attempt to install the Active Directory Domain Services failed. The sysvol cannot be placed at the root directory. Retry the promotion with a different sysvol path. |
The attempt to install the Active Directory Domain Services failed. The sysvol cannot be placed at the root directory. Retry the promotion with a different sysvol path. |
| 0xC0007235 | Failed to identify the requested replica partner (%1) as a valid domain controller with a machine account for (%2). This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller not advertising the Active Directory Domain Services. Please consider retrying the operation with %3 as the replica partner. |
Failed to identify the requested replica partner (%1) as a valid domain controller with a machine account for (%2). This is likely due to either the machine account not being replicated to this domain controller because of replication latency or the domain controller not advertising the Active Directory Domain Services. Please consider retrying the operation with %3 as the replica partner. |
| 0xC0007236 | Failed to identify a suitable site for %1. |
Failed to identify a suitable site for %1. |