Comments
9 comments
-
Issue dealt with as part of a duplicate logged issue on our ticketing system.
Cause was found to be with a line in the custom audit script shown in exception message screenshot.
@tomjohn please let us know if further assistance is required with Redgate Monitor. -
Hi I also have this issue in RedgateV13, any ideas?, where can I find the connection or error logs?
-
Hi @darkwarrior,
Sorry you're seeing this issue with Redgate Monitor.
Please see the following documentation for grabbing logs from Monitor:
https://documentation.red-gate.com/sm/maintaining-and-upgrading-sql-monitor/maintaining-sql-monitor/viewing-component-information-and-log-files
Are you seeing the exact same erroring as previously reported in this thread? If not containing any private information, perhaps you could provide a screenshot of the exception shown. -
Thanks Tom_C ..let me grab a screen shot and place it here..
-
Hi @darkwarrior,
Many thanks, if not an immediately obvious resolution from the provided exception/screenshot we'll look to get an internal ticket opened so we can have a look at log files/diagnose. -
Hi Tom_C, here is a screenshot,
-
Hi @darkwarrior,
This looks slightly different to the original post on this thread.
There's several reasons this could be showing in the UI. I think I'll open an internal ticket and reach out to you directly to grab your log files to clarify the cause rather than get you to post anything further here. -
Tom_C after selecting the message here is the explanation, this is a WSFC, the RPT and gendbjpv1\p as seen monitoring above, using the same credentials, I have 4 licenses, yet it says Three licenses are used up. so if I am following the logic the same failed nodes which are being monitored (licensed) needs two separate licenses? this is confusing.
-
Thanks Tom_C...see you in that portal...
Add comment
Please sign in to leave a comment.
I want to say this is something that could fix itself as I have suspended monitoring in the past and then resumed and the issue did not happen for a week or so, then the 'Monitoring Error' appeared again.
I have tried deleting the server from the monitoring and then re-adding but the issue presents itself again after a while.
Any ideas as to what I can do?