Not able to see databases while adding MSSQL monitors in OpManager
Issue/Scenario:
When I try to add the application monitor, I get to the stage to add databases there are none to be selected.
This issue could occur if the SQL servers WMI agent is not responding to the WMI request which results "null" i.e the WMI repository does not contain any SQL information which results in null.
Solution/Workaround:
Step 1:
1. Go to the monitored device.
2. Click Start-->Run,
For Windows 2000 winmgmt /resyncperf' command.
For Windows XP, 2008 and 2003 etc, use 'wmiadap /f' command.
3. After running this command about 4 times, wait for an hour and check for the same.
Step2:
1. Go to the monitored device.
2. Click Start-->Run-->services.msc
3. Restart WMI service & MSSQL services.
Ifissue persist, send us the Support InformationFile(Support-->Support Information File) along with the followingqueries executed.
1. From command prompt go to <OpManager\conf\application\scripts>
2. Execute the following command :
\scripts>cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT CacheUseCountsPersec from Win32_PerfRawData_MSSQLSERVER_SQLServerCacheManager"
\scripts>cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT UserConnections from Win32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics"
Example:
cscriptwmiget.vbs rex.india.adv adventnet\rex 1223123 "ROOT\CIMV2" "SELECTUserConnections fromWin32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics"
If the above query does not show any databases , use WMI Diagnostic Utility to Diagnosing and Repairing Problems with the WMI Service
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx
When I try to add the application monitor, I get to the stage to add databases there are none to be selected.
This issue could occur if the SQL servers WMI agent is not responding to the WMI request which results "null" i.e the WMI repository does not contain any SQL information which results in null.
Solution/Workaround:
Step 1:
1. Go to the monitored device.
2. Click Start-->Run,
For Windows 2000 winmgmt /resyncperf' command.
For Windows XP, 2008 and 2003 etc, use 'wmiadap /f' command.
3. After running this command about 4 times, wait for an hour and check for the same.
Step2:
1. Go to the monitored device.
2. Click Start-->Run-->services.msc
3. Restart WMI service & MSSQL services.
Ifissue persist, send us the Support InformationFile(Support-->Support Information File) along with the followingqueries executed.
1. From command prompt go to <OpManager\conf\application\scripts>
2. Execute the following command :
\scripts>cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT CacheUseCountsPersec from Win32_PerfRawData_MSSQLSERVER_SQLServerCacheManager"
\scripts>cscript wmiget.vbs devicename domainname\username password "ROOT\CIMV2" "SELECT UserConnections from Win32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics"
Example:
cscriptwmiget.vbs rex.india.adv adventnet\rex 1223123 "ROOT\CIMV2" "SELECTUserConnections fromWin32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics"
If the above query does not show any databases , use WMI Diagnostic Utility to Diagnosing and Repairing Problems with the WMI Service
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx
New to ADSelfService Plus?
Related Articles
MSSQL Monitors not working - Shows N/A in OpManager
This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers). 2)Required Monitors are not associated to the device in OpManager. 3)WMI might not be responding ...No Database listed while adding MSSQL Monitors
Issue/Scenario: When I try to add MSSQL performance Monitors, I get to the stage to add databases but there were no databases listed . This issue could occur if 32bit MSSQL is installed on a 64bit Widows2008 R2. Solution/Workaround: Apparently ...AD Monitors Shows N/A in OpManager
This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers). 2)Required Monitors are not associated to the device in OpManager. 3)WMI might not be responding to ...OpManager Enterprise installation procedure for central and probe on a Windows server (MSSQL)
OpManager DB migration from PGSQL to MSSQL on the same server in Version 12.3
Please follow the below mentioned steps to migrate DB from PGSQL to MSSQL on the same server. These steps are applicable only on builds 12.3.045 and above. If you are in older versions below 12.3.045, please upgrade to 12.3.045 and follow these ...