Error Demoting Server 2008 DC
This is the error I receive when I try to demote the server.. We currently have an "otherDC" on the network that will be the primary DC. The operation failed because: Active Directory Domain Services could not transfer the remaining data in directory partition DC=ForestDnsZones,DC=local,DC=domainname,DC=com to Active Directory Domain Controller \\otherDC.local.domainname.com. "The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers." A command I've run to check the FSMO roles. C:\Users\Administrator.domainname>netdom query fsmo Schema master otherDC.local.domainname.com Domain naming master otherDC.local.domainname.com PDC otherDC.local.domainname.com RID pool manager otherDC.local.domainname.com Infrastructure master otherDC.local.domainname.com The command completed successfully. I am receiving an errors when trying to force AD to sync C:\Users\Administrator.DOMAINNAME>repadmin /syncall /AePDq Syncing all NC's held on localhost. Syncing partition: DC=ForestDnsZones,DC=local,DC=domainname,DC=com SyncAll terminated with no errors. Syncing partition: DC=DomainDnsZones,DC=local,DC=domainname,DC=com SyncAll reported the following errors: Error issuing replication: 8452 (0x2104): The naming context is in the process of being removed or is not replicated rom the specified server. From: a7067e83-8491-448e-89dc-ad2a5cb1d0df._msdcs.local.domainname.com To : 7364ddae-ca84-4a87-afe4-fa9149388971._msdcs.local.domainname.com Syncing partition: CN=Schema,CN=Configuration,DC=local,DC=domainname,DC=com SyncAll terminated with no errors. Syncing partition: CN=Configuration,DC=local,DC=domainname,DC=com SyncAll terminated with no errors. Syncing partition: DC=local,DC=domainname,DC=com SyncAll terminated with no errors.Regards, Andrew
May 10th, 2012 11:05am

Hello, was the DC you trying to demote the FSMO roles holder before? Anyway, as that DC seems not to be demoted, assure all required data is saved or copied to another server and remove the problem DC from the network and NEVER reconnect. Then run metadata cleanup and cleanup AD sites and services, DNS zones and zone properties, Name server tab from the old entries of that machine. http://msmvps.com/blogs/mweber/archive/2010/05/16/active-directory-metadata-cleanup.aspx If you have more DCs and other also have problems you may check and upload the following files: ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server] dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)] dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045) As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: http://msmvps.com/blogs/mweber/ Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2012 11:18am

Hi, Seems this is a recorded issue and discussed before. This problem occurs when tries to contact the infrastructure master for each application partition in the forest and meet following conditions: The partition or the partitions that are referenced in the error message no longer exist. The infrastructure master for the referenced partition or partitions has been forcefully demoted or is offline. To determine the infrastructure master for a partition, query the fSMORoleOwner attribute on the infrastructure object under the naming context root in question. For example, query the fSMORoleOwner attribute on the CN=Infrastructure,DC=DomainDnsZones,DC=contoso,DC=com naming context root to determine the infrastructure master for the DC=DomainDnsZones,DC=contoso,DC=com partition. Similarly, query the fSMORoleOwner attribute on the CN=Infrastructure,DC=ForestDnsZones,DC=contoso,DC=com naming context root to determine the infrastructure master for the DC=ForestDnsZones,DC=contoso,DC=com partition. Run script in this article to modify the fsMORoleOwner attribute on the infrastructure object of the specified Non-Domain Naming Context (NDNC) to an active, or contactable, server. Error message when you run the "Adprep /rodcprep" command in Windows Server 2008: "Adprep could not contact a replica for partition DC=DomainDnsZones,DC=Contoso,DC=com http://support.microsoft.com/kb/949257 For more information please refer to following MS articles: Demoting a Domain Controller Error http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/a56a351f-c3f8-4ad3-bbe6-6a26fafa19a8 dcpromo remove domain controller failed http://social.technet.microsoft.com/Forums/en/winserverDS/thread/72640045-616b-4b6c-8fc4-e30dd8463402 Lawrence TechNet Community Support
May 11th, 2012 2:28am

Hi, Seems this is a recorded issue and discussed before. This problem occurs when tries to contact the infrastructure master for each application partition in the forest and meet following conditions: The partition or the partitions that are referenced in the error message no longer exist. The infrastructure master for the referenced partition or partitions has been forcefully demoted or is offline. To determine the infrastructure master for a partition, query the fSMORoleOwner attribute on the infrastructure object under the naming context root in question. For example, query the fSMORoleOwner attribute on the CN=Infrastructure,DC=DomainDnsZones,DC=contoso,DC=com naming context root to determine the infrastructure master for the DC=DomainDnsZones,DC=contoso,DC=com partition. Similarly, query the fSMORoleOwner attribute on the CN=Infrastructure,DC=ForestDnsZones,DC=contoso,DC=com naming context root to determine the infrastructure master for the DC=ForestDnsZones,DC=contoso,DC=com partition. Run script in this article to modify the fsMORoleOwner attribute on the infrastructure object of the specified Non-Domain Naming Context (NDNC) to an active, or contactable, server. Error message when you run the "Adprep /rodcprep" command in Windows Server 2008: "Adprep could not contact a replica for partition DC=DomainDnsZones,DC=Contoso,DC=com http://support.microsoft.com/kb/949257 For more information please refer to following MS articles: Demoting a Domain Controller Error http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/a56a351f-c3f8-4ad3-bbe6-6a26fafa19a8 dcpromo remove domain controller failed http://social.technet.microsoft.com/Forums/en/winserverDS/thread/72640045-616b-4b6c-8fc4-e30dd8463402 Lawrence TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2012 2:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics