Once you have finished Installing the Management Pack (Microsoft Azure SQL) and Configuring the Management Pack (Microsoft Azure SQL), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

  • Test Connection Errors
  • Adapter and Collector Log Files

Test Connection Errors

When Creating an Adapter Instance (Microsoft Azure SQL), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Incorrect Subscription ID

Error Message: Unable to establish a valid connection to the target system. The subscription <subscription_id> could not be found.

Incorrect Tenant ID

Error Message: Unable to establish a valid connection to the target system. No Tenant ID named <tenant_id> was found in the data store.

Incorrect Client ID

Error Message: Unable to establish a valid connection to the target system. Application with Client ID <client_id> was not found in the directory <tenant_id>.

Incorrect Secret

Error Message: Unable to establish a valid connection to the target system. Error validating credentials. Invalid client Secret is provided.

Note: See the Find your Subscription and Tenant IDs topic for assistance.

Monitor Queries set to true, but no SQL Database credentials specified

Error Message: Unable to establish a valid connection to the target system. Query Collection is turned on, but SQL Database credentials were not provided.

Description: When Creating a Credential (Microsoft Azure SQL), ensure you have selected the Azure Subscription & SQL Database Credential credential kind, and enter your SQL Database user name and password.

Unable to validate the SSL certificate

Error Message: Unable to establish a valid connection to the target system. Unable to validate the SSL Certificate for Microsoft Azure, but the certificate appears to be in the vRealize truststore. You may need to restart the vRealize Collector for the change to take effect.

Description:Customers who installed the vROps Azure Management Pack version 6.3.10100015 or earlier received an SSL certificate that is no longer valid. Installing version 6.3.10100016 or higher provided the valid certificate; however, if the invalid certificate is still installed, it can cause the error above.

Steps to Correct: To clear the invalid certificate from the truststore, perform the following steps:

  1. Obtain the truststore password (named ssltruststorePassword) from the following file: /storage/vcops/user/conf/ssl/storePass.properties. Copy the password for use in the next step.

  2. Run the following command from the /storage/vcops/user/conf/ssl/ folder:

    keytool -delete -alias azure -keystore tcserver.truststore

    You will be asked to input the password from step 1.

  3. Click Test Connection for the adapter instance again, and accept the new certificate.

SSL Handshake Exception: General SSL engine problem

Error Message: Unable to establish a valid connection to the target system. javax.net.ssl.SSLHandshakeException: General SSLEngine problem.

Description: This error relates to a known issue with the truststore in vROps 6.4+. The error prompt to restart the vRealize Collector is currently the suggested corrective action.

Adapter and Collector Log Files

You can review adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

  • Adapter log files are located in the $VCOPS_BASE/user/log/adapters/MicrosoftAzureAdapter/ folder.
  • Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

  1. Navigate to Administration > Logs.
  2. Expand the MASTER folder, then select the COLLECTOR folder.
  3. Click the Edit Properties configure_icon icon.
  4. In the Root logger level drop-down menu, select the desired option.
  • The default logging level is warning.
  • To troubleshoot issues, set the logging level to info.
  • To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.
Caution: If you set the logging level to debug , log files can become large very quickly. Set the logging level to debug only for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.