Datamaker: SQLSTATE = 08001 error- No connection could be made because the target machine actively refused it.

Document ID : KB000004456
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

When trying to connect to a SQL database in Datamaker, we are receiving the following error message, despite being able to connect to it using the same details in the SQL Server management studio: 

CA Test Data Manager-Datamaker has experienced a problem connecting to your SQL Server Test Data Repository using the information supplied. 
The error message returned from the SQL Server client software is given below: 
SQLSTATE = 08001 
[Microsoft][SQL Server Native Client 10.0] TCP Provider: No connection could be made because the target machine actively refused it. 
Please rule out the following common causes of this connectivity issue before contacting support: 

1. SQL Server service is not running on SQL Server. 
2. TCP/IP protocol is not enabled for SQL Server. 
3. SQL Server Browser service is not running on SQL Server. 
4. Firewall on SQL Server is blocking TCP port of SQL Server. 
5. Firewall on SQL Server is blocking UDP port (1434) of SQL Server browser. 

Environment:
CA Test Data Manager (TDM)- Datamaker
Cause:

The most common causes for this issue are listed in the actual error message: 

  • SQL Server service is not running on SQL Server. 
  • TCP/IP protocol is not enabled for SQL Server. 
  • SQL Server Browser service is not running on SQL Server. 
  • Firewall on SQL Server is blocking TCP port of SQL Server. 
  • Firewall on SQL Server is blocking UDP port (1434) of SQL Server browser. 

 

Here are some other causes we have seen:

  • Not using the IP address along with the port number for the ODBC data source. 
  • Not having administrator privileges. 
  • Using the wrong connection details. 
Resolution:

Below are the resolutions for the top 5 common causes of this error message. We highly recommend working with your internal IT team or DBA when doing these steps. 

 

SQL Server service is not running on SQL Server:

This document describes how to start, stop, pause, resume, or restart the SQL Server Database Engine, the SQL Server Agent, or the SQL Server Browser service by using SQL Server Configuration Manager, SQL Server Management Studio, net commands from a command prompt, Transact-SQL, or PowerShell: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/start-stop-pause-resume-restart-sql-server-services 

 

TCP/IP protocol is not enabled for SQL Server:

This document describes how to use the SQL Server Configuration Manager to enable the TCP/IP network protocol for the SQL Server instance: https://technet.microsoft.com/en-us/library/hh231672(v=sql.110).aspx 

 

SQL Server Browser service is not running on SQL Server:

This document describes how to start and stop the SQL Server Browser service: https://technet.microsoft.com/en-us/library/ms165734(v=sql.90).aspx 

 

Firewall on SQL Server is blocking TCP port of SQL Server:

This document reviews how to configure the Windows firewall to allow SQL Server access: https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access 

 

Firewall on SQL Server is blocking UDP port (1434) of SQL Server browser:

This document reviews how to configure the Windows firewall to allow SQL Server access: https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access 

Additional Information:

If you experience any further issues, please open a support case by going to https://www.ca.com/us/services-support/ca-support/contact-support.html