Web Client

(0) Share

Report

Posted on by Julio Ramos

Hi, I finished installing the Web client on the server and when I access it starts charging the screen tells me the following

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.30514.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

Any help.

*This post is locked for comments

All responses (7)

Answers (0)

Jonathan Fear on at

Like (0)

Report

RE: Web Client

Reinstalling resolved the issue Julio? If so please mark the post as the answer.
Julio Ramos on at

Like (0)

Report

RE: Web Client

I`m Reinstall and very good

Thenks.
Jonathan Fear on at

Like (0)

Report

RE: Web Client

Did you bind a cert to the Session host and Session Central service? If so that could be the problem (typically if they are on different machines). There really is no need to bind a cert to these services as there is already a layer of encryption for traffic between these two services.

We really need to know how this is setup. How many servers? Internal or External? what was used during the install for each service (host name)?
Julio Ramos on at

Like (0)

Report

RE: Web Client

Yes, everyone is running
Tom Cruse 1,477 on at

Like (0)

Report

RE: Web Client

Are the sites, App Pools and Services all up and running?
Julio Ramos on at

Like (0)

Report

RE: Web Client

Yes, the certificate is fine. I've done this procedure your comments.

In both shows me the same error on Clients and Server
Suggested answer

Tom Cruse 1,477 on at

Like (0)

Report

RE: Web Client

Are you receiving the this error on both the client workstation and the webserver?

It might be a cert issue if you're able to access the site on the webserver but not the client workstation.

I ran across a lot of issues when setting up the WebClient and they all pertained to the self-signed cert I created. It had to be installed on the client machine in the Trusted Root Authority location for it to work.