A client recently encountered an issue where the eConnect integration he was using out of SQL stopped working. He received the following error despite of several attempts to repair:
“There was no endpoint listening at net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details…”
One of the most common cause to this error is the service account. Over time or through user error on setup, these accounts can be improperly marked or configured. Sometimes Domain Administrators will also change a service account’s password without understanding the impact that may have on existing systems. Sometime passwords are not marked correctly, as they should be set to “never expire” when they are set up for use as a Dynamics GP service account. This was the issue in my case.
I had the user restart the eConnect service through Administrative Tools | Services. When he restarted, the system sent him an error that the service failed to log on as a result of bad credentials.
We quickly changed the configuration of the service account to be set to never expire and reset the password. The system restored to service and the client was able to complete the integrations without issue.
The moral of this story is when you encounter “End Pipe Not Listening” errors in eConnect for Dynamics GP, check the service and restart it. This simple check will show you the issues that are at hand 90% of the time.