Microsoft Dynamics GP (Archived)

GP 2013 Web Client Error

(0) Share

Report

Posted on by YasserMahmoud

270

Dear All,

I have a problem with GP 2013 Web Client.

My scenario as below:

- GP 2013 deployed on external server (Win 2008 R2) that has fixed IP on internet.

- GP 2013 deployed using Standalone model

- The server contain our domain controller and DNS.

- Web Server has a public certificate from GoDaddy Site and already setup as Microsoft videos.

http://www.youtube.com/watch?v=UUa48fILf3Q&feature=youtu.be[object]

When I try to access GP Web Client from inside the server, I can and no problem with it.

If I try to access it from one of my clients, I face the below error:

Severity: Critical

Summary: An error occurred while initializing communication with the server.

Details:

The remote server returned an error: NotFound.

Severity: Critical

Summary: An error occurred while initializing communication with the server.

Details:

[HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.30214.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

Please if any help on that i will be appreciated. i spent more than week on that i cannot solve it.

*This post is locked for comments

All responses (10)

Answers (0)

Jonathan Fear on at

Like (0)

Report

RE: GP 2013 Web Client Error

I apologize that what I am noting is not making sense but I am not sure how else to explain this process. You cannot use the IP address unless that is covered under your Cert. If you get to the Web Client login page and you received a Cert error whether it is external or internal GP is not going to work. You will never get logged into GP because traffic from Web Client is not going to be encrypted and therefore not work.

At this point I would recommend you reach out to your partner for further troubleshooting/questions or open a support case.
YasserMahmoud 270 on at

Like (0)

Report

RE: GP 2013 Web Client Error

OK, we run at the same space

I already installed all GP Web Client component on one server and using default ports Session Central Service (48650), Session Service (48651), and Runtime Service (48652). Server has name server1.contoso.com and public IP Address 11.22.33.44. IIS and its https protocol (port 443) use public SSL certificate, not Self-Signed, had common name server1.contoso.com.

I successfully access GP Web Client from inside server without any problem, only Cert not verified.

So, what is the best solution to successfully access the GP from clients (External/Internet)?
Jonathan Fear on at

Like (0)

Report

RE: GP 2013 Web Client Error

This is because of the exact same thing I noted last time. The cert has to protect the URL you are putting in for the hostname on the Runtime Service. If it does not then the traffic that will be sent on the Runtime Service URL/Port is not going to be protected by the cert, Web Client isn't going to allow it.

Also if you are using 443 as the port for Runtime you can only do that if both Session Central and Session Service are installed on the same machine as your IIS site. Otherwise you need to look at changing the runtime service to run on another port and do port forwarding.
YasserMahmoud 270 on at

Like (0)

Report

RE: GP 2013 Web Client Error

Hi Nataraj

Thanks for your reply.

I already visit the link you mentioned and done the steps. I change the Runtime Service Port to 443 in SessionService configure file but I face error massage “Service endpoint not found.”, When I access the GP Web Client.

For the firewall, I already off the windows server firewall to put it out-off the equation.

Please, If you have another suggestions, I will be appreciated.

Thanks again for your reply and have a nice day.
YasserMahmoud 270 on at

Like (0)

Report

RE: GP 2013 Web Client Error

Hi Jonathan,

Thanks for your reply

When I create the cert request, I entered my Cert’s common name as server01.contoso.com, for example. So, I configured the Session Central, Session Service, and Runtime Service to use the same host name, server01.contoso.com. When I try to access GP Web Client, browser cannot solve server01.contoso.com to public IP Address, for example 88.99.11.22.

If I try to access https:// 88.99.11.22/GP, I can login as GP Web domain User but after loading session and silverlight counter, I face the mentioned error. About Cert, Browser cannot verify it, because, as you know, the common name is not the same as I registered. So, no trust between server and client. I do workaround in client windows host file, to solve the IP Address to server01.contoso.com (88.99.11.22 = server01.contoso.com), Cert verified correctly but I face the same error again.

If I do A-record in DNS, contoso.com, this will solve the issue. I already search for that and I found below link

community.spiceworks.com/.../304735-how-to-set-up-fqdn-that-is-resolvable-internally-and-externally

OR there is another way in Cert to do my scenario.

Thanks again for your help, I hope you have a nice day.
Jonathan Fear on at

Like (0)

Report

RE: GP 2013 Web Client Error

You don't want to put the IP address for the hostname as the runtime service unless the IP address is actually protected on your Cert. For example:

1. My FQDN of my computer is jonathan.microsoft.com

2. The public URL I want to have end users use is jonathanswebclient.com/gp

3. My Cert needs to protect that and that is the name I should be using when I configure the runtime service/host name during the install.

4. Now you also have to remember that if you are binding information to the Session Central and Session Service services those HAVE to be protected by the cert as well.

5. So if my server name for Session Central is say WebClientSC.microsoft.com and my Session Service machine is WebClientSS.microsoft.com then my cert has to protect both of those as well using the FQDN. If you do not specify the FQDN on the cert you would need to look at doing some A-record in DNS.
Suggested answer

Community Member on at

Like (0)

Report

RE: GP 2013 Web Client Error

Hi Yasser,

Please have the look on the below link that might helps you

community.dynamics.com/.../122693.aspx
YasserMahmoud 270 on at

Like (0)

Report

RE: GP 2013 Web Client Error

Thanks for your quick response

But I already add the certificate to both personal store and the trust root authority store in client mmc. By the way, certification is not Self Signed Certification, it is purchased from GoDaddy as SSL Standard.

When running Web Client installation, I provide the public IP, not URL, for the host name of runtime service. When I try to access GP Web client from server, I got the same error.

Severity: Critical

Summary: An error occurred while initializing communication with the server.

Details:

[HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See go.microsoft.com/fwlink
Suggested answer

Community Member on at

Like (0)

Report

RE: GP 2013 Web Client Error

Hi Yasser,

Please find the below community forum link that may fix your case

community.dynamics.com/.../252218.aspx
Suggested answer

soma 24,410 on at

Like (0)

Report

RE: GP 2013 Web Client Error

Have you installed the Silverlight applications & certifications on the client computer?

Have you installed DynamicsGPTrustedApp.msi?

If not, run the same from the web client installation path (default path is C:\Program Files\Microsoft Dynamics\GP Web Client\GPweb) on your IIS server.

Also have a look on the below links.

community.dynamics.com/.../252218.aspx

vaidymohan.com/.../gp-web-client

Hope this helps!!!