Its look like issue with <soapenv:Header/>
What I think it should have similar to this:
This might sound wierd, but I have once came across this. I tried creating the WS newly and did the mapping from a fresh and it just worked.
Thank you, but letting the external WS developer recreate the WS is not an option (for now), because via soapUI it's "proven" that the WS is fine and other departments will also be using that WS.
I tried to enable web service plug-in logging via the Server Information form and by selecting the 'Plug-In Log' checkbox:
... but when I try to the consume that WS (via Remedy ticket modify that triggers the WS filter), I do not see a SOAP envelope or any of the data that I entered in the 'arplugin.log' file.
Did I forget something?
That external WS also failed when I tried to access it from a VB.NET script... so that indicated that there was definitely something wrong with that WS!
So contacted the external WS developer and he confirmed & fixed the issue with the WS.
Make sure the WSDL you want to consume is not: SOAP-encoded arrays and SOAP-encoded structures are not supported. This means that RPC-encoded and document-encoded web services with complex