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:
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 Viewing performance monitor counters from a 32bit SQL install on a 64bit OS is not supported by Microsoft. As the DB install will run under %systemroot%\SysWOW64\ but the OS will run under %systemroot%\system32 when the counter dlls are loaded it does not ,by default, load the sql counter (sqlctr90.dll). A potential solution to this is to copy the sqlctr90.dll file from the SysWow64 folder and put it in the system32 folder. Although this is unsupported and can be temperamental it does enable the SQL2005 counters to be visible in the 64 bit performance monitor, after a short while you will be able to select a database within OpManager and the monitoring counters for MSSQL will start collecting data.
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 ...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 ...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 ...Creating performance monitors
Live database backup