1. Data Management
  2. Connectivity Studio
  3. Flows

Troubleshooting connectors
Activity Flow

When a message does not run successfully, you can troubleshoot the related source connector and target connector.

You have several options to troubleshoot a connector. You can, for example:
  • Validate the connector setup.
  • Solve a connection issue for an Azure file storage connector.
Common issues on the connector are:
  • Connection issue to folder for Azure file storage connector:
    • Test the connection. To do so, on the Connectors page, in the Action Pane, on the Development tab, click Test connection.
    • Verify the connector properties: Share, User name, Password.
    • Verify the folder setup, like Work and Archive. Do these folders exist in the file system? Are these folders defined correctly on the connector? You can use the File explorer to quickly access and view the share as defined for the Azure file storage connector. To open the File explorer, on the Connectors page, in the Action Pane, on the Development tab, click File explorer.
  • Connection issue on Database connector:
    • Test the connection. To do so, on the Connectors page, in the Action Pane, on the Development tab, click Test connection.
    • Verify the Azure Service Bus settings on the connector, in case of an ODBC connection.
    • Verify the ODBC data source settings on the connector, in case of an ODBC connection.
    • If applicable, verify the direct SQL settings on the connector. 

Application Consultant Application Consultant Start Start Validate connector setup

Validate connectivity setup

If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon   is shown. You can click the icon to show the related error messages.

You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
Key element Check
Projects When automatically checked, only the project setup is checked, and not the related setup like messages and connectors. When started manually, the full project setup is checked.
Documents The document setup is checked, including the document records setup.
Document records Only the document records setup is checked.
Messages The message setup is checked, including the data synchronization setup and message mapping.
Message - Data synchronization setup Only the data synchronization setup is checked.
Message mapping Only the message mapping is checked.
Message business events A check is done if a business event is created for the message business event. Also, a check is done if the target fields and source fields match with the related document setup.
Connectors Only the connector setup is checked.
Web services The web service setup is checked, including the data synchronization setup.
Web service - Data synchronization setup Only the data synchronization setup is checked.

In this flow, in the activity steps, as an example, the validation is done for documents.

 Do you have a  Azure file storage  connection issue? Do you have a  Azure file storage  connection issue? Solve connection issue for Azure file storage connector Solve connection issue for Azure file storage connector For an Azure file storage connector, you can connect to an Azure file share. To access the Azure file share, you can mount the Azure file share. For most connectors, when a message is run, a connection is made only for the run. After the run the connection ends. However, for an Azure file storage connection with a mounted Azure file share, the connection stays, independent of messages run. When a related message is run or the connection is tested, a check is done, and an error can occur if something has changed. For example, the connector username or password is changed. In this case, the mounted connection to the Azure file share is no longer valid. To reset the mounting, first remove the connection (see steps). The next time, a related message is run, or the connection is tested, the mounting is restored, for example with the proper username or password. Usually, messages are run in batch. If you run a message in batch, you can use a batch group to direct a batch task to another server. If a message runs on another server, the connection also stays on the other server. In case of an error or change, this connection is no longer valid. So also, the connection on the other servers must be removed. For more information, refer to: Use an Azure files share with Windows Batch processing overview Batch processing and batch servers Procedure 1. Go to Connectivity studio > Periodic > Cleanup > Remove connections. 2. In the Connector field, enter or select the connector for which you want to remove the connection. 3. Sub-task: Define batch settings. 4. Expand the Run in the background section. 5. Select Yes in the Batch processing field. 6. In the Batch group field, enter or select the batch group that is used to direct batch tasks to other servers. Note: Make sure to remove the connection from each of the available other servers to which batch tasks are directed. 7. Click OK. Notes You can only use one username and password combination to connect to an Azure Storage account. So, on all connectors that connect to the same Azure Storage account, the same username and password must be used. You can also remove the connection for a specific connector from the Connector page. To do so, on the Action Pane, on the Development tab, click Remove connections. Be careful, removing the connection. Only do so when a connection error occurs. Removing a connection can disrupt running processes in batch jobs. Another way to restore the mounting to the Azure file share is to restart the D365 FO environment. However, usually, this is not acceptable in a production environment. End End Yes No

