SOAP fault: server returned a fault response

Target web service authentication failed due to invalid credentials, expired tokens, or incorrect authentication headers in the SOAP request. (high likelihood)

Invalid or malformed SOAP request payload sent to the target service, including missing required fields, incorrect data types, or schema validation failures. (high likelihood)

Target web service is temporarily unavailable, experiencing high load, or returning server-side errors due to internal processing issues. (medium likelihood)

Network connectivity issues or timeouts preventing successful communication with the target web service endpoint. (medium likelihood)

Target web service has changed its API contract, schema, or endpoint configuration without corresponding updates in ServiceNow integration. (low likelihood)

Step 1: Navigate to System Diagnostics > Log > Application Log and search for the specific SOAP fault error to examine the complete fault code and faultstring details.

Step 2: Go to System Web Services > Outbound > SOAP Message and locate the failed message record to review the request payload and response details.

Step 3: Verify the authentication credentials and headers in the SOAP message configuration by checking the HTTP headers and authentication settings in the web service record.

Step 4: Test the target web service endpoint independently using a SOAP client tool like SoapUI or Postman to confirm the service is operational and identify the correct request format.

Step 5: Compare the ServiceNow SOAP request payload with the target service's expected schema and correct any data type mismatches, missing required fields, or formatting issues.

Step 6: Check the target web service documentation for any recent changes to API endpoints, authentication methods, or request/response schemas that require updates.

Step 7: Update the ServiceNow web service configuration with corrected endpoint URLs, authentication credentials, or request formatting based on your findings.

Step 8: Test the corrected integration and monitor the System Log to confirm successful SOAP responses without fault errors.