Error: 7884, Severity: 20, State: 1 - by Francesco Quaratino

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 518156 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/4/2009 8:12:52 AM
Access Restriction Public


during the test of our application, we found many istances of this error on our SQL Server 2008 Enterprise Ed in the SQL logs:
Error: 7884, Severity: 20, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
any ideas on what could cause this?
Sign in to post a comment.
Posted by Mike [MSFT] on 3/22/2010 at 1:57 PM
Hi Francesco,

I'm closing this issue as Won't Fix since it is likely the expected error for your situation. Per the last comment you can examine the error log for the previous error to determine the cause of the 7884 error. If that doesn't identify the problem I'd recommend calling our support group or posting a question to the SQL Server forums.

You can find a list of the available support options, both paid and free, on

Mike Wachal
SQL Server
Posted by Madhan [MSFT] on 1/4/2010 at 8:23 AM
Dear Customer,
I apologize for the delay in getting back to you regarding this item. The Error code 7884 implies a TDS protocol violation which most often is caused by the previous exception. you can find that by looking through your error log and finding out what the previous error is and rootcausing that. If you can send us the error log, we can also help you in doing that.

thank you