How to resolve eConnect API Timeout Errors

When creating an integration to Dynamics GP, you might encounter errors returned at some point in the process such as eConnect API Timeout Errors. Finding a solution can be overwhelming and time-consuming. So in this blog post, we will go over how we resolved them.

Recently there was a requirement from one of our client to develop an integration to integrate Sales Orders into Dynamics GP. For the requirement, a .NET AddIn leveraging eConnect was developed. The .Net AddIn uses the eConnect serialization classes to construct an eConnect XML document and then uses eConnectMethods class to create the transaction into Dynamics GP.

All was good until we faced an eConnect exception. The exception thrown by eConnect was “There was an error writing to the pipe: The pipe is being closed.”  The exception is due to the eConnect call getting timeout.

In order to resolve the above issue, we need to modify the configuration file for eConnect services to specify the timeout. By default when eConnect is installed there will not be any timeout specified in the configuration file.

Add receiveTimeout="infinite" to the Microsoft.Dynamics.GP. eConnect.Service.exe.config file for the eConnect Integration service. The binding section should resemble like this.

Once the service configuration file is changed, restart the eConnect Integration services and you are good to go.

That’s all for now. See you again in another interesting blog post.

Happy Developing...

This article addresses a solution for the eConnect API Timeout Errors in Dynamics GP. If you are experiencing a different related error, please feel free to reach out to us by filling out the form below.