Monitoring stopped Incorrect credentials or insufficient permissions

• 
  Hi Azhkanizkael 
  
  This looks to be an error from the MI. Sometimes this error can occur when there is some corruption detected on the database. There is a blog here that seems to have a similar issue https://sqltechblog.com/2020/04/15/its-2020-do-i-really-need-to-dbcc-checkdb/

  ATurner December 06, 2021 13:31

  - 0 +
• 
  following a dbcc checkdb on every database, all we get is this on every database:
  
  CHECKDB found 0 allocation errors and 0 consistency errors in database '<dbname>'.
  
  So it doesn't look like there's any corruption; at least at the current time. It might be a bit tricky to figure out if there somehow becomes a tiny bit of corruption at the time of disconnect.
  

  Azhkanizkael December 07, 2021 14:34

  - 0 +
• 
  One suggestion I might have:
  Would it be possible to build some sort of "auto-retry" mechanism for when this happens?
  

  Azhkanizkael December 08, 2021 16:57

  - 0 +
• 
  Got another disconnect last night, so a little over a week this time before it un-auth'd the user:
  
  
  Maybe it's something we can work around or tell it to not attempt to connect to?

  Azhkanizkael December 09, 2021 15:06

  - 0 +
• 
  Is there a possible way to tell SQL Monitor to ignore the database replicatedmaster? It's only there for a blip of time, so I can't select it from any list.

  Azhkanizkael December 28, 2021 15:47

  - 0 +
• 
  Hi Azhkanizkael
  increasing the timeout may help alleviate the issue whilst it is failing over from configuration > monitored servers edit credentials on the MI then under SQL instance edit properties

  ATurner February 01, 2022 14:57

  - 0 +
• 
  Hi Azhkanizkael
  
  Have you enabled auto retrying in SQL monitor? https://documentation.red-gate.com/sm/adding-and-managing-monitored-servers/managing-monitored-servers/reconnecting-automatically-after-monitoring-stopped

  ATurner February 16, 2022 19:45

  - 0 +

Add comment

Please sign in to leave a comment.