- Do the following to check the Collector Manager logs:
- View /opt/APG/Collecting/Collector-Manager/microsoft-sqlserver/logs/collecting-0-0.log.
- Verify that the last message in the log states that a certain number of raw values were collected using nine SQL queries. This message indicates the collector is working.
<instance_master> collect done: 2,735 new raw values collected in 0 seconds 527 ms using 9 SQL queries
- Check for any Java exceptions and warning messages.
- If collector errors exist, do the following:
- Ping the Microsoft SQL Server using the fully qualified domain name (FQDN).
- Replace the current user, which is the username and password set during SolutionPack installation to retrieve data from the Microsoft SQL sever, with a user with SYSADMIN rights.
- Use telnet to check if the Microsoft SQL port is accessible from the SQL collector server.
- Reconfigure the SolutionPack by navigating to .
- Under SolutionPackBlock, click the pencil next to Collector to reconfigure the settings.
- To edit advanced connection settings, you may need to manually edit the SQL collector configuration file.
- If no errors exist and the last message in the log indicates that nine queries were executed, do the following:
- Wait a minimum of three polling cycles. By default, one polling cycle is fifteen minutes.
- Navigate to .
- Under the Backend category, run backend/Default/import_variable_status.task.
- Refresh the reports after fifteen minutes.
- Make sure the Frontend is attached to the database used by the SQL collector.