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
