Part 3
This series narrate my personal experiences of installing Microsoft Dynamics GP 2013 Beta and the Web Client in an unsupported environment. The following installation steps are for testing purposes only and were done on a test box. If you are to test, please make sure your machine is not a production box.
"While it's not supported, it doesn't mean it won't work. It only means we haven't tested it"...
Microsoft Dynamics GP Support
In the previous installment of this series, I went through the Web Client installation steps and showed you some challenges with ASP.NET 4.5 installation on IIS 8.0 on my Windows 8 environment. Today, I will talk about some common errors I have experienced with Web Client and show how to troubleshoot these.
Troubleshooting Web Client Installation Issues
1. Unexpected Error - System.Web.HttpUnhandledException (0x80004005): There was no endpoint listening at https://fqdn:48650/SessionCentralService that could accept the message.
 |
| Unhandled Exception (0x80004005) |
Typically, this error will appear when the Session Central Service is not running on the FQDN (fully qualified domain name) server on the port being listened on. If you open the Services snap-in under Administrative Tools, you will see that the service is stopped.
 |
| Session Central Service service not running |
2. There are no remote servers available to handle the request
 |
| No remote servers available error |
This error is usually attributed to the Session Service service(s) not running on one of the session hosts.
 |
| Session Service not running |
A further look into the Session Central Service log (found under \Program Files\Microsoft Dynamics\GP Web Client\SessionCentral\Logs) would show the following trace:
Microsoft.Dynamics.GP.Web.Services.Session.Service.SessionCentralService
Error: 0 : Session Central Service was not able to successfully communicate with
the Session Service at https://fqdn:48651/SessionService. The exception details
are:
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at
https://mgb003:48651/SessionService 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 [2001:0:4137:9e76:2cce:1cb8:9cdf:4470]:48651
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 ---
If you see this error, turn on the GP Session Service and try to log in again on the Web Client. If the error persists, check to make sure the port is active - the default listening port is 48651.
3. Unexpected Error - System.Web.HttpUnhandledException (0x80004005): Process has exited during startup with code: '-532462766'.
 |
| Unhandled Exception: Process has exited during startup |
 |
| Web Client Runtime |
Of course, there are a number of things that can go wrong and these are just a few that come to mind. Damaged certificates can also be an issue and I will be covering this in my next installment, also showing some troubleshooting techniques I learned from my buddy Aaron Donat.
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
0 comments:
Post a Comment