Activities

Name Responsible Description

Validate connectivity setup

Application Consultant

If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon   is shown. You can click the icon to show the related error messages.

You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
Key element Check
Projects When automatically checked, only the project setup is checked, and not the related setup like messages and connectors. When started manually, the full project setup is checked.
Documents The document setup is checked, including the document records setup.
Document records Only the document records setup is checked.
Messages The message setup is checked, including the data synchronization setup and message mapping.
Message - Data synchronization setup Only the data synchronization setup is checked.
Message mapping Only the message mapping is checked.
Message business events A check is done if a business event is created for the message business event. Also, a check is done if the target fields and source fields match with the related document setup.
Connectors Only the connector setup is checked.
Web services The web service setup is checked, including the data synchronization setup.
Web service - Data synchronization setup Only the data synchronization setup is checked.

In this flow, in the activity steps, as an example, the validation is done for documents.

Solve connection issue for Azure file storage connector

Application Consultant

For an Azure file storage connector, you can connect to an Azure file share. To access the Azure file share, you can mount the Azure file share.

For most connectors, when a message is run, a connection is made only for the run. After the run the connection ends. However, for an Azure file storage connection with a mounted Azure file share, the connection stays, independent of messages run.
When a related message is run or the connection is tested, a check is done, and an error can occur if something has changed. For example, the connector username or password is changed. In this case, the mounted connection to the Azure file share is no longer valid. To reset the mounting, first remove the connection (see steps). The next time, a related message is run, or the connection is tested, the mounting is restored, for example with the proper username or password.
Usually, messages are run in batch. If you run a message in batch, you can use a batch group to direct a batch task to another server. If a message runs on another server, the connection also stays on the other server. In case of an error or change, this connection is no longer valid. So also, the connection on the other servers must be removed.

Activities

Name Responsible Description

Validate connectivity setup

Application Consultant

If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon   is shown. You can click the icon to show the related error messages.

You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
Key element Check
Projects When automatically checked, only the project setup is checked, and not the related setup like messages and connectors. When started manually, the full project setup is checked.
Documents The document setup is checked, including the document records setup.
Document records Only the document records setup is checked.
Messages The message setup is checked, including the data synchronization setup and message mapping.
Message - Data synchronization setup Only the data synchronization setup is checked.
Message mapping Only the message mapping is checked.
Message business events A check is done if a business event is created for the message business event. Also, a check is done if the target fields and source fields match with the related document setup.
Connectors Only the connector setup is checked.
Web services The web service setup is checked, including the data synchronization setup.
Web service - Data synchronization setup Only the data synchronization setup is checked.

In this flow, in the activity steps, as an example, the validation is done for documents.

Solve connection issue for Azure file storage connector

Application Consultant

For an Azure file storage connector, you can connect to an Azure file share. To access the Azure file share, you can mount the Azure file share.

For most connectors, when a message is run, a connection is made only for the run. After the run the connection ends. However, for an Azure file storage connection with a mounted Azure file share, the connection stays, independent of messages run.
When a related message is run or the connection is tested, a check is done, and an error can occur if something has changed. For example, the connector username or password is changed. In this case, the mounted connection to the Azure file share is no longer valid. To reset the mounting, first remove the connection (see steps). The next time, a related message is run, or the connection is tested, the mounting is restored, for example with the proper username or password.
Usually, messages are run in batch. If you run a message in batch, you can use a batch group to direct a batch task to another server. If a message runs on another server, the connection also stays on the other server. In case of an error or change, this connection is no longer valid. So also, the connection on the other servers must be removed.
Related to Notes

Message process

 		 

Solve errors - Message run

 		 

Troubleshooting connectors

 		 

See also

Provide feedback