integration manager - ioexception error

(0) Share

Report

Posted on by SL_GP_BC_123

1,112

My client is upgrading from GP2018 to 18.5 and uses integration manager. We have a Sales Transactions integration that uses the eConnect adapter and am having an issue where the integration hangs for about 10 minutes and then produces the following error and stalls again.

The integration never completes processing and I am unable to retrieve the full log other than what displays on screen. The eConnect adapter is installed and the service is on. The integration was migrated from our production server to a test server and upgraded to the current release. As part of that process the destination was updated to the current server. I've found a few vague messages for that type of error but no concrete resolutions. I've also tried rebooting and restarting the eConnect services. Would appreciate any advice or suggestions as to how to resolve or troubleshoot.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Derek Albaugh Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

It looks like you may be seeing this error:

DOC 1 ERROR: System.IO.IOException: The read operation failed, see inner exception. --> System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).

Usually, we see this type of error when attempting to integrate too large a volume of data in an integration and it reaches the threshold it allows and then closes the pipe causing this message to occur.

Frequently, we'll see where customers are attempting to integrate a couple of transactions, but those transactions will contain a large number of items or distributions and they don't take that into account.

Do you see smaller integrations go through while large integrations receive this error, or is it random as to which integrations seem to fail?

More often than not, with these types of cases and errors, the only 'fix' really available is to break up the integrations into smaller chunks and then run them separately, which allows them all to go through without timing out.

These two documents have related information:

social.msdn.microsoft.com/.../there-was-an-error-reading-from-the-pipe-the-pipe-has-been-ended-109-0x6d

www.eonesolutions.com/.../

Let us know...

Thanks

Was this reply helpful? Yes No