You’re offline. This is a read only version of the page.
267
Hello,
I have a customer that has an eConnect integration into GP that failed with the following error:
Sales Order Number 31552 failed export to GP for the following reason(s):
There was an error writing to the pipe: The pipe is being closed. (232, 0xe8).
They found the following article:
They are currently on GP 2018 R2. I am not familiar with these changes so I wanted to confirm if they recommended for that error, and if they are still valid with eConnect for GP 2018.
Regards,
Kayla
*This post is locked for comments
I have the same question (0)
Hello Kayla,
It appears to be pretty much the same thing. I found a support case for Dynamics GP 2015 R2 that mentioned this exact same error, and we advised the customer to do the following:
Typically this is a time out problem. Let’s try this Add this to the following in their Microsoft.Dynamics.GP.eConnect.Service.exe.config file for the eConnect Integration service.
sendTimeout="00:10:00" receiveTimeout ="24.20:31:23.6470000" transferMode="Buffered" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"> maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
Here is another option/example Add receiveTimeout="infinite" to the Microsoft.Dynamics.GP.eConnect.Service.exe.config file for the eConnect Integration service. The binding section should resemble this:
<binding name="eConnectNamedPipeConfig" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout ="infinite" transferMode="Buffered" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"><readerQuotas maxDepth="60" maxStringContentLength="2147483647"maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /><security mode="Transport"><transport protectionLevel="EncryptAndSign" /></security> </binding>
Another item you can try is the following: Change the httpGetEnabled=”false” in the eConnect Service .config file. Here is the section:
<behaviors> <serviceBehaviors> <behavior name="eConnectServiceBehavior"> <!--Leaves this to true in order to receive Exeption information in eConnect--> <serviceDebug includeExceptionDetailInFaults="true" /> <!--This settings turns on Metadata Generation. Metadata allows for consumers to add service references in Visual Studio--> <serviceMetadata httpGetEnabled="false" httpGetUrl="localhost/.../mex"/> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel> </configuration>
Start and stop the eConnect Service and try to integrate again.
I didn't find many cases on this error nor for any GP versions newer than GP 2015 R2, but I'm thinking there hasn't been much change to eConnect between GP 2015 and GP 2016, other than changes made to the procedures for new table columns, etc.
Thanks,
Share
Report
All responses (
Answers (
