SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 .NET Inside SQL Server (2005)
 Sql Error 3617
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

subbum12
Starting Member

2 Posts

Posted - 05/26/2014 :  04:04:33  Show Profile  Reply with Quote
Hi All,

I'm getting Sql Error 3617 when trying to execute a select query from the application that too the error is coming to one or two members. Any idea/guess ?

tkizer
Almighty SQL Goddess

USA
36949 Posts

Posted - 05/26/2014 :  20:04:31  Show Profile  Visit tkizer's Homepage  Reply with Quote
Show us the text of the error, please.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

subbum12
Starting Member

2 Posts

Posted - 05/27/2014 :  06:09:55  Show Profile  Reply with Quote
3617 -Sql Error 3617 -notfound in teh error.sql
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
36949 Posts

Posted - 05/27/2014 :  13:45:46  Show Profile  Visit tkizer's Homepage  Reply with Quote
Please run the query in Management Studio and see if it errors there too. If it does, please post that error. If it doesn't, then the issue is with the application code.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

TG
Flowing Fount of Yak Knowledge

USA
6062 Posts

Posted - 05/27/2014 :  13:59:59  Show Profile  Reply with Quote
I don't know if this is true and it's a new one on me but this forum post discusses that error.
quote:

Error code 3617 is a system attention. A system attention occurs when the client cancels a running request. This can happen if the command times out for example. This error is normally not sent to the client however.

There is a special case where this can occur that you may be hitting. When you re-use a pooled connection, the first outbound request sends a special bit flag on the request to tell the server to reset the connection state prior to executing the request. This bit causes the server to first clear connection state, then execute the command. If your SQL Server is under heavy load, and this bit is set, and it takes a long time to reset the connection state, the client may timeout and send the system attention. This causes the reset of the connection to be cancelled and in this case you can see the 3617 sent to the client.

We've recently hardened this code in current release to avoid sending back this specific error code as the error is spurious in nature (based on timing you may or may not get this error). In any case, you can consider this error equivalent to: "A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user."

To verify if it is this issue, examine your SQL errorlog for error like below:

spid51 Task abort was requested while attempting to reuse a session with SPID 51, which has been reset for connection pooling. The session will be terminated.

Proposed as answer by William Assaf Thursday, July 05, 2012 9:01 PM




Be One with the Optimizer
TG
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000