ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable).Why..?

  • Thread starter Thread starter David.R
  • Start date Start date
D

David.R

Hi guys i am trying to upgrade my win2000 AD Schema to Support Win2003
Domains ..so i use the ADPREP /FORESTPREP from the win2003/ i386 CD and iget
thi's ERROR :

ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable).
----------------------------------------------------------------------------
--------------------------- WHY..?

Full Eroor INFO :

Opened Connection to 2000ADV
SSPI Bind succeeded
Current Schema Version is 13
Upgrading schema to version 30
ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable).
If the error code is "Insufficient Rights", make sure you are logged in as a
mem
ber of the schema admin group.
Adprep was unable to upgrade the schema on the schema master.
[Status/Consequence]
The schema will not be restored to its original state.
[User Action]
Check the Ldif.err log file in the
C:\WINNT\system32\debug\adprep\logs\200201111
35657 directory for detailed information.

Adprep was unable to update forest-wide information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema
maste
r in order to complete this operation.
[User Action]
Check the log file, Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20020
111135657 directory for more information.

....
thanks for you help .
David
 
"ERROR: Failed to transfer the schema FSMO role: 52 (Unavailable)" in the
log.



This means the current domain controller is not the schema FSMO role owner,
and trying to transfer the role from the other domain controller (whoever is
the FSMO role owner) to this domain controller failed.



To check who is the current schema fsmo role owner, use either the Schema
snap-in or the ntdsutil tool to view the current Schema FSMO role owner.



Note



To increase the DS diagnostics logging level (which logs schema failures to
the event log, sometimes provides hints as to why a schema operation is
rejected) increase the value of the Internal Processing entry in



HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics to
Level 3.



I would suggest that you do the Schema Upgrade on the server that holds the
Schema Master FSMO Role or start by changing the registry and look at the AD
Event Log.



/// MCSE, MVP Active Directory ///
 
Back
Top