Notifications
Announcements
No record found.
We have a Dynamics GP 2013 R2 Web Client implementation that has been running for several months now and recently we had two incidents where at certain locations the GP web client would stop working with the error during the initialization phase saying "An error occurred while initializing communication with the server". The error only effected two locations out of 20+ locations connected over a private WAN to GP. The quick fix is for them to run the https://*************/GP/DynamicsGPTrustedApp.msi utility and that allows the GP Web client to run again. We have not had to run this utility before and I'm not sure why out of the blue it has become a requirement at certain locations. The end users do not require the enhanced functionality that running this utility is supposed to provide but it seems to fix what ever problem is introduced. The only change I can think of that was made is the client added their domain name to the IE Trusted sites list. Forexample microsoft.com was added to the trusted sites but microsoft would be the name of the client.
*This post is locked for comments
Are you using self signed certificates or did you purchase a cert like a wild card?
If you're using self-signed then you'll need to make sure that the certs are located in the proper cert authority. I'm not sure if this scenario pertains to your situation or not but I've run across some webclient issues and most pertain to certs. Whether self-signed, expired or wildcard, I've had problems with all 3.
We purchased a commercial certificate similar to gp.microsoft.com.
Sorry I forgot to respond to you, are the other "locations", I'm assuming that these are different geographical locations, on different domains?
Same domain....everyone authenticates to GP using a domain like microsoft\tcruse
I'm wondering if you have a GPO that's affecting these locations, or actually not affecting these locations because they're having troubles reaching the dc to get the proper policies which is why the trusted app is fixing it. I've had DC issues where policies weren't being applied correctly because the DNS wasn't being resolved.
Might want to check with your network peeps if this is handled by them to see if this might be the issue.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
mtabor 1
