Troubleshooting the Management Pack (Microsoft SQL Server)

Once you have finished Installing the Management Pack (Microsoft SQL Server) and Configuring the Management Pack (Microsoft SQL Server), 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

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

The following errors are possible:

Bad Microsoft SQL Server host name

Error Message: Unable to establish a valid connection to the target system. Unknown server Host name "<hostname>". Check connection settings.

Description: Ensure the host name (or IPv4 address) provided when Creating an Adapter Instance (Microsoft SQL Server) is correct.

Important: IPv6 addresses are not supported.

Bad Microsoft SQL Server user name/password

Error Message:Unable to establish a valid connection to the target system. Login failed for user "<username>". Check connection settings.

Description:Ensure the user name and password provided when Creating a Credential (Microsoft SQL Server) is correct.

Instance/Port Mismatch

Error Message: Unable to establish a valid connection to the target system. Instance on Default Port 1433 is MSSQLSERVER, does not match supplied Instance of NAMEDINSTANCE.

Description: Ensure the instance name and port are correct when Creating an Adapter Instance (Microsoft SQL Server).

Note: The default instance is MSSQLSERVER; default port is 1433.

Collection Timeout

Error Message: pollCompletionService method returned null or timed out before the result was returned with timeout set to <timeout length> seconds.

Description: The default Thread Timeout value of 30s may be insufficient for your environment. Raising it to 240s should resolve any collection issues due to this problem. Note also that raising the timeout does not cause collection to take any longer, it just gives it more time in which to complete. In addition, increasing the Thread Pool Size should help performance if you are running into collection timeout problems. You can find these parameters listed here: Creating an Adapter Instance (Microsoft SQL Server).

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/SqlServerAdapter/ 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 > Support > Logs .
2. Expand the MASTER folder, then select the COLLECTOR folder.
3. Click the Edit Properties 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.