Customer is unable to connect to monitored host SQL Server server in the database discovery process.
Received "Database Connection Failed" errors.
Network error IO Exception: Connection refused
[SQL SERVER Error Code = 0. SQL State : 08S01]
or
Failed to establish a SQL-Server JDBC connection protocol to Host [MYHOSTNAME\DEFAULT_INSTANCE], user account [MYDOMAIN\MYUSER] . Reason : [[Foglight][SQLServer JDBC Driver]Error establishing socket to host and port: MYHOSTNAME:2033. Reason: Connection timed out: connect- Profile:MSSQLProfile{host='MYHOSTNAME', instance= 'DEFAULT_INSTANCE', username='MYDOMAIN\MYUSER', authType= 'WINDOWS_CUSTOM', port= '2033' useNTLMv2= 'true', socketTimeout= '900', secureConnection= 'OFF' }]. . [SQL-Server Error Code = 0. SQL state : 08001]
CAUSE 1
Incorrect port was used in the database agent installer.
CAUSE 2
Firewall is blocking the port between the Foglight Agent Manager and the monitored host
CAUSE 3
Incorrect remote server hostname or IP address was used in the database agent installer.
CAUSE 3
DB user Credentials entered are invalid.
Check that the Windows Authentication Credentials were entered in the DOMAIN\USER format.
Ensure that the Windows Authentication Credentials entered are trusted and exist in the Database Logins.
CAUSE 4
Windows Authentication Credentials entered are not trusted or do not exist in the Database Logins.
CAUSE 5
SQL Server Windows service is running.
CAUSE 6
SQL Server is not configured to use TCP/IP
CAUSE 7
The SQL Server Browser Service is not running. This is required to discover SQL Server instances using dynamic ports.
RESOLUTION 1
Specify the correct port number when defining the new agent properties so the database agent can be created to monitor the SQL Server instance.
RESOLUTION 2
Ensure that the SQL Server port is open and accessible from the Agent Manager server.
A Telnet test can be used to test the connection between the FglAM and the host.
TELNET MYHOSTNAME PORTNUMBER
for example TELNET DBSERVER123 1433
Please refer to KB 238273 for alternatives to using a Telnet test to confirm connection and port opening.
RESOLUTION 3
Ensure that the Windows Authentication Credentials entered are trusted and exist in the Database Logins.
RESOLUTION 4
Ensure that the Windows Authentication Credentials entered are trusted and exist in the Database Logins.
RESOLUTION 5
Activate the SQL Server database service on the monitored host.
RESOLUTION 6
RESOLUTION 7
Enable the SQL Server Browser Service to discovery SQL instances that use dynamic ports.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center