none
BizTalk 2010 WCF Port does not receive response RRS feed

  • Question

  • Hi,

    I have setup and orchestration in BizTalk 2006 which constructs a message to send to a WCF service using the WCF-Custom port with a WS-Http binding and secured using a certificate. This works correctly, the request message is sent and the expected response message is received.

    However after having converted this to a BizTalk 2010 solution and installing in a BizTalk 2010 environment BizTalk does not appear to receive a response even though the port settings are the same and the messages being sent are the same. By no response I mean no response message, no error and not even a timeout (this includes leaving it running over the weekend.) The orchestration stays in a dehydrated state, as expected since it is waiting for a response from the request response port, and the messaging instance stays as running.

    The WCF Service is hosted outside of the network which the BizTalk servers (2010 and 2006) are running on, but the providers of the service say they are receiving traffic and sending a response and the managers for the network for the BizTalk servers can see the request and response from/to the BizTalk 2010 servers. Using Wireshark shows that there are data packets being sent and received (calling the WCF service uses a specific port), but BizTalk does not receive a response.

    Can anyone provide any suggestions of where to look to find why BizTalk 2010 is not receiving a response when the setup in BizTalk 2006 did receive a response?


    • Edited by Neil Harman Monday, April 15, 2013 2:28 PM Missed out some information
    Monday, April 15, 2013 2:27 PM

Answers

  • What kind of authentication is used by the service you are calling, if you are using certificates make sure certificates are installed in host user local certificate store.

    I would also suggest to create the port again on 2010 environment and re-configure it. If you testing this on your dev machine you can also try to call the same service using a .NET client on 2010 machine.

    • Marked as answer by Pengzhen Song Monday, April 22, 2013 10:41 AM
    Thursday, April 18, 2013 5:07 PM

All replies

  • try to change the port over which service exposed then try .

    try with IIS port 80.

    Regards

    Mohit gupta

    Monday, April 15, 2013 2:49 PM
  • Few places to check

    - Send Port Retry Configuration.

    - Any error in Event Viewer.

    - Send Port inbound message configuration

    Tuesday, April 16, 2013 3:12 AM
  • Couple things.  Just to confirm, if you put Wireshark in the middle, you see the request and responses over the wire, correct?

    There's WCF Tracing: http://msdn.microsoft.com/en-us/library/ms733025.aspx

    To quickly check if the messaging is hitting the Pipeline Manager, you can inject a simple custom component.

    Finally, is it just this one service or are all wsHttpBindings showing similar behavior?  Of it's just this one, maybe reconfigure the Port manually.

    Tuesday, April 16, 2013 8:02 PM
  • We are unable to use a different port for the WCF service as we do not have control over the service and as it is currently working on the current port with BizTalk 2006.
    Tuesday, April 16, 2013 11:20 PM
  • The send port retry is configuration is set to 0 retries as wanted to get the any error as soon as possible.

    Unfortunatley there are no entries in the Event Viewer when a request occurs.

    The send port inbound message configuartion is set to Body.

    Tuesday, April 16, 2013 11:26 PM
  • Putting wireshark in the middle we can see the BizTalk machine establish a connection to the machine hosting the WCF service and a small amount of data is sent back. Comparing the wireshark capture between BizTalk 2010 and BizTalk 2006 it is clear that the full process (establishing security, sending message, getting response) is not occuring (but connection between the servers is successful) and there should be an error, however we do not see one in the event viewer or returned into BizTalk.

    We have other ports for other orchestrations within BizTalk using the wsHttpBindings to call different WCF services and these function correctly.

    Thanks for the other suggestons we will give them a try.

    • Marked as answer by Pengzhen Song Monday, April 22, 2013 10:41 AM
    • Unmarked as answer by Pengzhen Song Monday, April 22, 2013 10:41 AM
    Tuesday, April 16, 2013 11:38 PM
  • What kind of authentication is used by the service you are calling, if you are using certificates make sure certificates are installed in host user local certificate store.

    I would also suggest to create the port again on 2010 environment and re-configure it. If you testing this on your dev machine you can also try to call the same service using a .NET client on 2010 machine.

    • Marked as answer by Pengzhen Song Monday, April 22, 2013 10:41 AM
    Thursday, April 18, 2013 5:07 PM