12-09-2023 02:40 AM
This error just started happening on a different SOAP Server Service:
"cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher"
Other Server URLS work OK
Any pointers to fix this from :LabVIEW HTTP client end?
Anthony
Solved! Go to Solution.
12-10-2023 12:45 AM
This has been resolved.
I wrote this article as a solution pointer.
https://www.linkedin.com/pulse/post-http-heders-witsml-labview-client-anthony-lukindo-xptdc/
Implementing WITSML in plain LabVIEW code using HTTP VIs requires that the following Headers are added before running the POST function which sends the SOAP request packet.
Cache-Control = private
Content-Type =text/xml
charset = utf-8
SOAPAction = http://www.witsml.org/action/120/Store.<User WMLS_FUNCTION>
Where: <User WMLS_FUNCTION>
Must be replaced with any one of the following SOAP Action requests:
WMLS_GetCap
WMLS_GetVersion
WMLS_GetFromStore
WMLS_AddToStore
WMLS_UpdateInStore
WMLS_DeleteFromStore
Including these headers before running the intended LabVIEW HTTP POST method helps to ensure proper response from WITSML AGGREGATE servers.
Mezintel has deployed LabVIEW-based WITSML 1.4.1 client to multiple WITSML service providers by including these headers before each target POST method.
Anthony Lukindo