SQL Monitor 5

Reconnecting automatically after monitoring stopped

If the Configuration > Monitored servers page displays Monitoring stopped (Incorrect credentials or insufficient permissions), by default, SQL Monitor won't attempt to reconnect until you change:

  • the credentials specified in SQL Monitor, or
  • the account permissions (in this case, you need to click Retry connection on the Monitored Servers page).

You can change this setting so SQL Monitor will automatically attempt reconnection.

Configuring automatic reconnection after monitoring stopped in v4

  1. Run a text editor as administrator. To do this, right-click the program shortcut or executable (eg Notepad.exe) and select Run as administrator.
  2. In the text editor, browse to the SQL Monitor installation folder. By default, this is %ProgramData%\Red Gate\SQL Monitor

  3. Open RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config

  4. Find the reconnectAfterAuthorizationError section. This contains a setting called reconnectAfterAuthorizationError="false":

  5. Replace "false" with "true" for this setting, and save the file.
  6. Restart the Base Monitor. To do this, in the Start menu, type services.msc and press Enter. In the Services dialog, right-click SQL Monitor Base Monitor and select Restart:

The Base Monitor will attempt reconnection at increasing intervals. This prevents SQL Monitor from sending a potentially large number of failed login messages to your security log, and triggering Intrusion Detection System in the process.

After 24 hours, the Base Monitor will stop trying to reconnect automatically. After this point, you can only retry the connection manually using the SQL Monitor interface:

  1. In SQL Monitor, in the Configuration tab, go to the Monitored servers page.
  2. Under the Actions for the entity you want to reconnect, select Retry connection:

Didn't find what you were looking for?