none
Current schema master (offline): ERROR - Help!

    Question

  • Picture of my error message

    Hi,

    We are in the process of demoting our current DC from 2003 x86to 2008 x64 std on a different server. We moved everything over and left the FSMO roles to last. It worked for about 30 seconds and now it says that the Current schema master (offline) and ERROR.

    How can I get everything to work again?
    I dont want to bring down the old domain controller until i am 100% sure that logins will still process - as i work at a school and it is the start of term and it is vital that there is no downtime!

    Thank you for your help!
    Sean
    Thursday, July 31, 2008 1:12 AM

Answers

  •  

    Hi,

     

    From your description, I understand after several minutes when you transfer FSMO roles from windows server 2003 to 2008, you found 'schema role' is missing in GUI. If I misunderstood, please let me know.

     

    There is possible replication latency between two DC, which may cause the Schema role holder was not visible in GUI. So, please wait more time to see if Schema role is visible in GUI. If not, please perform the following steps and provide me the corresponding information:

     

    1) Use Netdom query command to view which DC holds Schema FSMO roles? If you can view it in, please refer to the following article to clean metadata of old DC.

     

    metadata cleanup

    http://technet2.microsoft.com/windowsserver2008/en/library/8ff66708-2ad0-4f52-982d-376a50a0e2dd1033.mspx?mfr=true

     

    2) You can verify the operating system support level of the schema by looking at the value of the Schema Version registry subkey on a domain controller. You can find this subkey in the following location:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

     

    Please check if it match with real environment?

     

    13=Microsoft Windows 2000

    30=Original release version of Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1(SP1)

    31=Microsoft Windows Server 2003 R2

    44=Microsoft Windows Server 2008

     

    3) Is the old DC offline? If so, please use ntdsutil.exe to seize the schema role again to test the result. If it's online, please run ntdsutil.exe to transfer FSMO role again.

     

    Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller

    http://support.microsoft.com/kb/255504

     

    4) Is there any error message occurring during promoting Windows sever 2008 as an additional DC?

     

    5) If the old DC is online, please check if there is any error message of DC replication in Event log? If so, maybe, this problem is related to DC replication. Please help me collect the MPSReport file on the problematic DC.

     

    =============

    1.     Download the executable file from the following URL specific to the support issue being experienced.
    http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXE

    2.     Copy the file to the problematic computer.

    3.     Double-click the executable to launch the report gathering tool.

    4.     Accept the EULA.

    5.     Then, the reporting tool begins to gather necessary information on your system.

    After the tool finishes gathering the information, a cab file is generated in the following folder: C:\WINDOWS\MPSReports\DirSvc\cab.

     

    Send it via tfwst@microsoft.com with following three lines in the email body:

     

    Current schema master (offline): ERROR – Help

     

    http://forums.technet.microsoft.com/en-US/winserverMigration/thread/f0552f83-ab2b-4639-aa71-b386bfa0b1a1

    Morgan

    =========

     

    Hope this helps.

    Thursday, July 31, 2008 10:14 AM
    Moderator