Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Transfer FSMO role fails with error 4

Status
Not open for further replies.

AJester

MIS
Oct 31, 2003
5
US
Hello,

I'm trying to transfer the schema master fsmo role over to a different DC. The current FSMO role holder is up and running fine, so a seizure is not necessary (and really is out of the question anyway because it is the main file server as well). DNS is working correctly, everything is pingable, I have schema admin rights, etc. Unfortunately I'm running into the following error when I try to do it:

ldap_modify_sW error 0x35(53 (Unwilling to perform)
ldap extended error message is 000020F1: SvcErr: DSID-0321016E, problem 5003 (WILL_NOT_PERFORM)

Win32 error returned is 0x20f1 (This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.)


I can't find even a mention of this error anywhere. This is getting to be a time sensitive issue, so any help would be greatly appreciated. Thanks!

Adam
 
Try rebooting the machine and then transfer the role again. There could be a service that is hung.
 
The reason we want to move this FSMO role is to shift some of our downtime. We have to run forestprep and domainprep, which involve unplugging the machine from the network. Since this is the main file server, this creates a scheduling issue that is best avoided if possible. In addition to this, the machine that it sets on right now has just gone off maintenance and is unavailable for renewal. Should there ever be a problem, I don't want it to be on a machine that holds all 5 FSMO roles.

I actually had rebooted a few times late last night but still to no avail. Do you think compacting the NTDS database would help?
 
I'm guessing you want to add a Win2K3 server if you will be running adprep /forestprep & adprep /domainprep? You do not need to to take the server offline to run these.

Also, If you have more than one DC, then you could always transfer the other roles over and leave this one where it is and do a siezure for the schema master if you retire the server.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
You are correct. We're adding a 2003 server to a 2000 mixed-mode domain and need to run those preps. In Microsoft KB article 278875, it says that you need to disconnect the schema master from the network, run the forestprep, plug it back in, and let it replicate. I've never run these (obviously), so I was just going to go by what Microsoft says (blindly, much like sheep, haha). It would really help things in our environment as a whole if we could move these roles off this server anyway. I like to think my internet searching skills are on the honed side of mediocre, but I can't find that error anywhere. What else ya got? Thanks for your help.

Adam

 
As I said above, this error can occur if a service is hung.

Did you try rebooting the machine and transferring again?
 
Thanks for sharing that KB. I've done a few upgrades to 2k3 and not taken the schema master offline and have still had success. Having read this KB I'd say go with what MS suggests on this.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
This q article is the subject of much debate, trust me.

There are initial synchronization requirements for DCs running 2000 SP4 or higher. Servers that hold FSMO roles will not advertise those roles until they replicate with their replication partners (at least one partner).

So if you were to reboot the schema master after unplugging it from the production network, it will never advertise that it holds the schema role, and adprep will fail.

The revised procedure is detailed in this article:

If you want to isolate the schema master while running adprep, we recommend that you disable outbound replication.
 
Cool info. A star for you sir.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Alright, here are some verdicts:

- The transfer error was definitely cured by a reboot of the NEW schema master. I thought you meant the CURRENT schema master. Everything's good to go there, everything transferred, no problem.

- Just to be safe, and on coin flip-like decision making, we decided to take the server offline to do the forestprep. It did work, but I'm convinced it would have without doing that.

Everything else seems to be up and running. It's 4:10am and I'm just waiting for everything to replicate right now. Thanks very much for all your help guys.

Adam
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top