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

Unable to see the connector tile on the GUI

After installing

, the Tenable.sc connector tile is not displayed on the Manage Connectors page.

Resolution

Restart the Stack Manager utility. Run the following command:

./stackmanager restart --deployment  application

Or

./stackmanager stop --deployment  application

./stackmanager start --deployment  application



Issues in importing TrueSight Server Automation properties into TrueSight Automation Console

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

The following error messages are displayed, based on the TSSA properties:

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 some of 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 some of 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 some of the specified TrueSight Server Automation properties do not exist in TrueSight Server Automation or some have typos.

Workaround: Verify with BMC Support team for the missing TrueSight Server Automation properties. Alternatively, check for typos in specifying the TSSA Properties.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*