Forum Discussion
Issue connecting to Fabric SQL Server thru SSMS
We have been using Microsoft Fabric SQL Databases for a couple months now, and have been using SSMS as the primary data access tool. We connect/authenticate using Microsoft Entra MFA, and we've not had any issues with users connecting to the SQL Server or Fabric SQL databases until this past week when we started intermittently getting the following error:
------------
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)
------------
I cannot discern a pattern as to when the log in works or doesn't work, but we have been able to successfully log in at least once per day, even if not for very long and I get kicked out again.
We have no issues accessing the databases directly within the online Fabric environment, but can't seem to authenticate using an external tool. We have the latest version of SSMS (22) and are operating on Windows 11. We do not have any additional Fabric workspace network rules configured. Our capacity sometimes reaches the limit, but the error persists even after increasing the limit.
Any ideas on what else we need to look into to resolve this access issue?
We explored many networking side issues with no luck. So far, with better managing the capacity and avoiding overloaded states as much as possible, we've been able to avoid this issue!
10 Replies
tayloramy Thank you. We haven't made any network changes, and don't see any regional outages in our area (South Central Region). We paused & resumed our Fabric Capacity and this resolved the issue, so perhaps it was ultimately related to our capacity being in an throttled/overloaded state?
v-abhinavmuCommunity Support
Hi bhennessy1,
Thanks for the update. Glad to hear that pausing and resuming the Fabric Capacity resolved the connection issue. It’s also useful to see another report of a similar issue being resolved on the networking side. Hopefully this helps others who may encounter the same intermittent SSMS connection error.
Thank you.
We explored many networking side issues with no luck. So far, with better managing the capacity and avoiding overloaded states as much as possible, we've been able to avoid this issue!
- tayloramy
Super User
Hi bhennessy1,
Have there been any network changes that have happened in your on prem environment by chance?
Hi tayloramy, Our set up is fully cloud-based, so we aren't using an on-prem environment. And we haven't introduced any network changes, either to Fabric or within our Microsoft tenant as a whole.
- tayloramy
Hi bhennessy1,
Even if all your data sources are cloud based, SSMS is running on a computer in your on prem environment connected to your internal network, so it would have an impact if your IT changed on prem firewall settings.
What region is your capacity in? Perhaps there's a regional outage not yet reported?
Everything is working good in Canada Central right now.
- svenchio
Hi bhennessy1 this error is commonly tied to the TLS/pre-login handshake not completing within its expected window (normally between 100–200ms), some of the usual suspects are:
#1. Client-side network latency (e.g. VPN, proxy, change in corporate network)
#2. TLS protocol mismatch between the client machine and the Fabric SQL endpoint (e.g. Encrypt=Mandatory vs Optional)
#3. Server side issues (e.g. regional outage on specific fabric items)
Given your description (started abruptly across multiple users with no client-side changes) and no changes in the TLS protocol (same type of connection, encryption and credentials) I would bet the reason to be a transient/regional issue on the Fabric SQL endpoint side. ; I would suggest you to check with your network team if they are performing some sort of SSL inspection, just to be sure.
If the problem does not go away withing the next 12 hours, I'd suggest opening a support ticket with Microsoft with timestamps of failures, hoping you have a support contract 😅 🤞(Help + Support / > New support request)
Let us know if the connection via SSMS is working now... if you find this info useful, give us a thumbs up, best of lucks!
Hello bhennessy1 , If you have any security app for network security like Zscalar, its worth checking with them, most of the times tunnel needs ip whitelisting to communicate without interruption.
jj44Advocate I
Hi bhennessy1, we were experiencing the same issue.
And to muddy the waters...I could connect to a Fabric SQL Warehouse using Entra MFA. But not SQL database using Entra MFA.
Its now resolved, according to our IT guys, it was a problem with Azure private links service.
