WSDL import failed: cannot parse web service definition

The WSDL document contains malformed XML syntax, invalid namespace declarations, or structural errors that prevent proper parsing by ServiceNow's XML parser. (high likelihood)

Network connectivity issues prevent ServiceNow from reaching the WSDL URL, including firewall restrictions, proxy configuration problems, or the remote server being unavailable. (high likelihood)

The WSDL contains unsupported WS-Policy extensions, complex schema definitions, or SOAP binding configurations that ServiceNow cannot process. (medium likelihood)

Authentication is required to access the WSDL URL but credentials are not provided or are incorrect, resulting in access denied responses. (medium likelihood)

The WSDL document exceeds ServiceNow's size limits or contains circular references and includes that create parsing loops. (low likelihood)

Step 1: Navigate to System Diagnostics > Log > Application Log and search for detailed error messages related to the WSDL import to identify specific parsing issues.

Step 2: Validate the WSDL URL by accessing it directly in a browser or using curl to confirm it returns valid XML content and check for authentication requirements.

Step 3: Use an online WSDL validator or XML validator to check the WSDL document for syntax errors, malformed XML, or structural issues.

Step 4: Check network connectivity by testing the WSDL URL from the ServiceNow instance using System Diagnostics > Network > Test Network Connection if available.

Step 5: If authentication is required, configure proper credentials in the SOAP message record or consider downloading the WSDL locally and importing it as a file.

Step 6: For complex WSDLs, try simplifying the document by removing unsupported elements or create a custom SOAP message definition instead of importing the full WSDL.

Step 7: Verify the sys_properties table for any SOAP or web service related configuration limits and adjust if necessary, particularly for document size restrictions.

Step 8: If the issue persists, enable debug logging for web services by setting the log level for com.glide.soap to Debug in System Diagnostics > Log Levels.