DCPROMO demotion fails causing trouble? Find out what our in-house experts suggest. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team is ready to help customers disable XML-RPC for a WordPress instance hosted in Plesk.

What to do if DCPROMO demotion fails?

If the demotion of a Windows Server computer responsible for hosting the Active Directory Domain Services or domain controller server role fails and you are not sure how to proceed, you have come to the right place. According to our Support Team, we are likely to come across the following error message in this scenario:

Title bar text: Active Directory Domain Services Installation Wizard
Message Text:
The operation failed because:
Active Directory Domain Services could not transfer the remaining data in directory partition
DC=DomainDNSZones,DC= to Active Directory Domain Controller
\\
“The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.”

Furthermore, the DCPROMO.LOG file will also consist of the following:

<date> <time> [INFO] Transferring operations master roles owned by this Active Directory 
Domain Controller in directory partition DC=DomainDnsZones,DC=contoso,DC=com to 
Active Directory Domain Controller \\<DNS name of helper DC... <date> <time>
[INFO] EVENTLOG (Warning): NTDS Replication / Replication : 2091

Moreover, we will also come across a review of the infrastructure object as well as attributes for the DNS application partition in the DCPROMO error and DCPROMO.LOG:

Expanding base 'CN=Infrastructure,DC=DomainDnsZones,DC=contoso,DC=com'...  
Getting 1 entries:  
Dn: CN=Infrastructure,DC=DomainDnsZones,DC=contoso,DC=com  
cn: Infrastructure;  
distinguishedName: CN=Infrastructure,DC=DomainDnsZones,DC=contoso,DC=corp,DC=microsoft,DC=com;  
dSCorePropagationData: 0x0 = (  );  
fSMORoleOwner: CN=NTDS Settings\0ADEL:<NTDS Settings objet GUID>,CN=\<hostname of last
DC to host the partition infrastructure role>,CN=Servers,CN=<active directory site name>,
CN=Sites,CN=Configuration,DC=contoso,DC=com;  
instanceType: 0x4 = ( WRITE );  
isCriticalSystemObject: TRUE;  
name: Infrastructure;  
objectCategory: CN=Infrastructure-Update,CN=Schema,CN=Configuration,DC=contoso,DC=com;  
objectClass (2): top; infrastructureUpdate;  
objectGUID: <object guid>;  
showInAdvancedViewOnly: TRUE;  
systemFlags: 0x8C000000 = ( DISALLOW_DELETE | DOMAIN_DISALLOW_RENAME | DOMAIN_DISALLOW_MOVE );  
uSNChanged: <some USN #>;  
uSNCreated: <some USN #>;  
whenChanged: <date> <time>;  
whenCreated: <date> <time>;

According to our Support Techs, this error is due to the DC that is undergoing demotion is not able to outbound replicate changes to the domain controller that is in charge of the infrastructure FSMO or operational role for the partition present in the DCPROMO log error.

How to resolve: DCPROMO demotion fails

Our proficient Support Team has come up with the following methods to help resolve the issue on hand:

• Try using ADSIEDIT.MSC in order to assign the fsMORoleOwner attribute’s DN path to a live domain controller. This DC should be a direct replication partner of the original FSMO role owner. After that, wait for the change to inbound-replicate to the domain controller in the demotion process.
• In case the domain controller in the demotion process is not able to inbound-replicate changes for the directory partition in question, our Support engineers recommend running the DCPROMO FORCE/ REMOVAL command. This will forcefully demote the DC.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our skilled Support Engineers at Bobcares demonstrated how to disable XML-RPC for a WordPress instance hosted in Plesk.