Troubleshooting Microsoft Dynamics 365 Connector 2.6 - Mule 4

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:

In Studio, right-click on the project and select Run > Run Configurations.
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:

Access Anypoint Studio and navigate to the Package Explorer view.
Open your application’s project name.
Open the src/main/resources folder.
Open the log4j2.xml file inside the folder.

Add an <AsyncLogger> tag inside the <Loggers> tag:

			<Loggers>
				...
				<AsyncLogger name="org.mule.extension.microsoftdynamics365" level="DEBUG"/>
				...
			</Loggers>

Save your application changes.
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.

Troubleshooting Microsoft Dynamics 365 Connector 2.6 - Mule 4

Enable Verbose Exception Logging

Enable Verbose Logging

Understand Commonly Thrown Exceptions

See Also