Error, "The TCP/IP connection to host, port 1433 has failed. Error "connection time-out, Verify connection properties..." creating CLM database tables from JTS Setup
SQL Server is running on a non-default TCP port (not on port 1433) and IBM Rational Jazz Team Server (JTS) setup fails to create the database connection for IBM Rational Quality Manager (RQM), Rational Team Concert (RTC), Jazz Team Server, Rational Requirements Composer (RRC).
Error in JTS setup, attempting to configure the JDBC connection for a CLM database:
CRAJ1579E ID CRAJ1579E
The TCP/IP connection to host x, port 1433 has failed. Error , "connection time-out. Verify the connection properties, check that an instance of SQL server is running and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port."
The SQL Server instance is possibly running on a non-default port (1433 is the default port) or a firewall such as the Microsoft Windows Firewall preventing access to the port used in the JDBC connection.
Diagnosing the problem
Check the Microsoft Windows registry hive KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQLServer\SuperSocketNetLib\Tcp\ for the key TcpPort. The value of TcpPort is what SQL Server will use for TCP communication. The default value is 1433 but non-default ports can be used.
Run netstat -na | findstr <port>
where <port> is the port used in the JDBC connection string that fails with the error above. If the port is open, this command should show a LISTENING status
C:\WINDOWS>netstat -na | findstr 1433
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 192.168.199.254:1433 188.8.131.52:2939 ESTABLISHED
If nothing is returned, the port is not open and listening. Check the Microsoft Windows registry value above to see if a non-default port is used.
Resolving the problem
If the Microsoft Windows registry TcpPort key is not using the default SQL Server port of 1433, test the JDBC connection string using the port set in the TcpPort registry key. If test connection still fails, disable any firewall software or ensure the firewall has a rule to allow communication on the port being used. Ensure that netstat -na shows the port used in the JDBC string as LISTENING.
The Jazz based products have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.
Review technote 1319600: Leveraging the Jazz Community on Jazz.net for details.
Translate this page: