---
schema_version: "1"
id: d0dadda3e7dee16af65059388c786ba3f28123a08ac74305d65194df8cbdc60a
title: Troubleshooting Microsoft Dynamics 365 Connector 2.6
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/microsoft-dynamics-365-connector/latest/microsoft-dynamics-365-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/microsoft-dynamics-365-connector/latest/microsoft-dynamics-365-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 14fc4638e23438d1515bfe42226e1d4280c83de8b471bc7c8d6d24118dc6beba
description: MuleSoft Documentation Site
release: "2.6"
latest: true
---
---
product: Microsoft Dynamics 365 Connector
version: 2.6
is-latest-version: true
---

# Troubleshooting Microsoft Dynamics 365 Connector 2.6

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

To troubleshoot Anypoint Connector for Microsoft Dynamics 365 (Microsoft Dynamics 365 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 Microsoft Dynamics 365
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="org.mule.extension.microsoftdynamics365" 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:

- DYNAMICS:CONNECTIVITY

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

- DYNAMICS:INVALID\_PAGE\_SIZE

  The page size is invalid, for example, if the fetch size value exceeds 5000.

- DYNAMICS:NOT\_FOUND

  The server could not find the requested resource.

- DYNAMICS:OPERATION\_FAILED

  The operation fails, for example, if the protocol or entity attributes are invalid or if
  invocation fails.

- DYNAMICS:PARSE\_ERROR

  There is an error when parsing a JSON entity, for example, the entity ID is invalid or the
  encoding for the provided JSON is invalid.

- DYNAMICS:RETRY\_EXHAUSTED

  The consumer is not subscribed to any topics, and no manually assigned partitions are set to
  consume from.

- DYNAMICS:TIMEOUT

  A specific request takes longer than the configuration timeout values.

- DYNAMICS:UNAUTHORIZED

  There is an unauthorized request.

- DYNAMICS:UNKNOWN

  There is an unknown or an unexpected error.

## See Also

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

- [Microsoft Dynamics 365 Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-365-connector/latest/microsoft-dynamics-365-connector-reference)

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

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