HOW TO: Diagnose RockSolidAgent Connection Issues

This article describes how to diagnose connection/communication issues between the RockSolidAgent and a given SQL Server instance.  The approach used in this article assumes you have already reviewed information available in the RockSolid portal, including the instance monitoring log, and also reviewed the RockSolidAgent application event log.

If you are receiving information that the instance is appearing as down to the RockSolidAgent even when the instance is up and accessible by other means, this indicates either a network issue (such as ports or firewall) or a authentication issue.  Usually these can be resolved via the RockSolid portal information, however sometimes it is beneficial to isolate the testing of the issue to allow for a more focused resolution.  To do this please obtain the RockSolidConnectionTester from your RockSolid support consultant.

The rest of this article requires the use of the RockSolidConnectionTester.

Testing Instance Communications

  • First copy the RockSolidConnectionTester.exe to the RockSolidAgent host.  This is very important to ensure you are testing from the host where the agent is running.  
  • Next right click the RockSolidConnectionTester.exe executable and select the RunAs option.  In the run as dialog please enter the user name and password of the service account domain login that is used to run the RockSolidAgent service.  This is again very important to ensure you are testing with the login the RockSolidAgent uses and not your own personal login, which may have different rights.
  •  To test the Agent to SQL Server instance communications, use the default SQL Connection tab.  Enter the SQL Server instance details below.

It is very important for the testing process that you enter the SQL instance details here in exactly the same manner as you have entered in the RockSolid instance configuration.  For example if you have only entered the instance name in the RockSolid instance config just enter the instance name here.  However if you have specified an IP and/or port number in the RockSolid instance configuration then enter the exact same details here for the test.

  • Hit the "Test Connection" button to test communications.
  • Any errors connecting to the SQL Server instance will be displayed in the error box.  If you receive errors then it will be unlikely that the agent will be able to connect until these errors are resolved.


The error message will give an indication of what is required to resolve the issue, but in general the issues typically would relate to:

  • Insufficient SQL Server login rights granted to the RockSolidAgent service account
  • The "allow remote connections" option been disabled in SQL Server (e.g. for express instances)
  • Windows firewall settings not allowing remote connections to the SQL Server ports
  • A network firewall not allowing connection through the network to the SQL Server ports


Have more questions? Submit a request


Please sign in to leave a comment.