Comments
Sort by recent activity
Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I will need to go into services and change it back to "Automatic (delayed start). Every time Windows patches are applied to the server and it's rebooted, RGM fails to start if it's not set to delayed start. / comments
Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I ...
ThomasBE said:
TUellner said:
Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I will need to go into services and change it back to "Automatic (delayed start). Every time Windows patches are applied to the server and it's rebooted, RGM fails to start if it's not set to delayed start.
Why not create a one-line powershell script and schedule it on reboot (or daily for that matter) that checks and sets the service to delayed start if needed?
That's exactly what I just finished doing but I really do wish the setup would check and if the service already existed and was Automatic or Automatic (Delayed Start) it would leave it alone. / comments
ThomasBE said:
TUellner said:
Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the set...
Thanks David. I can confirm that works. / comments
Thanks David. I can confirm that works.
Thanks David. / comments
Thanks David.
I had the same experience as Mark. Restarted the SQL Monitor services and the other servers came back into a monitored state. / comments
I had the same experience as Mark. Restarted the SQL Monitor services and the other servers came back into a monitored state.
Alex, I installed the release and I was able to restart one of the updated SQL Servers with the MS update and SQL Monitor went right back to monitoring the server as soon as it restarted. Thanks to the development team for getting this fixed so quickly! -Tom / comments
Alex,I installed the release and I was able to restart one of the updated SQL Servers with the MS update and SQL Monitor went right back to monitoring the server as soon as it restarted. Thanks to ...
The cumulative update we had to roll back was Microsoft KB#5009557 / comments
The cumulative update we had to roll back was Microsoft KB#5009557
ATurner said:
Hi Tom I believe this to be related to a known bug. I shall let you know once there is a fix available.
Any progress on this? Adding some screen shots. As you can see, the login for this server is sysadmin so there should be no issue with master being read-only. [image] [image] [image] / comments
ATurner said:
Hi TomI believe this to be related to a known bug. I shall let you know once there is a fix available.
Any progress on this?Adding some screen shots. As you can see, the login...
ATurner - Any progress on this? I can monitor my QA instance but not my production instance. Really do need this. / comments
ATurner - Any progress on this? I can monitor my QA instance but not my production instance. Really do need this.
Thank you for checking. I look forward to the bug fix. / comments
Thank you for checking. I look forward to the bug fix.