Comments
Sort by recent activity
Hi nhartman,
We've seen this before. It's usually a problem with the NetBIOS/WINS name resolution rather than DNS. We're not sure what causes it but we've generally seen it on Windows 7 machines. Which OS are you using?
Restart the following services on the machine that is running the SQL Monitor base service.
Server
TCP/IP NetBIOS Helper
Netlogon
Windows Management Instrumentation
Let me know if you are still seeing the issue.
--
Daniel / comments
Hi nhartman,
We've seen this before. It's usually a problem with the NetBIOS/WINS name resolution rather than DNS. We're not sure what causes it but we've generally seen it on Windows 7 machines. W...
Although many people found the "Job did not start" alert useful we had many customers with a large number of false positive alerts.
After researching into the cause of these issue and talking to Microsoft about the SQL Server Agent scheduler we were not confident that we could predict when jobs would run correctly. Specifically some reoccurring jobs did not appear to run in a deterministically scheduled way.
We did not feel that the alert meet the minimum functional quality for us to include it in SQL Monitor so we unfortunately had to withdraw it.
--
Daniel / comments
Although many people found the "Job did not start" alert useful we had many customers with a large number of false positive alerts.
After researching into the cause of these issue and talking to Mi...
We've done quite a bit of research into this problem and unfortuntally the root cause is a bug in the WMI Provider in Windows when running as a failover cluster.
For some reason, remote WMI access is being refused even though we are using the correct encryption settings. We've also checked that the issue occurs when using WBEMTEST.
The following is deeply unsupported by Microsoft, but gets around the issue:
• Open a UACed command prompt
• Change the directory to %windir%\System32\Wbem
• Run “notepadâ€
• Open ClusWMI.mof
• Change [RequiresEncryption] to [RequiresEncryption(FALSE)]
• Run “Mofcomp.exe ClusWMI.mofâ€
• Retry the WMI Query using Wbemtest to see if this fixes the error logging issue.
I strongly suggest you take this issue up with Microsoft.
--
Daniel Kenyon-Jones
Software Engineer - DBA Tools
Red Gate Software Ltd / comments
We've done quite a bit of research into this problem and unfortuntally the root cause is a bug in the WMI Provider in Windows when running as a failover cluster.
For some reason, remote WMI access ...
Hi,
Please try the following steps:
Open C:\ProgramData\Microsoft\Crypto\RSA or C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA in windows explorer
Right click on "MachineKeys" to bring up the properties dialog
Click on the Security tab
Remove all users except "Everyone" and "Administrators"
Edit the permissions for "Everyone" to Allow everything except Full Conrol
Click OK
Restart the Response Services
If the error still shows, repeat steps, but set "Everyone" to allow "Full control" / comments
Hi,
Please try the following steps:
Open C:\ProgramData\Microsoft\Crypto\RSA or C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA in windows explorer
Right click on "Machine...
The instance offline alert indicates that either the service stopped or that there was some sort of connectivity issue between the instance and the base monitor. Given that one of your users experienced a connectivity issue at the same time as one of the alerts was raised and the instance didn't restart or fail over I would suggest that some sort of connectivity issue was experienced on your network.
This could have been caused by many things eg: a peek in network traffic increasing latency or causing packet loss, a switch or router dropping traffic, etc...
None of these would have left any trace in the SQL Server log files.
I have inspected the SQL Monitor log files and can't find anything which would indicate a false positive alert.
Regards,
--
Daniel / comments
The instance offline alert indicates that either the service stopped or that there was some sort of connectivity issue between the instance and the base monitor. Given that one of your users experi...
Hi Jim,
Running diagnostics using 3rd party tool enables us to differentiate between problems with SQL Monitor and problems and configuration issues with your windows environment.
SQL Monitor provides fairly detailed error messages on these issue, but sometimes it is unclear what is causing the issue.
On top of this, some windows APIs seem to have transitory issues associated with them.
Let me know if you'd like any further detail.
--
Daniel / comments
Hi Jim,
Running diagnostics using 3rd party tool enables us to differentiate between problems with SQL Monitor and problems and configuration issues with your windows environment.
SQL Monitor provi...
Hi Janhoran,
Does this happen when you first connect or does it happen after some time?
Does clicking the retry option on the cog icon in the Monitored servers configuration page fix this?
Cheers,
--
Daniel / comments
Hi Janhoran,
Does this happen when you first connect or does it happen after some time?
Does clicking the retry option on the cog icon in the Monitored servers configuration page fix this?
Cheers,
...
Hi,
SQL Monitor 2 was release in early November, so the April toolbelt will not include SQL Monitor.
Toolbelt can be downloaded from the Red Gate Upgrade Center: https://www.red-gate.com/Dynamic/UpgradeCenter/SerialNumberEntry.aspx / comments
Hi,
SQL Monitor 2 was release in early November, so the April toolbelt will not include SQL Monitor.
Toolbelt can be downloaded from the Red Gate Upgrade Center: https://www.red-gate.com/Dynamic/Up...
Hi Js
This is a known issue. It has been fixed in version 2.1 which should be released in the next week or so.
Cheers,
--
Daniel / comments
Hi Js
This is a known issue. It has been fixed in version 2.1 which should be released in the next week or so.
Cheers,
--
Daniel
Unfortunately we are at the mercy of Microsoft on this one. As we don't install a monitoring agent on the SQL Server we have to use the APIs that are available on Windows.
We've had quite a few reports that domain admins and groups don't seem to satisfy the access requirements for WMI and Remote Registry connections but we've not come up with a way of enabling this.
If anyone has any joy with this, please let us know.
hbuckner: what specific error were you seeing when using an AD Group?
--
Daniel / comments
Unfortunately we are at the mercy of Microsoft on this one. As we don't install a monitoring agent on the SQL Server we have to use the APIs that are available on Windows.
We've had quite a few rep...