Troubleshooting: The TCP/IP connection to host local, port 1433 has failed
search cancel

Troubleshooting: The TCP/IP connection to host local, port 1433 has failed

book

Article ID: 5021

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

Users of Test Data Manager (TDM), Unified Infrastructure Management (UIM), or other applications connecting to a Microsoft SQL Server database may encounter the following JDBC connection error:

Could not get JDBC Connection; The TCP/IP connection to the host [HOSTNAME], port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall."

This issue typically occurs in the following scenarios:

  • Testing connection profiles in Datamaker or TDM Portal.
  • Launching Subset individually or from Datamaker.
  • Initial configuration of the UIM database.

Environment

  • CA Test Data Manager (TDM)

  • UIM ( Unified Infrastructure Management) with SQL Server DB

Cause

There are several potential causes of this error message:

  • For SQL Server, specifying both the Instance Name or Port number, instead of just one.

  • For SQL Server Express, not having a static TCP port and having a dynamic entry instead. 

  • SQL Server may not be running on the host or accepting TCP/IP connections at the port.

  • TCP connections could be blocked by a firewall or not enabled.

  • For SQL Server, using 'local' as the Server Name instead of localhost or the IP address. 

  • Your profiles.xml file from C:\%AppData%\roaming\Grid-Tools folder may be corrupted or contain incorrect information.

  • The database may not be up and running. 

  • The hostname, username, or password may be incorrect. 

Resolution

1. Enable TCP/IP in SQL Server

  1. Open the SQL Server Configuration Manager.
  2. Expand SQL Server Network Configuration > Protocols for [YourInstanceName].
  3. Right-click TCP/IP and select Enable.
  4. Double-click TCP/IP and navigate to the IP Addresses tab.
  5. Scroll to the IPAll section and set the TCP Port to 1433. Ensure TCP Dynamic Ports is blank.
  6. Restart the SQL Server Service for the changes to take effect.

2. Verify Host Reachability

To confirm the port is open and accepting connections from the application server:

  1. Open a Command Prompt.
  2. Run the following command: telnet [IP_ADDRESS] 1433
    • Success: A blank screen indicates the connection is established.
    • Failure: "Could not open connection to the host" indicates a network or firewall block.

3. Resolve SQL Server Express Specifics

SQL Server Express often defaults to dynamic ports. To fix this:

  • In the SQL Server Configuration Manager, remove any values in the TCP Dynamic Ports field and explicitly enter 1433 in the TCP Port field.

4. Configure "Local" vs "Localhost"

While SQL Management Studio may resolve "local," JDBC-based applications often require explicit naming:

  • Change the Server Name in your connection profile to localhost or the specific IP Address of the database server.

5. Repair Corrupted Profiles (TDM Only)

If the error occurs specifically in Subset:

  1. Navigate to C:\Users\[User]\AppData\Roaming\Grid-Tools.
  2. Delete the profiles.xml file.
  3. Relaunch GTSubset and recreate the connection profiles for the Source and Repository.

Additional Information

If you are still experiencing any issues, please open a support case by going to https://support.broadcom.com

Powered by Wolken Software