Troubleshooting

In Micro Focus Connect there are three main areas to review when a problem occurs during a connection run. In the UI you can refer to the Connection messages and Audit sections. The log files provide additional details. For details, see Gather debug information.

Connection messages

Connection messages provide:

  • High level details about the Connection run. The details include: Where the Connection is within an iteration cycle, how many items are visible, what actions were taken, etc.
  • General errors encountered during the run. For example, an inability to connect to data sources, failure to access a project. You can find details of the problem in the Connect.log and Connect-Err.log files. Depending on the type of error, it may result in the Connection stopping. If you have setup email notifications, you will also receive an email regarding these errors.

Back to top

Audit tab

The Audit tab provides additional insight into items that were created or updated during a Connection run.

Select a Connection, and click the Audit tab.

To display audit information:

  1. Define a filter of the information you want to display in the left pane.

    To focus on failed actions, in the Operation Type filter, select Failed Action.

  2. Click Run. The most recent activity of the Connection is displayed, broken down by iteration, project, operation type, item type, and item.

If an error occurred, the information will include the failure cause, and optionally the failure stack trace with more details. In most cases, these messages are the error that is returned by the product in the Connection, for example, Jira or ALM Octane.

Note: If you purge the database at regular intervals, the Audit tab will only show the data since the last purge. Older audit data is exported into a file by the Purge scripts, and saved in the backup folder.

Back to top

Common issues

The following section lists some issues that you may encounter.

Back to top

Issues with synchronizing ALM/QC projects

The following scenario demonstrates a typical pitfall when syncing ALM/QC projects.

If multiple ALM/QC projects use UDFs (user-defined fields) with the same name but different labels, the synchronization may fail to get the right field values.

The following example shows a uni-directional synchronization between Azure DevOps user stories to ALM requirements, where AzureDevOps, the parent, is mapped to the custom UDF in ALM/QC, AzureID.

In ALM/QC the AzureID is empty.

After clearing the watermarks and running one iteration on the connection, the audit states that the AzureID UDFs have been updated.

In ALM/QC however, the AzureID UDF was not updated, but a different UDF, Rally Milestones Data String, was updated.

Cause: The cause for this issue is the sample project in the data source. The AzureID UDF has the name RQ_USER_09 (user-09). In the project defined in the connection, the Rally Milestones Data String UDF is also named RQ_USER_09 (user-09).

Sample project user-defined fields as defined in the data source

Master ALM/QC project user-defined fields as defined in the connection

Solution: Always use a template project as the ALM/QC data source project, and ensure that the projects synchronizing on the connections use that template. For details, see Data source settings.

If this is not possible, create a separate data source for each connection.

See also: