Comments
Sort by recent activity
Evan, could you help me out on another registry entry?
Error: Status: Monitoring stopped (Incorrect credentials or insufficient permissions)
Date: 12 May 2014 5:45 PM
Group: Registry
Event: OpenSubKeyOrNone: \\<my_machine_02>\HKEY_LOCAL_MACHINE\Cluster
Outcome: Incorrect credentials or insufficient permissions
Exception: Win32Exception
Exception message: Access is denied
the problem is: the account used is local administrator, and such "Cluster" key/value does not exist in the registry hive listed. This is a standalone w2008 server that should not have anything labeled "cluster" on it.
ty / comments
Evan, could you help me out on another registry entry?
Error: Status: Monitoring stopped (Incorrect credentials or insufficient permissions)
Date: 12 May 2014 5:45 PM
Group: Registry
Event: OpenSub...
yes, I was referring to the "#fsG" (and any other code too). / comments
yes, I was referring to the "#fsG" (and any other code too).
thanks for your detailed explanation, Evan.
I tried to do a search about the error before posting here, but could not find an index of messages/codes. do you guys have anything like that to help us?
regards, / comments
thanks for your detailed explanation, Evan.
I tried to do a search about the error before posting here, but could not find an index of messages/codes. do you guys have anything like that to help us...
So, back I am.
Unfortunately I was not able to duplicate the conditions that caused the first error ("missing dbo schema"), because I had to configure my SQLMonitor Hosted acct with a different server.
But I am still facing some errors that are preventing the monitoring, and in my understanding they should only generate alerts. This happens when I have a database marked as Read-Only (or a Snapshot) and the login used to collect the data is not given SA rights.
In this scenario, the monitor will try to connect to the unavailable database, fail, and stop monitoring. I believe it should only fail the connection and generate an alert, continuing monitoring the other databases.
"Configuration > Monitored servers > Show Log (for a specific instance)"
Date: 5 May 2014 4:46 PM
Group: SQL
Event: #LVG
Outcome: Incorrect credentials or insufficient permissions
Exception: SqlException
Exception message: The server principal "<my_login>" is not able to access the database "<my_snapshot>" under the current security context.
The only workaround I found was to mark the database as writable, create the monitoring login, and mark it as read-only again - or just drop the snapshot in this case. / comments
So, back I am.
Unfortunately I was not able to duplicate the conditions that caused the first error ("missing dbo schema"), because I had to configure my SQLMonitor Hosted acct with a different ser...
hi Fiona.
unfortunately I was not able to resolve this yet. I need to assing the minimum possible privilege to the acct that will collect the data, and could not test other options until now.
I believe this error happens when some databases are marked as "offline" on SQL Server. It would be nice to have a report on these, but this should not stop monitoring.
i will test it again and come back to you later.
thanks / comments
hi Fiona.
unfortunately I was not able to resolve this yet. I need to assing the minimum possible privilege to the acct that will collect the data, and could not test other options until now.
I bel...
UP!
no word on port numbers? does anyone have experience with such restricted/firewalled environments?
regards / comments
UP!
no word on port numbers? does anyone have experience with such restricted/firewalled environments?
regards
hi Fiona. I got the relay to talk with the web server of the SQL Monitor Hosted service.
Also my firewall team was able to open a bunch of ports on the internal network, but we could not get the server to use a fixed port for wmi.
Is it possible to monitor only SQL events and ignore all data captured via WMI in some way?
PS: ports opened both ways:
TCP 139
TCP 445
TCP 135
TCP 137
TCP 24158
UDP 137 / comments
hi Fiona. I got the relay to talk with the web server of the SQL Monitor Hosted service.
Also my firewall team was able to open a bunch of ports on the internal network, but we could not get the se...
I believe SQL Monitor does not compare to Profiler.
Profiler is really hard on the server, because it will keep track of *everything* that it logged. SQL Monitor will only poll the server every few seconds to request the information it will store. / comments
I believe SQL Monitor does not compare to Profiler.
Profiler is really hard on the server, because it will keep track of *everything* that it logged. SQL Monitor will only poll the server every few...
the same happens on the hosted beta of SQL Monitor: it tries to create "permanent" tables in TempDB. / comments
the same happens on the hosted beta of SQL Monitor: it tries to create "permanent" tables in TempDB.
Hello. I'm a new user to RedGate tools, and the first one I'll test is the SQL Monitor.
Currently we have 2 domains on my work network, so I was searching the forums for similar setups in order to know what to do.
Do the support team has any news regarding this kind of environment? Is this supported on SQL Monitor 3.5 by now?
I have not yet installed the services, but will do it soon and this information will be important.
regards, / comments
Hello. I'm a new user to RedGate tools, and the first one I'll test is the SQL Monitor.
Currently we have 2 domains on my work network, so I was searching the forums for similar setups in order to ...