Monitoring stopped

Monitor, diagnose and receive alerts to problems across your SQL Servers.

Monitoring stopped

Postby SQLSlammer » Wed Apr 03, 2013 10:21 am

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?
Posts: 2
Joined: Wed Apr 03, 2013 10:11 am

Postby chriskelly » Thu Apr 04, 2013 12:43 pm

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: ... ng+stopped
Posts: 373
Joined: Mon Apr 19, 2010 12:44 pm
Location: Cambridge, UK

Postby SQLSlammer » Thu Apr 04, 2013 12:43 pm

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:
Posts: 2
Joined: Wed Apr 03, 2013 10:11 am

Return to SQL Monitor Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests