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

Anyone?

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report

There was an earlier post with a lot of traffic on a similar error. The issue had several possible causes.

Easiest possible - a service had not started (even though I had rebooted and the service was set to start Automatically). Looking at my services, the "GP Session Central Service" had not started, even though the "GP Session Services" had started successfully. I started it manually and the error went away. (FYI, the web client is installed on my local machine for testing.)

Easy, but not likely -The certificate was issued against the computer name and you were trying to access the site by the IP. Since the address on the certificate did not match the one on the browser there was an SSL error. If you replace the IP in the address for the computer name (Say, https://servername.local:port/gp) it should work. Confirm the name the server has on the certificate and use that. I was having the exact same issue.

What to do when all else fails...

* Uninstall the GP Web Client

* Delete the database GPWEBCLIENTSESSIONCENTRAL & GPWEBMANAGEMENT in the SQL Server

* Reinstall the GP Web Client then assign the Externally Signed Security Certificate

* Then the GP Web client works fine.

community.dynamics.com/.../105812

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

Thanks for that. Unfortunately the first 2 scenarios didn't apply, so I'm in the process of uninstalling the Web Client and removing the databases. I'll post back with results shortly.

Cheers,

Shaun

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

Argh. So I uninstalled Web Components, and deleted the databases, reinstalled the lot, but am still getting the error...

I'm wondering now if there's some sort of conflict with one of the other IIS sites on the server maybe...I'll have a look at that side of things

Was this reply helpful? Yes No
Suggested answer

KirkLivermont 5,985 on at

Like (0)

Report

Hi Shaun,

Did you already try disabling the firewall on the host server? Disabled AV?

This part of the error makes me suspect the firewall. No connection could be made because the target machine actively refused it [2002:ac3d:145d::ac3d:145d]:48650

Regards,

Kirk

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

Thanks Kirk,

I've been assured that nothing has changed with the firewall, but I've asked our sys admin to double check. It does seem suspiciously like a firewall thing though.

S

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

Like (0)

Report

Also if this is on your local network why are you connecting via ipv6?

Kirk

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

Good question...does it make a difference?

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

Like (0)

Report

I would check DNS and make sure there are both A & AAAA records registered for the FQDN of the server.

It might also be worth disabling IPv6 on the client's network adapter to test the connection and rule out IPv6 being the issue (this is a troubleshooting step but not a good permanent solution).

Sorry if this is pointing you in the wrong direction. They are some of the things I would check but networking and DNS are not my specialty.

Kirk

Was this reply helpful? Yes No
ShaunDaws on at

Like (0)

Report

So apparently ports 48650-2 are all open...I'll play with the IPv6 stuff next

Was this reply helpful? Yes No