Sql Server Error : A transport-level error has occurred when receiving results from the server ...

Question

Sql Server Error : A transport-level error has occurred when receiving results from the server ...

Hamed Vaziri 136

Hi
In my sql server 2014 ssms i've run a simple query like this :
select * from Diet_PatientDetails

but i'm facing this error, during running my query :
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

All other tables works correctly, but when i select from this table, i'm facing the given error!
Where is my problem & how to solve it?
Thanks in advance

SQLZealots 276 Reputation points

2021-04-26T03:43:52.98+00:00

Is Diet_PatientDetails a table or synonym that refers different server object ?
Or whats the object type of Diet_PatientDetails?

Accepted answer

2 additional answers

Your answer

SQLZealots 276 Reputation points

2021-04-26T03:43:52.98+00:00

Is Diet_PatientDetails a table or synonym that refers different server object ?
Or whats the object type of Diet_PatientDetails?

Answer 1

Hi @Hamed Vaziri ,

In addition, please check if there is any corruption in the database. You can use DBCC CHECKDB to check.
If there are any error is reported by DBCC CHECKDB, it is recommended to restore the database from the last known good backup. If this happens to be no good backup, then you have to use the repair option with DBCC CHECKDB after the database placed in emergency mode.

Best Regards,
Amelia

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Erland Sommarskog 121.4K MVP Volunteer Moderator

The first thing I would do is to look in the SQL Server errorlog to see if there are any messages which seem to correlate with this error. Actually, I think that before we venture into other speculations, we should see the errorlog.

Hamed Vaziri 136 Reputation points

2021-04-24T22:08:09.47+00:00

Thanks ErlandSommarskog
I've check out event-viewer and see this error on sql server :

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-04-24T22:10:36.493+00:00

So, are you using READ UNCOMMITTED, a.k.a NOLOCK?

I assume that the table has a LOB column of some sort?
Hamed Vaziri 136 Reputation points

2021-04-24T22:14:45.73+00:00

I don't know!
this database is for our customer & we are working to convert it's data into new database!
Would u plz help me how to work-around this problem?
Thanks in advance
Hamed Vaziri 136 Reputation points

2021-04-25T06:31:17.903+00:00

Hi again
Any help?
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-04-25T09:17:12.28+00:00
Sorry for not responding sooner, but as it was midnight my time, I went straight to bed after posting my last reply.

We can't help you, if you don't help us to help you. That is, if you don't know the answers to the questions I asked on the top of your head, you will need to find out. To see the table definition, you can use sp_help on the table, or script it from SSMS.

One would like to know which isolation level you are using. Since READ COMMITTED is the default, you cannot get READ UNCOMMITTED without asking for it.

But if you don't know what you are doing, try

SELECT * FROM Diet_PatientDetails WITH (REPEATABLEREAD)

I would also recommend that you run DBCC(CHECKDB) on the database. (Or if you don't have permission do so yourself, that you ask the DBA to run it.)
Viorel 122.6K Reputation points

2021-04-25T11:15:40.253+00:00

Did you reproduce the problem after restarting SSMS and using some modified queries, such as ‘SELECT TOP(10) *…’ or ‘SELECT column…’ instead of ‘SELECT *’?

Answer 3

Łukasz Huk 0

In my case the db check showed no errors, the application that reported this problem is running locally on the same machine as SQL Server - so it's not a connection issue.

However, the SQL instance is named, so to be sure, I also turned on Named Pipes, and turned on Ad Hoc Distributed Queries.

I updated MS SQL 2019 to the last available CU (18) and the problem no longer occurs.

Share via

Sql Server Error : A transport-level error has occurred when receiving results from the server ...

2 additional answers

Your answer