dbTalk Databases Forums  

Help with 1205 Not raised

comp.databases.ms-sqlserver comp.databases.ms-sqlserver


Discuss Help with 1205 Not raised in the comp.databases.ms-sqlserver forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
gigijk@gmail.com
 
Posts: n/a

Default Help with 1205 Not raised - 04-08-2005 , 09:52 AM






Hi,
I have an application that causes a dead lock at random. The issue I am
having is, when the deadlock occurs, my applications is not recieving
any errors from the DB. ie, during the deadlock SQLServer is returning
an empty recordset and user is seeing a blank screen. The app logic
does not go into the Try Catch statment in the C# code. I can't
understand why my app is not receiveing 1205 error from SQL server when
dead lock occurs.
Any ides why this is happening?

Thanks
_GJK


Reply With Quote
  #2  
Old   
Razvan Socol
 
Posts: n/a

Default Re: Help with 1205 Not raised - 04-08-2005 , 12:15 PM






Read the following article by Erland Sommarskog, SQL Server MVP:
http://www.sommarskog.se/error-handling-I.html#ADO.Net
especially this part: "If you use ExecuteReader, there are a few extra
precautions. If the stored procedure first produces a result set, and
then a message, you must first call .NextResult before you get an
exception, or, for an informational message, any InfoMessage event
handler is invoked."

Razvan


Reply With Quote
  #3  
Old   
GJK
 
Posts: n/a

Default Re: Help with 1205 Not raised - 04-08-2005 , 12:34 PM



In my case I am using SQLDataReader and sp being killed in the deadlock
is a simple select statement containing single resultset.
_GJK

Razvan Socol wrote:
Quote:
Read the following article by Erland Sommarskog, SQL Server MVP:
http://www.sommarskog.se/error-handling-I.html#ADO.Net
especially this part: "If you use ExecuteReader, there are a few
extra
precautions. If the stored procedure first produces a result set, and
then a message, you must first call .NextResult before you get an
exception, or, for an informational message, any InfoMessage event
handler is invoked."

Razvan


Reply With Quote
  #4  
Old   
GJK
 
Posts: n/a

Default Re: Help with 1205 Not raised - 04-08-2005 , 12:35 PM



In my case I am using SQLDataReader and sp being killed in the deadlock
is a simple select statement containing single resultset.
_GJK

Razvan Socol wrote:
Quote:
Read the following article by Erland Sommarskog, SQL Server MVP:
http://www.sommarskog.se/error-handling-I.html#ADO.Net
especially this part: "If you use ExecuteReader, there are a few
extra
precautions. If the stored procedure first produces a result set, and
then a message, you must first call .NextResult before you get an
exception, or, for an informational message, any InfoMessage event
handler is invoked."

Razvan


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.