eConnect 2010 Error: There was an error writing to the pipe: The pipe is being closed

When you run an eConnect 2010 integration, it may display this error when the code calls CreateTransactionEntity:


I recall seeing this a while ago in some testing, but I didn't think much of it at the time.  Well, it cropped up again, this time on both my development server and the client's workstation for a GL JE integration.

The quick fix to this is to close the integration and relaunch it, and it will then import fine.

Fortunately, there is a publicly accessible KB article available that describes the issue and the resolution.

http://support.microsoft.com/kb/2539263

I'm not a WCF expert, but it seems odd that this is happening since my code is re-instantiating the eConnect objects each time it is run, so it isn't as if my code is somehow hanging on to an idle instance of eConnect--at least not explicitly.  What is also odd is that I've developed dozens of integrations, but haven't had to deal with this error before.  I'm pretty sure this isn't the first customer that has left the integration open for more than 10 minutes, so it could be that the error does not occur for some integrations.

Fortunately, the fix described in the KB article is very simple, and should resolve the issue permanently.  Just add the receiveTimeout="infinite" parameter to the eConnect service config file and restart the service.


The eConnect service config file is located at:


C:\Program Files\Microsoft Dynamics\eConnect 11.0\Service




Steve Endow is a Dynamics GP Certified Trainer and Dynamics GP Certified IT Professional in Los Angeles.  He is also the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.

http://www.precipioservices.com