Server not operational

Posted on 2007-08-02
Last Modified: 2012-06-21
I have a simple AD network consisting of 2 domain controllers, and some member servers.
All FSMO roles are on server named MDC, both servers run DNS, DHCP, WINS, both are Global Catalog servers
Both servers point to themselves for the DNS resolution.

When trying to open Active Directory Users and Computers or Active Directory Sites and services I will get following errors (they are intermittent and sometimes they will pop up, but than I try again and am able to get to the console)

The Directory Schema is not accessible bacause:
An Iinvalid directory path name was passed
For this reason, The New menu may be inaccurate, and extension snap-ins may not work properly.

followed by:

Data from Active Directory Users and Computers []is not available from domain controller bacause:
The server is not operational
Try again later, or choose another domain controller by selecting Connect to Domain Controller on the Domain Context menui

Nameing information cannot be located for the following reason:
Server in not operational

How do I correct that?

Group Policies would not work and I get following error frequently on all servers:

Source: userenv
Category: None
Evant ID: 1030
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

Above error are more frequent on the server holding FSMO roles (MDC is the mane of the server)
I have tried to move FSMO roles to MBKP, but it did not fix the problem.
Question by:pyotrek
    LVL 13

    Accepted Solution

    Take a look at replmon and see if you are replicating properly.  You might want to point DNS to the first DNS server created for both machines, then restart NETLOGON on each to ensure that the SRV records are re-registered properly.
    LVL 1

    Author Comment

    In replmon I do not see any servers when trying to add them for monitoring.
    If I try to add servers by name I am bale to monitor MBKP but not MDC (which is the server with the problem) I get message that I have no access rights.

    Just tried again and it worked - intermitent problem consistent with what was happening before.

    I did change DNS to point to MDC on both servers and restarteg Netlogon - still the same problem.
    LVL 4

    Expert Comment

    Log on to one of your DCs and run "DCDIAG /e" from the command-line then let us know of any errors
    LVL 13

    Expert Comment

    Also look in your systel event logs.  Sounds like you might have a connectivity problem.
    LVL 1

    Author Comment


    Not sure what solved the problem, but it looks like it is not there anymore.
    Maybe after restarting netlogon I was too impatient, maybe it needed some time to replicate the changes ? who knows ?
    Right aftre I have pointed both servers to the same DNS and restarting the Netlogon - I had still the same issues. Replmon was not allowing me to "vie" the servers in domain. After the second post was posted (2 hours later) - I tried to run DCDIAG /e - I have noticed that I have no errors there anymore?!?!?!? So I went to the event logs and tried to start MMC atc - and everything worked. Waited until today and still no errors.
    I guess the points should go to ocon827679 - THANKS
    LVL 13

    Expert Comment

    Thanks - and you are right about being patient with replication.  

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    PRTG Network Monitor: Intuitive Network Monitoring

    Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

    Companies that have implemented Microsoft’s Active Directory need to ensure that the Active Directory is configured and operating properly. If there are issues found and not resolved, it eventually leads the components to fail or stop working and fi…
    On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

    758 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    8 Experts available now in Live!

    Get 1:1 Help Now