Forum Discussion
sql endpoint connection
DataSource.Error: Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Details:
DataSourceKind=SQL
DataSourcePath=xxxxxxx.fabric.microsoft.com;kpi_history
Message=A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hi!
- Your Fabric capacity may be paused or suspended — if the capacity is offline, the endpoint won't respond
- The workspace may have been deleted or renamed, making the connection string stale
- Fabric SQL endpoints sometimes require you to connect via HTTPS/TDS on port 1433, which a firewall may be blocking
- If your source requires a gateway, ensure that is configured properly
You can try the following:
- Open the Fabric portal and confirm the workspace and capacity are active
- If published, check the gateway status in Power BI Service under Settings → Manage gateways
- Try connecting to the same endpoint fresh from Power BI Desktop to isolate whether it's a Service/gateway issue vs. a general connectivity issue
- Confirm the server string in your Power Query source step exactly matches the current Fabric endpoint URL (these can change if a workspace is renamed)
3 Replies
Hi!
- Your Fabric capacity may be paused or suspended — if the capacity is offline, the endpoint won't respond
- The workspace may have been deleted or renamed, making the connection string stale
- Fabric SQL endpoints sometimes require you to connect via HTTPS/TDS on port 1433, which a firewall may be blocking
- If your source requires a gateway, ensure that is configured properly
You can try the following:
- Open the Fabric portal and confirm the workspace and capacity are active
- If published, check the gateway status in Power BI Service under Settings → Manage gateways
- Try connecting to the same endpoint fresh from Power BI Desktop to isolate whether it's a Service/gateway issue vs. a general connectivity issue
- Confirm the server string in your Power Query source step exactly matches the current Fabric endpoint URL (these can change if a workspace is renamed)
Thanks! audreygerred It was a VPN connection issue.
Should we look at your error and guess your question and then answer that question, or would you like to show us your query and ask a question? Don't be lazy.
