Error demoting running DCPROMO - failed to stop file replication service
We have three DCs. The oldest of them failed (partition table corruption) and we were able to actually get it to boot enough to move all the FISMO roles to other servers. It also runs DNS. I have another DNS server as well.
As I understand it I do not need to do anything with the DNS, they are all primary.
When I try to run dcpromo to demote the corrupt server it gives me an error saying it could not stop the file replication service. I checked it and it's stuck on stopping.
I can't reboot the server as it took two hours just to start up and login and I don't know if it would start up again.
What can I do to stop the service ? Can I force the removal of the DC from the domain on the other machines? What are the drawbacks of doing this?
As I understand it I do not need to do anything with the DNS, they are all primary.
When I try to run dcpromo to demote the corrupt server it gives me an error saying it could not stop the file replication service. I checked it and it's stuck on stopping.
I can't reboot the server as it took two hours just to start up and login and I don't know if it would start up again.
What can I do to stop the service ? Can I force the removal of the DC from the domain on the other machines? What are the drawbacks of doing this?
Before depromoting the main DC promote (seize) other DC.
make sure all FSMO roles are transferred to other DC and than try to decpromote the existing one.
make sure all FSMO roles are transferred to other DC and than try to decpromote the existing one.
this will help you.
http://support.microsoft.com/kb/216498
http://support.microsoft.com/kb/216498
run dcpromo /forceremoval
ASKER
Hi Mike,
Yes the other DNS server is also a DC.
One question... They all are global catalog DCs and when I was moving the roles it said I could not move the role of infrastructure master to a DC that is also a GC but the one I was trying to move it from that failed was both the infrastructure master and a GC. I didn't do anything with it since I read online it doesn't matter if you move it if they are all GC DCs. Is this true?
Yes the other DNS server is also a DC.
One question... They all are global catalog DCs and when I was moving the roles it said I could not move the role of infrastructure master to a DC that is also a GC but the one I was trying to move it from that failed was both the infrastructure master and a GC. I didn't do anything with it since I read online it doesn't matter if you move it if they are all GC DCs. Is this true?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As i can see from your comment "As I understand it I do not need to do anything with the DNS, they are all primary."
Are they primary or AD-Integrated.
If its primary dns zone,right click the zone & make it AD-Integrated dns,give time for replication or force replication by right click on zone & update server in dns server.
if client is getting IP from DHCP,change the primary & secondary dns server into dhcp.
For static configured dns on server, need to change else Server pointing to wrong dns will logged unwanted events also failover will not happen when primary fails alternate will not take over.
After doing dcpromo /forceremoval make sure you run metadata cleanup.
Verify the records are removed from MSDCS folder in dns admin console as well as from cleanup the object from ADSIedit.msc.
If there is any old entry there will create an issue & log the events.
Are they primary or AD-Integrated.
If its primary dns zone,right click the zone & make it AD-Integrated dns,give time for replication or force replication by right click on zone & update server in dns server.
if client is getting IP from DHCP,change the primary & secondary dns server into dhcp.
For static configured dns on server, need to change else Server pointing to wrong dns will logged unwanted events also failover will not happen when primary fails alternate will not take over.
After doing dcpromo /forceremoval make sure you run metadata cleanup.
Verify the records are removed from MSDCS folder in dns admin console as well as from cleanup the object from ADSIedit.msc.
If there is any old entry there will create an issue & log the events.
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
For you the FSMO roles were already taken care of....just for others that may come across this question if the FSMO roles were not transferred then you can seize those http://www.petri.co.il/seizing_fsmo_roles.htm
Is your other DNS server also a DC?
Thanks
Mike