When using SOAPUI to call a BizTalk published ochestration or schema, you might get this error response/XML from SOAP-UI:
The message could not be processed. This is most likely because
the action ‘http://Neal.Temp.WCFTargetNamespace/Outbound214Service/Send214Request’
is incorrect or because the message contains an invalid or expired security context token or because
there is a mismatch between bindings. The security context token would be invalid if the service aborted
the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase
the Receive timeout on the service endpoint’s binding
Assuming no security is needed when first testing on your local machine. You can tighten up the security after you get the basic test working.
- Modify the web.config file of the published webservice and set the authentication mode to “None”.
- Modify the BizTalk Receive Location created by the WCF publish utility, on the Security tab, set the “Security mode” to none.
- In SOAP-UI, click on the WS-A words (tab) below your request xml message. Set the options as shown below:
Filed under: WCF