Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-0251: "Server not operational" error in Administrator Console Setup Wizard

Centrify DirectControl ,  

12 April,16 at 11:02 AM

Applies To:
Centrify DirectControl Administrator Console versions 3.0.0 and 3.0.1

Problem:
(1) After installing the DirectControl Administrator Console, and then running the Setup Wizard to configure DirectControl with the Active Directory forest, “The server is not operational” message appears.

(2) When trying to add users to a Zone, or when clicking on the Centrify Profile tab for an AD user in ADUC, you see the message "Server Not Operational"

Cause:
This is a problem in versions 3.0.0 and 3.0.1 of the DirectControl Administrator Console because they expect to see an A record in DNS. If not found, “The server not operational” error message is displayed.

Resolution:
This will be fixed in DirectControl 3.0.2.

There are two workarounds that can be employed:
1. Create the A record in the DNS. This will be the DNS that the Windows machine with the Administrator Console installed is pointing to. You can create this manually, in the DNS Management MMC, or run “netdiag /fix” on the machine servicing DNS and the A record will be created. Please first read about netdiag in Windows Help and run “netdiag /?” before running “netdiag /fix”.
2. On the Windows machine that has the Administrator Console installed, edit the hosts file, C:\WINDOWS\system32\drivers\etc\hosts. Add the line:
<IP_address_of_Domain_Controller> <domain_name>
Note that it is the <domain_name> and not the <DC_machine_name>
For example:
170.20.20.20 centrify.com
If you have this IP already existing, you can append the domain, as in:
170.20.20.20 dc1.centrify.com centrify.com


Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.