none
Problem with WCF-Custom adapter (WS HTTP Binding with reliable messaaging) - Error event logged, even though transaction completed Sucessfully RRS feed

  • Question

  • Hi All

    I am using WCF-Custom (WS HTTP Binding) with Message security as Windows and using Reliable messaging in the send port. Its a static Port. 

    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 following error

    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

    The Message Engine Encountered an error while suspending one or more Messages ( ID 5677)

    Event  ID : 5796

    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


    Should I have log this issue with Microsoft through Service request ? or is there any work around is there. Unfortunate is I cannot remove the reliable messaging from the service.


    Arun


    Tuesday, October 29, 2013 3:03 AM

All replies

  • The WCF adapters of BizTalk does not support WSRM, check the reply of Jon Flanders here ( http://social.msdn.microsoft.com/Forums/en-US/ec7afc24-1263-49ed-afad-8fa77e002dbb/biztalk-and-wsreliablemessaging?forum=biztalkgeneral )

    Also check following page (overview and architecture): https://social.technet.microsoft.com/wiki/contents/articles/13134.biztalk-wcf-adapters-and-troubleshooting.aspx


    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

    Tuesday, October 29, 2013 6:34 AM
  • Thanks for your response, I am using BizTalk Server 2010. Using WCF-Custom adapter I am able to configure and it is working fine as expected. The only worry is I am getting this exception after exactly 1 Minute

    Is this not resolved in BizTalk Server 2010 ?. Unfortunately I can not change the reliable session service of the end point.


    Arun

    Tuesday, October 29, 2013 7:52 AM
  • This also might help you to get the MoveToNextTransport() issue solved...http://rajwebjunky.blogspot.be/2011/09/biztalk-dynamic-request-response-port.html

    FYI, for a project I did the implementation of WSRM was not sufficient inside BizTalk (we just could not get it to work properly as requested). Therefor we decided to host a service in AppFabric which would handle the WSRM communication for us.
    So BizTalk forwarded the message to the AppFabric service, that service did the WSRM communication part and then forwarded the reply back to BizTalk.


    Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

    Tuesday, October 29, 2013 8:06 AM
  • Thanks for your response. Yes I have already tried that Blog. This is unfortunate to hear BizTalk is not able to handle reliable messaging :(. 

    I think the BizTalk has to safely close the reliable messaging, But I am sure the WCF-Custom is able to communicate to the WS-Reliable endpoint with a error (Which does not impact the transaction)


    Arun

    Tuesday, October 29, 2013 8:43 AM
  • Hi,

    Is there any solution to this problem?

    I am getting the same issue "The transport proxy method MoveToNextTransport() failed for adapter WCF-NetTcp: 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"

    I checked this link http://rajwebjunky.blogspot.be/2011/09/biztalk-dynamic-request-response-port.html, but in my case i am not using dynamic port.

    In my scenario, i have a number of dehydrated orchestrations that become active every Monday 6:00 AM UTC and make to calls to a WCF service, to spread out the load I have implemented a load distribution logic where orchestrations send request to service in every 1 minute (not at the same time). but still i get this error sometime.

    I have opened a ticket with MS support but thought that someone might have already found the root cause.

    Let me know if there is one.

    Thanks,

    Rahul


    Best Regards, Rahul Dubey MCTS BizTalk Server

    Tuesday, April 22, 2014 10:45 AM