I was recently creating an integration for a client to load some Purchase Orders into Microsoft Dynamics GP using Integration Manager. I added the source and destination adapters and then did the destination mapping. However, when I tried to run the integration I got the following error message:
DOC 1 ERROR: 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 InnterException, if present, for more details.
I was actually surprised at how detailed it was, as Integration Manager errors are usually fairly generic. This message was very specific and to the point.
The adapter I was using was an eConnect adaptor, so the first port of call was to check in Services to make sure the eConnect for Microsoft Dynamics GP 2010 Integration Services was running:
As you can see from the screenshot, above, the service was NOT running. I started the service and retried the integration and it worked without error.
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.
4 thoughts on “Integration Manager eConnect Incorrect Address Or SOAP Action”