[Company Logo Image] 

Home Up Contents Coffee Break Credits Glossary Links Search

 
Msg 10061 TCP Provider No connection could be made

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
SQL Server 2017
SQL Server 2019
Tips
Troubleshooting
Tuning

Msg 10061 TCP Provider No connection could be made.


Applies to: Microsoft SQL Server 2019, Azure SQL Database

Date created: February 25, 2020.
 

Problem Description.
 

I was trying to make all the configuration required to use Polybase external tables to query an Azure SQL Database. I had installed Polybase and enable it on the server already and proceeded to create a master key and a database credential successfully. However, when I tried to create the External Data Source the following error came up:

OLE DB provider "MSOLEDBSQL" for linked server "(null)" returned message "Login timeout expired".
OLE DB provider "MSOLEDBSQL" for linked server "(null)" returned message "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.".
Msg 10061, Level 16, State 1, Line 0
TCP Provider: No connection could be made because the target machine actively refused it.


Completion time: 2020-01-21T21:24:03.1263604-08:00
 


 

Cause.


This error may appear because Polybase services have not been started.

 

Solution.


Open SQL Server Configuration Manager and start Polybase services.









 

 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.