Troubleshooting connectors
Activity Flow
When a message does not run successfully, you can troubleshoot the related source connector and target connector.
- Validate the connector setup.
- Solve a connection issue for an Azure file storage connector.
- 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.
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 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:
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.
For more information, refer to:
|
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 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:
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.
For more information, refer to:
|
| Related to | Notes |
|---|---|
|
Message process |
|
|
Solve errors - Message run |
|
|
Troubleshooting connectors |