Forum Discussion
kushalvaykole
1 month agoFrequent Visitor
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 i...
- 1 month ago
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)
audreygerred
1 month agoSuper User
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)
kushalvaykole
1 month agoFrequent Visitor
Thanks! audreygerred It was a VPN connection issue.