By 33,291 total views, 7 views today
The specified network name is no longer available – if you have a SharePoint farm with multiples servers, then from the SharePoint server log we might get this error – “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.).”, this error is generally generated by the “Diagnostic Data Provider: Performance Counters – Web Front Ends” timer job. In this article, we will understand the root cause of this error and how to fix this.
By looking at the error message, it seems to be there are some issues in the network layer as the error message contains a TCP provider, after some analysis by checking the ULS log you will get to know it is a network failure error from the SQL server – meaning, the database connection is closed by the database server and the connection remains valid in the connection pool of your app; as a result, when the WFE server try to reach to SQL database server, it’s not able to reach the database.
Key-Highlights: What you will learn from this article?
- What is the root cause of the “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.).” error in the SharePoint WFE server?
- How to fix the “A transport-level error has occurred – The specified network name is no longer available.” error?
- What is the AG (availability group) group in the SQL server and what is its use of it?
Why does the transport-level TCP Provider error occur?
There could be many reasons, however, this could be the obvious one of the one. Before we get into this, we must know about the SQL Server AG (Availability Group) Group. In simple words, a SQL Server AG (Availability Group), is multiple database servers configured in the backend which is the backup of each other, meaning – if one SQL server fails to respond, the other SQL server will take over the job which increases the reliability, availability of SharePoint environment this is also known as SQL server always-on availability groups – means your SQL server will be always on, no downtime. One of the primary advantages of having an AG (Availability Group) group is – Zero Data Loss Protection.
Some of the benefits of AlwaysOn Availability Groups are as below:
- Zero data loss protection
- Failover of multiple databases.
- Automatic or manual Failover
- Local or shared storage
- Active use of secondaries
- Enhanced performance
In the below example, we will see the real-time benefits of the SQL Server AG (Availability Group) group.
Let’s say, by default, the SQL_Server_1 is configured as a primary server in the AG (Availability Group), and due to some technical reason, the SQL_Server_1 fails to respond to SharePoint WFE (Web Front End) server, then due to the power of AG group the other second SQL server will take care the job. So, in between switching the SQL server role – if the SharePoint WFE (Web Front End) server tries to contact the SQL server, the connection will be lost, hence in the SharePoint end, we get the “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.).”. However, it doesn’t impact SharePoint as this happens in just a fraction of seconds.
What to do when we see this transport-level TCP Provider error?
As soon as we see this error in SharePoint, we should contact to IT Networking team who maintains your SharePoint server.
Apart from the AG (Availability Group) reason, means, we don’t see that there was a server switch in the AG (Availability Group) however, still we see this error – we might look into the below configuration from the SQL server:
- Verify that the SQL Server Browser service is running
- Verify that the TCP/IP connections are enabled for SQL Server
- Verify that named pipes enabled for SQL Server
Note:
- After enabling the TCP/IP and Named Pipes, we need to stop and restart the SQL Instance and the SQL Browser.
Summary: What do we have here (Transport-level error)?
Thus in this troubleshooting article, we have learned the below with respect to transport-level TCP Provider error:
- What is the root cause of “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.).”
- What are the possible ways we can fix the “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.).” error.
- What is the AG (Availability Group) group in SQL server and what is its use of it?
- When do we get “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.).” error from SharePoint WFE (Web Front End) server.
- Benefits of AlwaysOn Availability Groups (AG groups).
See Also: The specified network name is no longer available
You may also like the below SharePoint troubleshooting articles:
- How to fix Open with Explorer issues in SharePoint Online?
- [Fixed]: Provider Hosted App Error – Invalid issuer or signature
- [Fixed]: How to fix No gulpfile found in SPFx framework project
- [Fixed] Error – activate the SharePoint Server Publishing Infrastructure feature in SharePoint Online site
- [Fixed] Server relative urls must start with SPWeb.ServerRelativeUrl”in reading web part properties!
- [Fixed]: The page could not be created. Custom Scripting might be deactivated on the destination site or you might not have sufficient permissions.
- [Fixed] The upgraded database schema doesn’t match the TargetSchema(Failed to upgrade SharePoint Products)
- [Fixed] “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error)
- [Fixed] How to fix the “Unexpected response from server. The status code of response is ‘500’ in SharePoint 2016 Search error.”?
- [Fixed] How to fix the wrong tenant credential error in SharePoint online?
- [Fixed] How to fix request timed out error in SharePoint 2016 search (There was no endpoint listening)?
- [Fixed] How to Fix a SharePoint 404 Error in sub site After Restoring a Content Database?
- The specified network name is no longer available
Download SharePoint Online & Office 365 Administration eBook
Buy the premium version of SharePoint Online & Office 365 administration eBook from here:
Get the free demo PDF eBook from here:
Send download link to:
About Post Author
