Schema master problems

[darren97]

Hello AD experts.

I recently checked the schema on our primary domain controller within mmc and found that when I right click Active Directory Schema>Operations master that there was an error. In the box where the current schema master should have been listed was blank, and the box underneath had 'ERROR' in it and said that the schema master was offline.
I transfered the schema master and domain naming master roles manually, and when I went back into the mmc there was an entry for the schema master and it was reporting a status of online.
I rebooted the server after close of businees, and checked again, the server has reverted back to an error status. I have 2 domain controllers. The server that should be the schema master and domain naming master is also the RID/PDC and GC. The other DC is the infrastructure master. The rid/pdc/infrastructure roles when checked in AD all seem OK. If anyone can help with my missing schema master that'd be great.

 

[jfwebber]

Anything in the event viewer relating to this issue?

Jim

Jim Webber
Network Administrator MCSE CNA

 

[Udir]

I had that problem last month. I had to run ntdsutil and go into role and seize all the options. Once I did this my problems went away. I noticed the problem when I was trying to extend the schema.

Let me know if you need more info.

 

[darren97]

thanks for replying.

Nothing of note in the event viewer. Seizing the role using ntdsutil has the same result as transferring the role. If I issue the command 'seize schema master' I get a message saying seizure not required, transfer successful.
I'm getting rather paranoid about this now, bare with me and I'll explain.
We haven't touched this domain in months, and all has been running smoothly. We decided to do some routine maintenance, and I was checking AD etc when I came across the original issue. After I made the changes (Friday last week) our file server reboots unexpectedly when certain users try to logon. It almost looks like the Lsass process is hanging when querying logon attempts. i know from previous experience that this can happen when the dc is also a gc. I've moved the gc to another server (unfortunately the only other dc is the infrastructure master, and MS say not to put a gc on infrastructure master,,,but this is the real world). I'm almost certain that innocently trying to resolve the original issue has caused me a shed load more problems.
Any ideas?

 

[darren97]

Hello

Ignore the above with reference to the server constantly rebooting, it was a completely unrelated problem that IBM have resolved by replacing the systemboard.

 

[ramblinrek]

Did you ever completely resolve your problem? I am interested because I "lost" my schema master last night when attempting to use ntdsutil to transfer schema operations master from one Windows 2000 server on my WAN to another. There weren't any error messages when I performed the transfer, but less than a minute later the server that was the original operations master crashed (this server has unexpectedly crashed 3 other times in the past 2 months). I rebooted with no obvious problems, except that neither server seems to be the scheme master (both say "ERROR" for current operations master in the mmc plugin).

 

[Kruzer]

Newbie question,

How do you modify the master schema for Active Directory? Do you use any tools like SQL server to modify the schema?

Thanks!

Dano
dan_kryzer@hotmail.com
What's your major malfunction