Answered

Endpoint Not Found

(0) Share

Report

Posted on by ShaunDaws

Hi all,

Our server certificate recently expired for Web Client. We've added a new one, and I've run a Repair on Web Components to update the Web Client. I've restarted the GP Session Services and GP Session Central Service services, and have added the new certificate to the Trusted Root, and Personal folders.

Despite all this, I am getting an Endpoint Not Found error when I try to access the GP via Web Client.

I searched the Event log and found this:

An error occurred during session monitoring: 'System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://servername:48650/SessionCentralService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [2002:ac3d:145d::ac3d:145d]:48650
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
--- End of inner exception stack trace ---

Any ideas?

Thanks,

Shaun

*This post is locked for comments

I have the same question (0)

All responses (30)

Answers (1)

ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

Update:

1 year later, and the self-signed certificate expired. We created a new certificated, added it to Trusted Root, and did a Repair, and got this Endpoint Error again.

After several days we spoke to Microsoft and managed to fix it. Here are some tips for future reference, for those that encounter a similar issue:

1. Rather than doing a repair, do an uninstall/reinstall, making sure that nothing else is open (config files, services, web pages, etc) to prevent locking. If you already did this, go through and make sure that all config files, etc have been properly removed before resinstalling (check in C:\Program Files\Microsoft Dynamics\GP Web Components\)

2. We had multiple SSL-requiring sub sites on our IIS default site. We created a new, separate site for WebClient, and changed the SSL port to 444 to avoid conflicts

3. If this doesn't work, check in C:\Program Files\Microsoft Dynamics\GP Web Components\SessionService and make sure that EnableClientAccessPolicyService is set to false

Was this reply helpful? Yes No
Redbeard 12,931 on at

Like (0)

Report

RE: Endpoint Not Found

Our shared experience is similar, this is usually a certificate conflict.

Was this reply helpful? Yes No
Suggested answer

ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

Hi Jed,

Yes it turned out to be a conflict between 2 certificates for the same site. I removed all certificates from the server and recreated them, and it fixed it up. Also swearing helped a lot.

Hope this helps,

Shaun

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Endpoint Not Found

Shaun,

I'm getting the same error message. Where you able to fix this? If you did, can you please share the fix with me?

Thanks,

Jed Perlowin

Was this reply helpful? Yes No
Verified answer

ShaunDaws on at

Like (1)

Report

RE: Endpoint Not Found

For future reference, the issue appears to have been caused by us having 2 certificates relating to the same hostname/port. This was causing a conflict, possibly because we had SSRS and GP Web Client on the same box. I changed the configuration so that we only needed one certificate, then did a full reinstall of Web Client (including manually removing the GPCONFIGURATION Database).

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

YES!!!!!!!!!!! Full reinstall of Web Client after removing the database seems to have worked!

Thanks for the help guys

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

Trying a full reinstall now to see what happens

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

Tried browsing directly from IIS and I get the same message

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

RE: Endpoint Not Found

Had a look, and DynGPWebApp and DynGPWebmgmt are both running

Was this reply helpful? Yes No
KirkLivermont 5,985 on at

Like (0)

Report

RE: Endpoint Not Found

Is the application pool running?

503.0 Service unavailable. The request is sent to an application pool that is currently stopped or that is currently disabled. To resolve this issue, make sure that the destination application pool is started. The event log may give information about why the application pool is stopped or disabled.

Was this reply helpful? Yes No