715
Hi,
We recently installed web client for GP2016 R2, using scale out deployment. After all installations, when we try to connect GP webclient after supplying domain credentials, GP hangs on 'Microsoft Dynamics GP' window as per screen shot attached.
Any help on this ... !
Regards..
*This post is locked for comments
This issue seems like authentication/Certificate.
First thing first. You should try accessing Web Client on the same server where it has been installed with localhost:port/.../
If it is working fine there, you may need to reinstall the Certificate for Remote Clients (same LAN/DOMAIN) on IIS and then run REPAIR of Microsoft Dynamics GP Web Components (from control panel / Program and Features) to make sure that Certificate is properly binded with all hosts.
If it is not working on localhost then I'll suggest you to reinstall the Web Client and Web Components (including Web Services).
All good points from Derek. I've also seen cases where this issue is due to the site itself, i.e., ESPN.com not being a part of the trusted internet zone in your browser settings.
Normally when Web Client hangs here, it is having an issue finding the Runtime Service, which is what is used to load the GP application into the browser window.
You mentioned you're using a scale-out deployment, how many servers do you have in this environment for Web Client?
Also, what type of certificate are you using?
Are you using tenant services at all?
What we commonly see is that a third-party and/or wildcard certificate will be setup for use with Web Client, for example using a host name such as ESPN.com, which isn't the FQDN at all. What happens then, is that when we tie the certificate to the Runtime Service, Web Client will look for this service via the host name applied to it and because of that, there needs to be something that will let the servers know that when they receive a call for ESPN.com, that it needs to be routed to the IP address of the session service server, where the runtime service will exist.
A good test of this is to ping the host name setup on the Runtime Service from all machines users are attempting to access Web Client from, and verify that it returns the IP address of the session host server where runtime services exists on. If it doesn't, you'll need to setup some type of forwarding to go from the host name to the IP address of the correct server.
The 'Dynamics' log in the Event Viewer on the server may also have additional information that can help with this type of troubleshooting.
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (