Routing Failure Exception on SOAP and WCF Receive Locations
While you publish your Schema or Orchestration as a Webservis, You may have routing exception which is one of the many other exceptions most probably you will have 
A message received by adapter “SOAP” on receive location “WebService_WSUpload/WSUpload” with URI “/WSUpload/WSUpload.asmx” is suspended.
Some problems that can cause this problem:
- The destination orchestration or send port is not enlisted, as specified in the error. Generally the solution is not that simple
- You are using the pass-thru pipeline which does not promote the message type and the orchestration binding fails. You should use XmlDisassembler pipeline
- If you create an Orchestration to consume the messages published by the auto-generated SOAP ReceivePort. The important thing to note here is the name of the “Operation” you define inside the logical port, make sure it matches the WebMethod name you have specified while generating the web-service.
You can also check the active subscriptions on the Group Hub page of the Biztalk Admin Console and you can see the orchestration which is filtering messages according to method name.
New Query -> Search for -> Subscriptions.
I also put some other useful links that may help while you are publishing your schemas or orchestrations as a web service.
Related posts:
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
