Error "There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)." occurs on eConnect for Microsoft Dynamics GP 2018

(0) Share

Report

Posted on by Denny1986

140

Hi Experts,

One of our customer encountered the error "There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)." on calling eConnect for GP2018.

The strange thing is when customer restart the GP server and eConnect, it will not have this error for the first time. But after that, it always encountered this error.

Does anyone shed me some lights on this issue?

Thanks

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Derek Albaugh on at

Like (0)

Report

RE: Error "There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)." occurs on eConnect for Microsoft Dynamics GP 2018

This type of error is seen most commonly when running large transactions through eConnect and the volume is more than the default configuration can handle.

The following all have information related to this type of error:

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

www.eonesolutions.com/.../

In most cases, it comes down to breaking the overall transactions into smaller parts if it seems a specific integration is causing this error.

I've also seen cases where restarting the eConnect integration service would resolve the message for a matter of time, then it would come back.

My last case on it, they removed all the database roles for the service user, restarted the service and it worked moving forward, so it can be other things as well, but with eConnect more commonly, it's trying to push through too large of transactions.

Thanks

Was this reply helpful? Yes No