Datamaker: A network-related or instance-specific error has occurred while establishing a connection to SQL Server

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

When trying to connect to our Microsoft SQL Server repository database in Datamaker, I am receiving the following error messages: 

Attempting connection 
[Microsoft][SQL Server Native Client 11.0]Encryption not supported on the client. 
[Microsoft][SQL Server Native Client 11.0]SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm. 

[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection 
[Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 

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

You will need to work with your internal IT team to resolve this since it is caused by a database or environment related issue. 

Resolution:

Here are some things you need to check for and make sure are configured: 

1. MSSQL Server is not started.
- Starting of it will allow you to see your MSSQL Server/instance in the drop-down list of available MSSQL Servers. 
a) Go to the Start menu -> Control Panel -> Administration Tools -> Services. 
b) In the list of services find SQL Server (instance name, by default it is EZPARTS5) and check its status, it must be Started (if it is not started, then right click on SQL Server and select Start from the context menu). 


2. Firewall is blocking port 1433 (MSSQL standard port for connections).
- It can be disabled following the steps below: 
a) Go to the Start menu -> Control Panel -> Administration Tools -> Services. 
b) Find Firewall service, it must be disabled (if it is not, then right click the service and select Stop from the context menu). 

Note: More information on this can be found on the official Microsoft site: http://msdn.microsoft.com/en-us/library/cc646023.aspx 


3. TCP/IP protocol is disabled for MSSQL protocols. To enable it, see the steps below: 
a) Navigate to SQL Server Configuration Manager in the Start menu. 
b) Specify settings for TCP/IP protocol in SQL Server Configuration Manager. 
c) Restart the computer. 

Note: More information on this can be found on the official Microsoft site: http://msdn.microsoft.com/en-us/library/bb909712%28v=vs.90%29.aspx 


4. Make sure your database engine is configured to accept remote connections (If you are using centralized database): 
a) Open SQL Server Management Studio. 
b) Right click SQL Server instance -> Properties -> Connections -> Check the Allow remote connections to this server box. 
c) Go to the General section and check name of SQL Server specified in the Name field. 


5. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings.
- Usually the format needed to specify the database server is machinename\instancename. 


6. Make sure your login account has access permission on the database you used during login. 
Alternative: 
- If you still can’t get any connection, you may want to create a SQL account on the server, a corresponding SQL user on the database in question, and just use this username/password login data to connect to SQL Server. 

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.