Return
-
Title
Console previously connected without issue but now getting "Server not Configured" or "Server is not operational" exception error -
Description
The below error is occurring when connecting within the GPOADmin client:
"Exception of type 'Quest.Avalance.Exceptions.ServerNotConfiguredException' was thrown"
The console was previously connecting without issue.
-
Cause
GPOADmin was previously configured to connect to a specific DC for the config storage but this DC is not currently available -
Resolution
Logon to the server with the GPOADmin service account and connect using the console. This should prompt to chose a different DC for the config storage. Chose a DC that is physically close to the GPOADmin server. The preferred domain controller may also need to be updated within the Options of the console.
This can also be updated manually by changing the DC name within the below registry string:
- HKLM\SOFTWARE\Quest\GPOADmin\VCConfig\ServerName
If a preferred domain controller is set then the below domain entry may also need to be updated:
- HKLM\SOFTWARE\Quest\GPOADmin\ServerConfig\PreferredDomainControllers\<domainname>
-
Additional Information
This solution only applies if the config is stored in AD, if it is stored in AD LDS then there may be an issue with the AD LDS instance.