Return
-
Title
"Server not configured" exception after upgrading GPOADmin to a new release or applying a hotfix/update -
Description
Attempting to connect to the console after upgrading GPOADmin may produce a "Server not configured" exception message. Example of exception message below:
'Quest.Avalanche.Exceptions.ServerNotConfiguredException' was thrown.Server stack trace:at Quest.Avalanche.VersionControl.VersionControlManager.get_VersionControlMaster()at Quest.Avalanche.VersionControl.VersionControlManager.get_VersionControlRootPath()at Quest.Avalanche.VersionControl.VersionControlManager.GetSids(String type,ICollection`1 initializationSids)at Quest.Avalanche.VersionControl.VersionControlManager.CanCurrentUserConnect()at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) -
Resolution
Log on to the GPOADmin server as the service account and connect. Configure the server to connect to the previous configuration store location (AD or AD LDS).