Critical severityconnection
Power BI Refresh Error:
2
What does this error mean?
The client cannot establish a TCP connection to the SQL Server — the server name is wrong, the port is blocked, or SQL Server is not running.
Common causes
- 1Wrong server name, instance name, or port in the connection string
- 2SQL Server service is stopped
- 3Firewall blocking TCP port 1433 (or custom port) between client and server
How to fix it
- 1Step 1: Verify SQL Server is running: in SSMS Object Explorer connect with the exact server name, or run: Test-NetConnection -ComputerName <servername> -Port 1433 from the client.
- 2Step 2: Check firewall rules — ensure TCP 1433 (or the custom port) is open inbound on the SQL Server and outbound on the client. For ADF self-hosted IR, check the IR machine's outbound rules.
- 3Step 3: Verify the connection string format: for a named instance use <server>\<instance>,<port> or enable the SQL Server Browser service so instance names resolve automatically.
Frequently asked questions
Official documentation: https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-2-database-engine-error