metricsign
Start free
High severityconnection

Power BI Refresh Error:
10060

What does this error mean?

The TCP connection attempt to SQL Server timed out — the server did not respond within the client's timeout window.

Common causes

  • 1Firewall silently dropping packets instead of actively refusing the connection
  • 2SQL Server is on a wrong port (not 1433) and the client is connecting to the right port but the server is unresponsive
  • 3Network congestion or high latency between the ADF IR and the SQL Server

How to fix it

  1. 1Step 1: Test connectivity and timing: Test-NetConnection -ComputerName <server> -Port 1433. A timeout here confirms the firewall is dropping packets silently.
  2. 2Step 2: Check SQL Server Configuration Manager for the actual listening port: SQL Server Network Configuration → TCP/IP → IP Addresses → IPAll → TCP Port.
  3. 3Step 3: Open the correct port on all firewalls between client and server: both the OS firewall (Windows Firewall) and any network firewall or NSG (Azure Network Security Group).

Frequently asked questions

How does error 10060 differ from error 10061?

Error 10060 is a timeout (no response) — typically caused by a firewall silently dropping the packet. Error 10061 is a refused connection — SQL Server actively rejected it, usually because it's not running or not listening on that port.

Can error 10060 appear in Azure Data Factory?

Yes — when a self-hosted IR tries to reach an on-prem SQL Server and the firewall blocks it. Check NSG rules and Windows Firewall on the SQL Server machine.

What is the default TCP timeout for SQL Server connections?

The default connection timeout in most clients (ADO.NET, ODBC) is 15–30 seconds. A 10060 error appears after this period if no SYN-ACK is received.

Official documentation: https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors

Other connection errors