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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win2000 Schema Master Crashed

Status
Not open for further replies.
Sep 29, 2003
44
Help,

The Windows 2000 Server we had setup as the Schema Master Crashed without a backup. This happened 1 year ago and we have had no problems without it, but now I want to upgrade our servers to Win2003 server and I cannot run the adprep /forestprep. I am assuming the problem it the missing Schema master. Anything I can do? Any help would be greatly appreciated.

Thanks

Mark Spencer
 
thanks for the fast response... I'll try it today

Mark Spencer
 
ok, now new error, The is in the schupgr.log file:

Opened Connection to LINDSEY5
SSPI Bind succeeded
Found Naming Context DC=lindsey,DC=com
Found Naming Context CN=Schema,CN=Configuration,DC=lindsey,DC=com
Found Naming Context CN=Configuration,DC=lindsey,DC=com
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 member of the schema admin group.

and the adprep.log file is:

Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=UID,CN=Schema,CN=Configuration,DC=lindsey,DC=com.
LDAP API ldap_search_s() finished, return code is 0x20
Adprep successfully determined whether Microsoft Windows Services for UNIX (SFU) is installed or not. If adprep detected SFU, adprep also verified that Microsoft hotfix Q293783 for SFU has been applied.
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\20040926145827 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 master in order to complete this operation.
[User Action]
Check the log file, Adprep.log, in the C:\WINNT\system32\debug\adprep\logs\20040926145827 directory for more information.



 
Did you seize (not transfer) the schema FSMO? Are you running adprep on the server that you seized the schema role to?
 
yep, I siezed the Schema and got further on the adprep, but this new one is wierd. I have gone through and removed the dead DC from the active directory with adsiedit and just finished verifying my changes and forcing an AD Replication to the other 2 servers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top