Share via

Read operation on a large object failed while sending data to the client

Salam 26 Reputation points
2021-05-23T08:44:03.027+00:00

I have a Sharepoint 2k13 which runs fine with sql2k16 backend (but runs in compatibility 2012 whic was the version before upgrading sql). I tried to run a sharepoint 2k13 backup, since I started perform backup, I started to receive alerts from sql every 5 minutes as follows

A read operation on a large object failed while sending data to the clientK backup

DESCRIPTION: 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.

COMMENT: Indicates that a statement has encountered a problem. Because the problem has affected only the current task, it is unlikely that the database itself has been damaged.

JOB RUN: (None)

I googles a little bit found a thread but for sql2k5. How this can be nailed down and see which object is causing this problem? Thanks

Microsoft 365 and Office | SharePoint Server | For business
SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments No comments

1 answer

Sort by: Most helpful
  1. Jerry Xu-MSFT 7,961 Reputation points
    2021-05-24T08:03:40.33+00:00

    Hi, @Salam ,

    Per my knowledge, this is normal behavior. The database goes into read only status while you are backed up the farm so you can ignore the error. If the error keeps popping up even after the backup, feel free to reply with your update here.


    If an 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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.