3.1.0.125: Monitoring Stopped 1 sec - no auto restart
PDinCA
Posts: 642 Silver 1
-
Machine authentication failed at: 1 Jul 2012 12:35:25 AM
Machine authentication successful at: 1 Jul 2012 12:35:26 AM
No performance data available for this host machine or SQL Server instance in this time range.
-
Raised when monitoring stops because the user name or password you entered for SQL Monitor to connect to your host machine fails authentication. Check whether:
Your user name or password have changed. NO THEY HAVEN'T!
Your permissions have changed and are no longer sufficient. NO THEY HAVEN'T!
Once the correct credentials are entered and authentication is successful, monitoring will resume and the alert will be marked automatically as Ended. THE ALERT IS MARKED AS ENDED 1 SECOND AFTER IT WAS RAISED!
For SQL Monitor to NOT self-repair after a single 1 second break seems, sorry to use the word, LUDICROUS! I only discovered this after SQL Monitor had been NOT collecting performance data for 36 hours (server is on EDT, I'm on PDT).
PLEASE, make it fix itself!
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...
Decide wisely...
Comments
There is however a work around to get SQL Monitor to retry the connection if for some reason it encounters this error.
Edit c:\programdata\red gate\sql monitor 3\RedGate.Response.Engine.Alerting.Base.Service.exe.Settings.config
Under <configuration>, set <reconnectAfterAuthorizationError > to true
restart the Base Monitor service
Product Support
Red Gate Software
Decide wisely...
Edit c:\programdata\red gate\sql monitor 3\RedGate.Response.Engine.Alerting.Base.Service.exe.Settings.config
Under <configuration>, add <reconnectAfterAuthorizationError />
restart the Base Monitor service
Product Support
Red Gate Software
Would you be so kind as to post a sample like mine, 2 posts above, that shows the suggestion in place, please?
Decide wisely...
However, the fact that the performance data did not restart collection would point to a different issue. It may well be triggered by the authorization error, but I don't think it is caused by it. Therefore, please can you send the SQL Monitor error logs to support@red-gate.com (see doc below). Please ensure that you send the logs which cover the 1st July 2012. Can you also make sure that you include the support ticket number F0061979 in the subject line so that it comes to me.
http://www.red-gate.com/supportcenter/c ... M_LogFiles
Thanks, Chris.
Decide wisely...