Test connection fails on local SQL Server robot machine running Windows 2008

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

It is throwing the below error. Still, we are able to connect to DB from the other (remote) server from the same subnet but not from the server where DB is present.

Windows Server OS Version: Windows 2008

Microsoft SQL Server version: 2008 R2

---------------------------
conf_sqlserver.exe
---------------------------
Connection test to localhost failed with: Profile: test connection profile/test connection checkpoint/Connect - COM Error: Code=0x80004002 Source=(null) Description=(null) 

---------------------------
OK   
---------------------------

sqlserver: ptConn->ntauth=1, [0][][localhost][(null)] 
sqlserver: Profile: test connection profile/test connection checkpoint/Connect - COM Error: Code=0x80004002 Source=(null) Description=(null)  
sqlserver: Connect/Retrun False 
sqlserver: Connection test to localhost failed 

Environment

• Release: 20.4
• sqlserver probe GA version
• MS SQL Server is 2008 SP2/2008R2

Resolution

Customer is trying to monitor MS SQL Server locally using Windows authentication.

'Monitor Always On' is checked

UserID: <domain>\<username>

ping ip from local machine

try ip-> ##.##.##.##

Using default MS SQL Server port

Remote access to machine for monitoring - connection works fine

hostname: <hostname>

Tried FQDN as well.

hub and robot are within the same domain.

Testing, on local machine, via saving a file as .udl extension.

Opened udl file for testing connection (Data Link Properties)

 - used localhost, server name, and ip but all fail

Using Windows Authentication Integrated Security

Results:

Error generated-> SQL Server 'does not exist' or 'access denied.'

Locally on the robot / MS SQL Server database machine, using data link properties window, with Windows Authentication, (NT Integrated Security) selected, Test connection succeeded locally on the server.

Used DBA's Windows credentials and that worked.

Conclusion:

Although current sqlserver GA probe techdocs indicates/seems to imply that monitoring of the following systems are still supported, e.g., "For SQL Server versions 2005, 2008, 2012, 2014, 2016, 2017, and 2019,..."

sqlserver (SQL Server Monitoring) Release Notes

Monitoring of MS SQL Server 2008/R2 is EOS (End of Sales/Support) as per this web page. 

Note also that Microsoft support for 2008/2008R2 are deprecated and no longer supported (even extended support is over as of Jan. 2023)

Unified Infrastructure Management Products End of Sales and Support Announcements

Although 2008 is no longer supported, a potential workaround for monitoring SQL Server 2008/2008R2 is to continue to monitor the machine remotely, and/or use a pseudo-sa account for access, not Windows Authentication.

Additional Information

Techdocs has now been updated as of October 9, 2023.