sqlserver probe cannot make a connection using Robot Service authentication method
Article ID: 132316
NIMSOFT PROBESDX Infrastructure Management
We are trying to deploy the sqlserver probe in our environment. We tested this successfully in our Dev environment, but when we rolled out to several staging systems, we cannot make a connection to localhost using the Robot Service authentication method. We have verified the Native client is installed. We are currently using v5.42-T2. Here is the error when trying to use the "Test Connection" feature.
May 15 14:31:28:552  sqlserver: Profile: test connection profile/test connection checkpoint/Connect - DB Provider: Code=0x80004005 Source=Microsoft OLE DB Provider for ODBC Drivers Description=[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. May 15 14:31:28:552  sqlserver: Profile: test connection profile/test connection checkpoint/Connect - DB Provider: Code=0x80004005 Source=Microsoft OLE DB Provider for ODBC Drivers Description=[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). May 15 14:31:28:552  sqlserver: Connection test to localhost failed Please advise.
- UIM 8.5.1 or higher - sqlserver 5.42 or higher
- Customer deployed two instances of the sqlserver probe, one on each cluster node where a Robot had already been deployed.
- When Robot Service authentication method is selected, by default, the probe automatically selects localhost as the server.
- Using raw configure, the customer had to edit the sqlserver probe on EACH instance and change localhost to point to the the SQL Server alias
- Note that the NT Authority\System account MUST be configured to have sysadmin rights.
- In another environment, the customer's DEV environment, they only had the default MS SQL Server instance being used, not separate DB instances/instance names, and different ports etc. so in that case using localhost (which is preconfigured when using Robot Service Authentication method, it worked just fine out of the box). In that same DEV environment, they already had the NT Authority\System account configured to have sysadmin rights to all of their SQL DB's. Without that set, it wouldn't have worked.
Note that Robot Service authentication will only work for sqlserver default instance, not for a named instance.