Error: 7886, Severity: 20, State: 1.

SQLServerCentral is supported by Red Gate Software Ltd.

Home Tags Articles Editorials Forums Scripts Videos Blogs QotD Books Ask SSC SQL Jobs Training Authors About us Contact us Newsletters Advertise Write for us

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Error: 7886, Severity: 20, State: 1.

17 posts, Page 1 of 2

1 2 »»

Error: 7886, Severity: 20, State: 1.

Rate Topic

Display Mode

Topic Options

Author

Message

NicHopper

Posted Monday, January 12, 2009 3:04 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:29 AM
Points: 731, Visits: 797

Hi all,

Last night my SQL box (2005 Std) reported the following error, this occured at just after 18:00

"Message
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."

Then at 19:00, my hourly transaction logs backups ran (for 7 seconds), then the SQL box became unresponsive and required a restart at around 19:15.

I cant find any indication as to why it became unresponsive (sql logs, event viewer) and judging by the fact that it occured so long after the error message that would indicate that the two are unreleated.

I was wondering if anyone had come across this error before and if so, had it caused any performance issue which could cause the box to become unresponsive.

Thanks,

Jackal

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Post #634529

GilaMonster

Posted Monday, January 12, 2009 8:48 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 3:55 AM
Points: 17,119, Visits: 12,217

Anything in the SQL error log?

Gail Shaw

We walk in the dark places no others will enter
We stand on the bridge and none may pass

Post #634745

NicHopper

Posted Monday, January 12, 2009 9:17 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:29 AM
Points: 731, Visits: 797

Hi Gail,

Thanks for the response, the SQL logs show the error occuring at 6.01pm, then transaction log backups at 7.00pm and then the actions involved with restarting SQL. Other than that nothing of any use what so ever.

Thanks,

Jackal

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Post #634774

GilaMonster

Posted Monday, January 12, 2009 9:26 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 3:55 AM
Points: 17,119, Visits: 12,217

Jackal (1/12/2009)

Thanks for the response, the SQL logs show the error occuring at 6.01pm

Can you post the full message that was in the log?
Anything in the windows event logs?

Gail Shaw

We walk in the dark places no others will enter
We stand on the bridge and none may pass

Post #634782

eng_mgomaa

Posted Tuesday, January 13, 2009 10:39 PM

Grasshopper

Group: General Forum Members
Last Login: Tuesday, March 02, 2010 9:56 PM
Points: 23, Visits: 95

I had the same error, but didn't know the reason, it appeared three or four times and then disappeared completly, if someone has analysis for this event please confirm us

Post #636012

ALZDBA

Posted Wednesday, January 14, 2009 12:07 AM

SSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 8:55 AM
Points: 4,976, Visits: 3,925

If you cannot fine any reasonable / related message in sqlservers errorlog,
I would suggest to at least run DBCC CheckDB (for the db if you know it, if you don't for all dbs)

Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere w00t

Very usefull HowTo for forums:
- How to post Performance Problems
- How to post data/code to get the best help

Post #636031

NicHopper

Posted Wednesday, January 14, 2009 2:33 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:29 AM
Points: 731, Visits: 797

It's certainly a strange one.

I cant find anything in either the SQL logs or the Windows logs. I'll shortly be posting the logs up so hopefully someone maybe able to spot something.

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Post #636071

Hadrian

Posted Wednesday, January 14, 2009 3:00 AM

SSChasing Mays

Group: General Forum Members
Last Login: 2 days ago @ 3:15 AM
Points: 692, Visits: 407

check this http://support.microsoft.com/kb/323630

Post #636079

Hadrian

Posted Wednesday, January 14, 2009 3:11 AM

SSChasing Mays

Group: General Forum Members
Last Login: 2 days ago @ 3:15 AM
Points: 692, Visits: 407

check if you are using large objects,LOB and try to reduce the level of locking checking for indexes,denormalize the table.

Post #636084

NicHopper

Posted Wednesday, January 14, 2009 3:34 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:29 AM
Points: 731, Visits: 797

The table that I beleive is causing this issue has a TEXT column in it.

It's a bit of an open ended question but what exactly is happening when this error is occuring, is it just a case of SQL not being be able to confirm the integrity of the data and then killing the connection for data integrity purposes?

------------------------------------------------------------
Check out my blog

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Post #636091

« Prev Topic | Next Topic »

17 posts, Page 1 of 2

1 2 »»

Permissions