Troubleshooting the sensor

Problems with the sensor might include unsuccessful authorization or discovery, and so on. However, you can recover from these problems.

Fix Pack 2

The script-based discovery of the Microsoft SQL Server sensor fails

Problem
When you run the Microsoft SQL Server sensor in the script-based mode, the discovery fails with the following message:
There was an error while Snapins adding...
Solution
Verify that the sqlps module of Windows PowerShell is installed correctly. The script-based discovery mode of the Microsoft SQL Server sensor relies on this module. However, the module is available only in Microsoft SQL Server 2008, and later. Therefore, if you want to discover Microsoft SQL Server 2005, you must have other instances like Microsoft SQL Server 2008, 2008 R2, or 2012 installed as well.

No details available for SQL Server after discovery

Problem
SQL Server is discovered but there are no details provided.
Solution
Check that the SQL Server authorization has access to the following tables:
  • sysdatabases
  • sys.master_files
  • syscurconfigs
  • sysprocesses
If an SQL Server authorization is not used, check the Windows authorization.

Microsoft SQL discovery without datareader authority

Problem
Is it possible to discover a Microsoft SQL database without having to grant the required db_datareader role to the entire database.
Solution
To discover a Microsoft SQL database, without having to grant authority to the entire database, use the following steps:
  • Create a user using the storage procedure from the SQL Server.
  • Use the sp_addlogin command to create a login that allows users to connect to the SQL Server using SQL Server authentication.
  • Use the sp_grantlogin command to allow a Windows user account or group to connect to the SQL Server using Windows authentication.
  • After the user is created, grant access to the following tables which are used by SQL server sensor:
    sysdatabases, sys.master_files, syscurconfigs, sysprocesses
    In the following example the user is taddmusr:
    GRANT SELECT on sysdatabases to taddmusr;
GRANT SELECT on sys.master_files to taddmusr;
GRANT SELECT on syscurconfigs to taddmusr;
GRANT SELECT on sysprocesses to taddmusr;

ProductName attribute is not clear

Problem
The ProductName attribute does not present enough information about the product.
Solution
If you recently migrated from the previous TADDM version, you must rediscover the Microsoft SQL Servers. The attribute includes the SQL Server version number, the ServicePack level, and the SQL Server edition.
The ProductName attribute has the following form:
  • Microsoft SQL Server 2008 R2 SP1 (Enterprise Edition)