Share this article
This article is translated in
Improve this guide
Fix: System.Data.SqlClient.SqlException (0x80131904)
Discover expert solutions that worked for others
3 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
This article is translated in
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
Administrators creating applications using aSQL connectiondon’t usually face many issues if the backend is tight. But often, due to misconfigurations or network issues, users come across the0x80131904error.
The message reads,A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The specified network name is no longer available.). It’s not something regular users can fix, and administrators, too, have a tough time dealing with it. Let’s find out more!
What is component error code 0x80131904?
The error usually has to do with a network-related issue, but if the problem persists, it could be settings to blame. More so, for some administrators, only a handful of users encountered the0x80131904error, while others could easily access things.
Here are a few reasons you are encountering the error:
How do I fix error 0x80131904?
Before we move to the slightly complex solutions, check these aspects first:
If none work, head to the fixes listed next.
1. Change the DNS entries
An administrator shared that changing the DNS entries fixed things when only a single user was unable to access the server while others could. Whether or not that’s the case with you, do try this first.
2. Reconfigure server authentication setting
In some cases, the server’s security settings were be to blame for the0x80131904: login failederror, and reconfiguring Server authentication toSQL Server and Windows Authentication modegot things running.
3. Downgrade the SQL client package
For many, the problem appeared after updating to a newer SQLClient package, which points to a bug in it. And in this case, you should downgrade to the previous one.
For instance, a user reported the issue after upgrading to2.0.0from1.1.3and reverting the change fixed things in no time.
4. Remove problematic suites
If nothing else worked, you could remove the following two cipher suites from the client list:TLS_DHE_RSA_WITH_AES_256_GCM_SHA384TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
This has worked for many users, but remember to check if a patch has been released for the problem before making changes to fix0x80131904.
Before you leave, check some quick tips toincrease the Internet speed in Windows.
For any queries or to share what worked for you, drop a comment below.
More about the topics:sign-in issues,sql server
Kazim Ali Alvi
Windows Hardware Expert
Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He’s specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He’s also one of our experts in Networking & Security.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kazim Ali Alvi
Windows Hardware Expert
Kazim is specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
