Monitoring stopped

SQLSlammerSQLSlammer Posts: 3
edited April 4, 2013 8:43AM in SQL Monitor Previous Versions
Hi there

I am currently in the process of setting up and using SQL monitor, but I have an issue where Monitoring has been stopped because of an authentication issue.

This happens when our group policy runs and strips out local admins and readds them.

Is there anyway to get SQL monitor to retry the connection rather than just pause monitoring if it can't authenticate?


  • Options
    It is possible to get SQL Monitor to retry the connection when there is an authentication error. But this should be used carefully. If there is a different issue with the user account and this setting is enabled, then SQL Monitor will keep retrying until you stop it, or it locks the password (which can obviously cause problems anywhere else that the account is used).

    The configuration change is described here:
    https://documentation.red-gate.com/disp ... ng+stopped
  • Options
    I have changed the config file to retry the connection, like so:

    <repositorySettings slaveMode="false">
    <!-- valid databaseEngines: "Mssql"-->
    <dataStore databaseEngine="Mssql" autoUpgrade="true">
    <!-- valid versions: "Auto", "SQL2005", "SQL2008" -->
    <mssql version="Auto" connectionStringName="DataConnectionString"/>
    <collectionSettings maxTraceFileAge="00:15:00" maxTraceFileDiskUsage="1024" reconnectAfterAuthorizationError="true">
    <!-- Four schedules are available:
Sign In or Register to comment.