Troubleshooting connectors

This topic describes the problems that you may encounter while configuring connectors.

BMC Discovery connector is not getting configured

To configure a connector, you must have administrative privileges in Automation Console. For the precise permissions, see User-roles-and-permissions.

If you still get an error in the logs, you can verify whether the user has permissions to access the API calls using Swagger. For details, see Using-REST-APIs.

Issues with the Tenable.sc connector

The following issues might occur with the Tenable.sc connector.

Vulnerabilities count mismatch

After you run the Tenable.sc connector, count of vulnerabilities that are imported in Automation Console does not match the vulnerabilities count in Tenable.sc.

Resolution

This behavior is expected as the data exported from Tenable.sc does not include all the properties. Check the response of the following API:

https://<tenable.sc server URL>/rest/analysis

Issues in importing TrueSight Server Automation properties into BMC Helix Automation Console

The user is unable to view the TSSA properties specified while configuring the TrueSight Server Automation connector in the BMC Helix Automation Console.

Check for the following messages in activity logs for the TSSA connector run:

Error message	Description
Managed Assets tags sync not initiated as no TSSA properties were provided.	If none of the TrueSight Server Automation properties are specified in the TSSA properties field.
Managed Assets tags sync not initiated as no matching TSSA properties were provided.	If the specified TrueSight Server Automation properties have typos or do not exist in TrueSight Server Automation. Workaround: Verify if the property exists in TrueSight Server Automation or check for typos in specifying the TSSA Properties.
TSSA server properties (provided on TSSA connector page), <Property name1>, <Property name2> not present on servers.	If the specified TSSA properties mentioned in error message is not found and not exists on TrueSight Server Automation or might have a typo entered in connector page. Workaround: Verify if the property exists in TrueSight Server Automation or check for typos in specifying the TSSA Properties.
Some of the TSSA server properties that you entered are not available in the TSSA server.	If the specified TSSA properties do not exist in TrueSight Server Automation or some have typos. Workaround: Verify with the BMC Support team for the missing TrueSight Server Automation properties. Alternatively, check for typos in specifying the TSSA Properties.