When BizTalk Server sends request to WCF Service, The
system is able to service the request and complete the transaction
successfully. But after the successful completion of the transaction, the
following two events are logged in the BizTalk server. The orchestration, which
initiates the service request also getting completed successfully.
Log
Name: Application
Source:
BizTalk Server
Date:
18/11/2013 10:43:11 p.m.
Event
ID: 5796
Task
Category: BizTalk Server
Level:
Error
Keywords:
Classic
User:
N/A
Computer:
Description:
The
transport proxy method MoveToNextTransport() failed for adapter WCF-Custom:
Reason: "Messaging engine has no record of delivering the message to the
adapter. This could happen if MoveToNextTransport() is called multiple times
for the same message by the adapter or if it is called for a message which was
never delivered to the adapter by the messaging engine". Contact the
adapter vendor.
Log
Name: Application
Source:
BizTalk Server
Date:
18/11/2013 10:43:11 p.m.
Event
ID: 5677
Task
Category: BizTalk Server
Level:
Error
Keywords:
Classic
User:
N/A
Computer:
Description:
The
Messaging Engine encountered an error while suspending one or more messages.
The details of the service is given below
Service
-
WS-HTTP Binding
-
Reliable messaging enabled
-
Security :
o
Mode : Message
o
ClientCredentialType : Windows
Client
-
BizTalk WCF Custom adapter with WS-http
binding (BizTalk Server 2010)
-
Static two way port
-
Reliable messaging enabled
-
Security :
o
Mode : Message
o
ClientCredentialType : Windows
Every thing works fine as expected for the interface. ie the transaction is
success. After a min of the transaction completion. I am getting the errors.
01. I have not checked Propagate Fault message (as a solution provided in
another blog)
02. Its a static Port
03. I am using reliable messaging
The below error events are logged in the event viewer
Looks like the issue is BizTalk is not able to handle the reliable message properly. Its failing when it tries to close the connection after successful transaction.
I am working with Microsoft to get this sort it out currently, I will update once I have more details on this issue.