We recently updated our SSL certificates for our GP environment, but now unable to access the web client. I tried multiple uninstalls, and fresh installs, including new databases for the Web Client, but after all of that, still seeing an issue as shown below:
Session Central Service was not able to successfully communicate with the Session Service at HOSTNAME:48651/SessionService. The exception details are:
System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Object reference not set to an instance of an object. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dexterity.Resource.DexDictionary..ctor(IDexResourceProvider resourceProvider)
at Microsoft.Dexterity.Resource.DexDictionary.Open(IDexResourceImplementation resourceImplementation, DexDictionaryConnection connection)
at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Implementation.WCDexRuntimeHost..ctor(DexRuntimeArgs dexRuntimeArgs, IWCDexImplementation implementation)
at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.DexRuntimeService..ctor(DexRuntimeArgs args, Int32 desktopHeapSize, Boolean runtimeLogEnabled, String customRuntimeSettings)
at Microsoft.Dynamics.GP.Web.Services.Runtime.RuntimeService..ctor(SessionProcessSharedData sharedData, String appDirectory, String setFile, String dexInitializationFile, Int32 desktopHeapSize, Boolean runtimeLogEnabled, String customRuntimeSettings, Str...).
Steps taken:
- Complete uninstall and fresh install of GP Web Client, this time not applying certificates for the Session Service and Session Central Service
- Same as above, but applying the certificates for those 2 services
- In addition, manually modified SessionService.config and SessionCentralService.config file to use the correct hostname, otherwise it defaults to NetBIOS name of the machine
- Verified user being used to test login is part of the GP users group in AD
- Verified test user can access GP using a thick client
Any idea of what could be the issue here?