Hi All,

We are integrating Dynamics AX using the Biztalk adapter i Biztalk.

After a while in stable production we are getting some communication errors
while sending messages to AX:

Source Biztalk Server 2006
Event ID: 5743
The adapter failed to transmit message going to send port "XXX.YYY.xml.mdax"
with URL "ax://XXX:YYYY". It will be retransmitted after the retry interval
specified for this Send Port. Details:"An unexpected failure occurred while
processing a message. The following error has occured: Failed to write to an
IPC Port: The pipe is being closed.
".

Source: Microsoft Dynamics AX adapter
Event ID: 0
The adapter is unable to send the following message to Microsoft Dynamics AX:
MessageId: 4946d50e-e7bd-4f1d-beda-d39f211ef30a
Error: Failed to write to an IPC Port: The pipe is being closed.

The messages are retransmitted after the failure and most of the times there
is no problem accept for a few messages that are being sent twice to AX!

Two suggestions:

1, Determine that the Pipe was not being freed (using Process Explorer by
SysInternals)

2, Running Filemon to see what's causing the underlying access denied. This
should let you see exactly where the error's coming from.(Set up Filemon to
show only named pipe activity, then filter by your channel name to see only
the channel you care about).
--
Kerrey Zheng

"Tomas" wrote:

...