The soap servcie return respons like this,
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Policy Falsified</faultstring>
<faultactor>http://<host>:<port>/<uri></faultactor>
<detail>
<l7:policyResult status="Service Not Found. The request may have been sent to an invalid URL, or intended for an unsupported operation." xmlns:l7="http://www.example.com/ws/policy/fault"/>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Checked the request uri and the resolution path of the service, it's correct.
Checked the SOAPAction header, it's correct as well.
Release : 10.1
As per the wsdl, an element requires namespace, but in the request payload, it doesn't have any namespace.
Use soapUI or similar tool to generate a valid request template from the wsdl
soap version mismatch can also cause "service not found" error, for example, the wsdl and request are for soap 1.1, but on service property > wsdl tab> set soap version as SOAP 1.2