• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2479
  • Last Modified:

Error trying to transfer Schema Master on Windows 2000 domain

Hi guys!  I have the following setup;

Windows 2000 Domain

2 DC's, Shore1 and Shore2

Shore1 used to be a NT DC upgraded to windows 2000 and 2000 Domain DC

I installed a fresh version of Windows 2000 on a new server called Shore2 and promoted it as a secondary DC

Now I want to get rid of Shore1 and bring in another Fresh install Server.

Anyway, I'm trying to transfer all FSMO roles to Shore2 and I was able to transfer all the roles fine except when transferring Schema Master I get this error;

fsmo maintenance: transfer schema master
ldap_modify_sW error 0x34(52 (Unavailable).Ldap extended error message is 000020AF: SvcErr: DSID-0321023C, problem 5002 (UNAVAILABLE), data 3 Win32 error returned is 0x20af(The requested FSMO operation failed. The current FSMO holder could not be contacted.))
Depending on the error code this may indicate a connection,ldap, or role transfer error.
Server "shore2" knows about 5 roles
Schema - CN=NTDS Settings,CN=SHORE1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=shoremortgage,DC=com
Domain - CN=NTDS Settings,CN=SHORE2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=shoremortgage,DC=com
PDC - CN=NTDS Settings,CN=SHORE2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=shoremortgage,DC=com
RID - CN=NTDS Settings,CN=SHORE2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=shoremortgage,DC=com
Infrastructure - CN=NTDS Settings,CN=SHORE2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=shoremortgage,DC=com

Any ideas would be greatly appreciated, should I just Seize the role?
0
tnowakow
Asked:
tnowakow
1 Solution
 
weareitCommented:
Server are you initiating the transfer from?

-saige-
0
 
tnowakowAuthor Commented:
I am on Shore2 using the ntdsutil.exe

fsmo maintenance: connections
server connections: connect to server shore2
Binding to shore2 ...
Connected to shore2 using credentials of locally logged on user
server connections: q
fsmo maintenance: transfer schema master
ldap_modify_sW error 0x34(52 (Unavailable).
Ldap extended error message is 000020AF: SvcErr: DSID-0321023C, problem 5002 (UN
AVAILABLE), data 3

Win32 error returned is 0x20af(The requested FSMO operation failed. The current
FSMO holder could not be contacted.)
)
Depending on the error code this may indicate a connection,
ldap, or role transfer error.

Based on MS's docs it said to run ntdsutil on the Server you want to transfer the roles to, is that correct?
0
 
weareitCommented:
Try initiating the Schema transfer from Shore1 to Shore2 (physically being logged into Shore1).

-saige-
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
suivethfirstCommented:
Can shore2 resolve the name shore1? Do the servers currently replicate properly?

Do NOT seize the role if the server shore1 is still on the network - this is intended only for when a server is not expected to ever be reconnected to the network.
0
 
Kini pradeepCommented:
did you try that using the GUI mode ?? should not make any difference though but i am curious to see what message it gives when you open the schema management console.
regsvr32 schmmgmt.dll on the cmd.
MMC ===> load the schema snapin.
connect to the other Dc and change the operation masters role..
I have seen a couple of instances where the issue was resolved by seizing the roles, but as suivethfirst mentioned it should be a last resort as you would have to do a metadata cleanup to remove the entries for shore1.
0
 
ocon827679Commented:
Are you using the "enterprise administrator" account?  

0
 
tnowakowAuthor Commented:
Thanks for all the help guys but nothing worked.  I was on Shore1 and tried it with ndtsutil and got an error, that made me google it some more and I read to try dcdiag to make sure dns was correct.  I checked and I got an error.  So I deleted a dns entry in one of my DC's and ran ntdsutil again from shore1 and it worked.  Now I'm going to wait for it to replicate before demoting shore1 off the network.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now