status=MUTED, label=QC server is muted due to unrecoverable error – Error establishing socket to host and port: xxxxx:1450. Reason: Connection timed out: connect
« Back
Tags:
Question ID: 108619
▲
0
▼
♥ 0

Hi – we are getting the following error on our server.

Server on ‘ALM01’ has entered an unstable state, please contact your site administrator.

status=MUTED, label=QC server is muted due to unrecoverable error,
StackTrace=
java.sql.SQLNonTransientConnectionException: [Mercury][SQLServer JDBC Driver]Error establishing socket to host and port: ALMDB_TEST:1450. Reason: Connection timed out: connect
at com.mercury.jdbc.sqlserverbase.dda4.b(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda4.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda3.b(Unknown Source)
at com.mercury.jdbc.sqlserverbase.dda3.a(Unknown Source)
at com.mercury.jdbc.sqlserver.tds.ddc.(Unknown Source)
at com.mercury.jdbc.sqlserver.SQLServerImplConnection.f(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.i(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:154)
at com.mercury.optane.core.db.CTdDriverManager.getConnection(CTdDriverManager.java:81)
wrapped in com.mercury.optane.core.CTdException:
at com.mercury.optane.core.db.CTdDriverManager.getConnection(CTdDriverManager.java:88)
at com.mercury.optane.core.db.CConnectionPool.newConnection(CConnectionPool.java:822)
at com.mercury.optane.core.db.CConnectionPool.tryToGetConnection(CConnectionPool.java:612)

Please help

Marked as spam
Posted by (Questions: 91, Answers: 5)
Asked on September 19, 2018 2:29 pm
237 views
Answers (1)
▲
0
▼
✔
Private answer

This specific error:
SQLServer JDBC Driver]Error establishing socket to host and port: ALMDB_TEST:1450. Reason: Connection timed out: connect

Is saying that it cannot connect on port 1460 to SQL-Server ALMDB_TEST.

Try using MS-SQL Server Management Studio to try to connect to your SQL-server FROM THE QC SERVER and login (as the QC DB Admin, or the ''td'' user). You could also try to establish an ODBC connection (Windows/Control Panel/Admin Tools/ODBC).

This will tell you if your QC Server can indeed reach the SQL-Server instance.

Check the port and password for the ''td'' user OR if using Windows authentication in SQL-Server, the user specified to run the QC service.

Sometimes when booting a QC server at the same time as the database server, QC will start BEFORE the database is ready, so it is best to give ample time to the DB startup, then start QC. If the DB is known to already be up and running, then this is not an issue.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on September 19, 2018 2:33 pm
▲
0
▼
Thanks, we cycled the SQL-server, waited a few minutes to confirm it was running, then cycled ALM service and it worked, thanks.
( at September 19, 2018 2:35 pm)
« Back
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Got it!
X
Scroll to Top