In this article, we will be discussing about the “A transport-level error has occurred when sending the request to the server” error message, you might get in SQL Server. This article’s purpose is to explain the above connectivity error and ways of resolving it.
Why you might get the “transport-level” error in SQL Server
In some cases (upon “wrong” actions or network problems 🙂 we might get the following error in SQL Server:
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.)
As the error message indicates, there is a connectivity problem with a previously opened session in SQL Server.
As an example, consider that you have a query window opened. This query window is connected to a database (the default database is “master”). To this end, there is an established connection to that database, that is a session. At a lower level in SQL Server, there is an spid representing this session.
If this spid is forcibly terminated (i.e. by using the SQL Server KILL function, or after an unexpected network problem) and though you are still trying to use this session (i.e. execute a query) you will most probably get the above connectivity error.
How to resolve the issue
A solution in this case, is to close the query window and open a new one. To this end a new session will be opened and will be assigned a new spid. After that, you will be able to use the database properly.
The above connectivity error might arise not only when using the query window, but other SQL Server services that might access SQL Server objects as well. It is a general connectivity error and the best solution for resolving it is to start a new session in order for the connectivity to the specific SQL Server object(s) to be restored/re-initiated.
Strengthen your SQL Server Administration Skills – Enroll to our Online Course!
Check our online course on Udemy titled “Essential SQL Server Administration Tips”
(special limited-time discount included in link).Via the course, you will learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!
Featured Online Courses:
- Introduction to Azure SQL Database for Beginners
- SQL Server 2019: What’s New – New and Enhanced Features
- SQL Server Fundamentals – SQL Database for Beginners
- Essential SQL Server Administration Tips
- Boost SQL Server Database Performance with In-Memory OLTP
- Essential SQL Server Development Tips for SQL Developers
- Working with Python on Windows and SQL Server Databases
- Introduction to Computer Programming for Beginners
- .NET Programming for Beginners – Windows Forms with C#
- Introduction to SQL Server Machine Learning Services
- Entity Framework: Getting Started – Complete Beginners Guide
- How to Import and Export Data in SQL Server Databases
- Learn How to Install and Start Using SQL Server in 30 Mins
- A Guide on How to Start and Monetize a Successful Blog
Check also:
- Best Way to Learn SQL Server – A Suggestion
- All our SQL Server Training-related articles
- What’s New in SQL Server 2019
- New Online Course – SQL Server 2019: What’s New
Rate this article:
Reference: SQLNetHub.com (https://www.sqlnethub.com)
© SQLNetHub
Artemakis Artemiou, a distinguished Senior Database and Software Architect, brings over 20 years of expertise to the IT industry. A Certified Database, Cloud, and AI professional, he earned the Microsoft Data Platform MVP title for nine consecutive years (2009-2018). As the founder of SQLNetHub and GnoelixiAI Hub, Artemakis is dedicated to sharing his knowledge and democratizing education on various fields such as: Databases, Cloud, AI, and Software Development. His commitment to simplicity and knowledge sharing defines his impactful presence in the tech community.
Our application has 12 clients posting transactions to the DB. In the middle of an otherwise eventless run, multiple of the clients will begin getting the transport-level error.
This error suggests a fairly fragile network library for SqlServer.
Curiously, without closing and opening a new connection the transactions eventually start working again.
I've been Googling around looking to see if Microsoft is aware of this problem and if there's any official recommendation or patch.
Of course, other times it works without a hiccup.