---
schema_version: "1"
id: ceea01f45c45e3c455e95379989ba6b09e4a3403f75f74d46b0f44de48512447
title: Troubleshooting ServiceNow Connector 6.17
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/servicenow-connector/6.17/servicenow-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/servicenow-connector/6.17/servicenow-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: de80dd9c1c597be603fa79da4f6e94075fd567b27d5dccb3187ce5b17365cb35
description: MuleSoft Documentation Site
release: "6.17"
latest: false
---
---
product: ServiceNow Connector
version: 6.17
---

# Troubleshooting ServiceNow Connector 6.17

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Anypoint Connector for ServiceNow (ServiceNow Connector), become familiar with the
information about interpreting commonly thrown exception messages.

## Enable Verbose Exception Logging

Enable verbose exception logs to show a complete stack trace of the error instead of the default
truncated output:

1.  In Studio, right-click on the project and select **Run > Run Configurations**.

2.  Go to the **Arguments** tab and append the arguments in the **VM arguments** section to add the
    `mule.verbose.exceptions` property. For example:

    `-XX:PermSize=128M -XX:MaxPermSize=256M -Dmule.verbose.exceptions=true`

## Enable Verbose Logging

To get a better understanding of why an application’s interaction with ServiceNow Connector is
failing, temporarily enable verbose logging for the connector.

Remember to always disable enhanced verbosity after troubleshooting, because it can affect your Mule
application’s performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name="com.mulesoft.connectors.servicenow" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Understand Commonly Thrown Exceptions

Here is a list of commonly thrown exception messages and how to interpret them:

- SERVICENOW:BAD\_REQUEST

  The request is incorrect, for example, there are invalid input headers or the service does not
  exist.

- SERVICENOW:CANNOT\_DISPATCH

  An error occurs when sending the request.

- SERVICENOW:CONNECTIVITY

  Either a connection could not be established or there is a connectivity error.

- SERVICENOW:ENCODING

  There is an encoding error when parsing the request or the response.

- SERVICENOW:INVALID\_WSDL

  The WSDL is invalid or inconsistent.

- SERVICENOW:PROCESSING\_ERROR

  There is a processing error, for example, there is an interruption during initialization.

- SERVICENOW:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

- SERVICENOW:SOAP\_FAULT

  There is a SOAP fault error.

- SERVICENOW:TIMEOUT

  A specific request takes longer than the configuration timeout values.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [ServiceNow Connector Reference](https://docs.mulesoft.com/servicenow-connector/6.17/servicenow-reference)

- [Salesforce Help](https://help.salesforce.com)

- [Known Issues](https://help.salesforce.com/s/issues)