metricsign
Start free
High severityconnection

Power BI Refresh Error:
53

What does this error mean?

The SQL Server cannot be reached via Named Pipes — the network path does not exist or Named Pipes is not enabled.

Common causes

  • 1Named Pipes protocol is disabled on the SQL Server
  • 2The server name in the connection string resolves to a different machine
  • 3SQL Server Browser service is stopped, preventing instance name resolution

How to fix it

  1. 1Step 1: Enable Named Pipes (or switch to TCP/IP): SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for <instance> → enable Named Pipes or TCP/IP.
  2. 2Step 2: Ensure SQL Server Browser is running if using named instances: SQL Server Configuration Manager → SQL Server Services → SQL Server Browser → Start.
  3. 3Step 3: Prefer TCP/IP over Named Pipes for remote connections — add 'tcp:' prefix to the server name in the connection string or explicitly set port: server,1433.

Frequently asked questions

When should I use Named Pipes vs TCP/IP?

Named Pipes is only suitable for local connections on the same machine. For all remote connections — including ADF and Power BI — use TCP/IP.

How do I check which protocols are enabled on SQL Server?

Open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for <instance>. Enabled protocols show Status: Enabled.

Does error 53 appear in Azure Data Factory?

Yes, when a self-hosted integration runtime machine cannot reach the SQL Server via Named Pipes. Switching the connection string to TCP/IP (server,port format) usually resolves it.

Official documentation: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol

Other connection errors