Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Unable to access GP Web Client after certificate updates

Posted on by Microsoft Employee

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:

  1. Complete uninstall and fresh install of GP Web Client, this time not applying certificates for the Session Service and Session Central Service
  2. Same as above, but applying the certificates for those 2 services
    1. In addition, manually modified SessionService.config and SessionCentralService.config file to use the correct hostname, otherwise it defaults to NetBIOS name of the machine
  3. Verified user being used to test login is part of the GP users group in AD
  4. Verified test user can access GP using a thick client

Any idea of what could be the issue here?

Categories:
  • Suggested answer
    RE: Unable to access GP Web Client after certificate updates

    I've seen where, if the Binding in IIS Manager of the SSL certificate was not setup correctly, that can cause issues, the most common is the Host Name field is specified with something when it needs to be empty/blank, as mentioned:

    5. In IIS Manager, for the site that you’re installing Web Client onto, click on ‘Bindings’ or right-click on the site and choose ‘Edit Bindings’.

        In the Site Bindings window that opens, select the HTTPS binding and click the ‘Edit…’ button.

        In the Edit Site Binding window that opens for HTTPS, make sure the IP Address field is set to ‘All Unassigned’, the port is normally 443, the Host Name field needs to be blank/empty and the ‘Require Server Name Indication’ option should be un-marked.

        In the SSL Certificate field, select your self-signed SSL certificate you’re using for Web Client and click OK to save any changes and close that window, then click Close to close the Site Bindings window.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to access GP Web Client after certificate updates

    Thanks Beat Bucher,

    The SSL cert we are using is from a separate certificate authority server, and we are not approved to use wildcard certificates so that option is ruled out. We have escalated with a Microsoft rep, who is perusing the HTTP traces as we speak, but I am going to dig deeper into the SSL bindings based on your suggestion. I appreciate the response.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to access GP Web Client after certificate updates

    Thanks Derek for the detailed explanation and steps on the URL reservations. Unfortunately, this did not resolve the issue, we still saw the same errors whether or not the certificates were applied.

    We've escalated with Microsoft, even checking the HTTP/S traffic on the server, but no clues as yet. I suspect something within the server environment is causing it, but there are no signs to indicate so.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at
    RE: Unable to access GP Web Client after certificate updates

    Thank you Derek for this complete detailed reply on the Web Client re-install..

    I had just spent hours on trying to re-install a GP 2015 RTM web client (yes, the one still using SilverLight) for a customer where the SSL Cert had expired too and it was a real nightmare.

    Despite the removal of the GPCONFIGURATION database, it would not help and I ran into multiple problems..

    In the end, it was all about he IIS configuration, the bindings that were done in a weird way by the previous consultant that had it initially installed and some clean-up on the old SSL Certs.

    Once I had that all out of the way, the GP Web client started to work again. The key was that the SSL Cert which was self-signed from the domain was created on the FQDN of the server (i.e.  greatplains.contoso.com) instead of being a wild-card cert like *.contoso.com.  

    If I tried to open the browser on just the shortname, I'd get an SSL Cert warning and would not be able to run the login correctly.. it would open up to a certain point but then throw connection errors and the like.

    Kishan,

    From my past experience, there is no way you can get the GP Web client work without using the SSL Cert all the way thru all the services..

  • RE: Unable to access GP Web Client after certificate updates

    You mentioned 'This time not applying certificates for the Session Service and Session Central Service'.  If you initially had the SSL certificate tied to these two services, did you manually delete the URL reservations before reinstalling Web Client again?

    if not, it may be a matter where the URL reservation is setup for these two services to show https://, when they're not setup to use http:// and that difference can cause Web Client not to be able to launch and/or spin up a user session.

    The steps to completely uninstall and reinstall Web Client are here:

    1. From Control Panel > Programs > Programs and Features, uninstall Microsoft Dynamics GP Web Components.

    2. Browse to C:\Program Files\Microsoft Dynamics\ and verify the Web Components directory is completely gone or empty.

    3. Run the 'netsh http show urlacl' script in the Command Prompt: Admin window and verify that you don't see any URL reservations for the following:

    -- https://+:443/RuntimeService/

    -- https://+:48651/SessionService/

    -- https://+:48650/SessionCentralService/

       If you see any URL reservations for the port numbers/services mentioned above, use the example script to delete the URL reservation:

                netsh http delete urlacl url=https://+:443/RuntimeService/

    4. In SQL, delete the existing GPCONFIGURATION database.

    5. In IIS Manager, for the site that you’re installing Web Client onto, click on ‘Bindings’ or right-click on the site and choose ‘Edit Bindings’.

         In the Site Bindings window that opens, select the HTTPS binding and click the ‘Edit…’ button.

         In the Edit Site Binding window that opens for HTTPS, make sure the IP Address field is set to ‘All Unassigned’, the port is normally 443, the Host Name field needs to be blank/empty and the ‘Require Server Name Indication’ option should be un-marked.

         In the SSL Certificate field, select your self-signed SSL certificate you’re using for Web Client and click OK to save any changes and close that window, then click Close to close the Site Bindings window.

    5. At this point, you can then launch the reinstall of Web Client for Dynamics, again.  

          On the IIS/web server, for the Session Central Service, we only need to enter the domain account that will be running that service, which is what you have/had setup.  We don’t want to tie the certificate to this service.

          On the session host server(s), for the Session Service, again you only need to enter the domain account that will be running that service and not tying the certificate to this service either.

          For the Runtime Service on the session host server(s), we have to add the certificate to it, thus it’d get the host name of the SSL certificate being used for Web Client.

    6. Once the reinstall of Web Client is completed successfully including the creation of the GPCONFIGURATION database again, you'd be ready to test the Web Client login again to verify users can access Dynamics GP through it or not.

       If it doesn’t work still, we’d want to look at the Event Viewer/Dynamics log again to see what additional information it is showing, to go with any errors that are seen in the browser window, if any.

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans