[David Morinello]

Hi Everyone!

I am deep into testing my first GP 2016 R2 Web Client install and am running into a non-standard “No Endpoint” type error.

I suspect I might be doing something wrong with the Self-signed Security certificate generated in IIS on the Web Client Server (GPWS01), but am I am not practiced enough in this area to pin-point my goof.

Ideas?

 *****************************************************

GP 2016 R2 – Can log into GP ok

Scale Out Web Client Install and Configure

1. One Web Client Server (GPWS01)

1. GP Session Central Service is running

[Don Schaefer]

David,

I recently went through this myself.  First, I put the certificates in the Personal section for each (Computer and Service).  Secondly, you need to add the certificate to a couple of the services as well.  I was unclear which two, so added it to all four services.  

See if that clears up the issue for you.
Don

——————————
Don Schaefer
Mark’s Plumbing Parts
Ft Worth TX
——————————
——————————————-

[David Morinello]

I tried so many possibilities I finally hit on one that worked for me. I installed IIS on the GPSS01 Session Services Server (not documented to do that but someone mentioned it in passing somewhere). I then created a self-signed Certificate there. Then exported/imported it to the Web Client Server (GPWS01).

Two Self-signed Certificates
With Self-signed Certificates created on each, the Web Client Server (GPWS01) & the Session Server (GPSS01), and loaded onto it’s opposite, in the Trusted Root, I finally was able to get it to work.

Then IT came by and offered to generate a wildcard certificate, so I’m off to play with it that way instead. Wheee!

Scaled out is the method we will need for our installation; I just wish there were more details and less assumptions on how to properly configure the systems ahead of “Pushing the install button”.

Have fun everyone!
David

——————————
David Morinello
Senior Dynamics GP Systems Architect
Ascend Learning, LLC
Leawood KS
——————————
——————————————-