|
Prev: Check Reporting Services Installation Programmitcally
Next: Need help with a hard SELECT STATEMENT.
From: ShadowFRJ on 21 Jul 2008 17:20 I've had two of my customers report the following error from a SQL stored procedure call in our application, running on SQL Server 2005. >> BEGIN ERROR A severe error occurred on the current command. The results, if any, should be discarded. Location: "xact.cpp":2630 Expression: !m_updNestedXactCnt SPID: 54 Process ID: 1732 Description: Trying to use the transaction while there are 1 parallel nested xacts outstanding Location: "xact.cpp":2788 Expression: !m_updNestedXactCnt SPID: 54 Process ID: 1732 Description: Trying to use the transaction while there are 1 parallel nested xacts outstanding Location: "xact.cpp":3851 Expression: !m_parNestedXactCnt SPID: 54 Process ID: 1732 Description: Trying to use the transaction while there are 3 parallel nested xacts outstanding Location: "xact.cpp":2879 Expression: !m_updNestedXactCnt SPID: 54 Process ID: 1732 Description: Trying to use the transaction while there are 1 parallel nested xacts outstanding << END ERROR I'm at a loss to determine what the cause of this is. Neither the application code nor the stored procedure are utilizing transactions around this call. The stored procedure does: 1. An OpenXML to get a list of keys it should act on from an input parameter 2. DELETE statements against a number of tables to delete all the data related to the specified keys. It appears to be very straight-forward. We've not yet been able to reproduce the error in house. - Are there any known operations or sequences of operations that could cause this? - Any known things that we might be doing wrong? - Any ideas on how to go about diagnosing this in the field? Thanks. -- - Shadow
From: Walt Butler on 18 Aug 2008 14:43 Any update on this one? I'm having the same problem (well, very very similar) "ShadowFRJ" wrote: > I've had two of my customers report the following error from a SQL stored > procedure call in our application, running on SQL Server 2005. > > >> BEGIN ERROR > A severe error occurred on the current command. The results, if any, should > be discarded. > > Location: "xact.cpp":2630 > Expression: !m_updNestedXactCnt > SPID: 54 > Process ID: 1732 > Description: Trying to use the transaction while there are 1 parallel > nested xacts outstanding > Location: "xact.cpp":2788 > Expression: !m_updNestedXactCnt > SPID: 54 > Process ID: 1732 > Description: Trying to use the transaction while there are 1 parallel > nested xacts outstanding > Location: "xact.cpp":3851 > Expression: !m_parNestedXactCnt > SPID: 54 > Process ID: 1732 > Description: Trying to use the transaction while there are 3 parallel > nested xacts outstanding > Location: "xact.cpp":2879 > Expression: !m_updNestedXactCnt > SPID: 54 > Process ID: 1732 > Description: Trying to use the transaction while there are 1 parallel > nested xacts outstanding > << END ERROR > > I'm at a loss to determine what the cause of this is. Neither the > application code nor the stored procedure are utilizing transactions around > this call. The stored procedure does: > > 1. An OpenXML to get a list of keys it should act on from an input parameter > 2. DELETE statements against a number of tables to delete all the data > related to the specified keys. > > It appears to be very straight-forward. We've not yet been able to reproduce > the error in house. > > - Are there any known operations or sequences of operations that could cause > this? > - Any known things that we might be doing wrong? > - Any ideas on how to go about diagnosing this in the field? > > Thanks. > > -- > - Shadow
From: Erland Sommarskog on 18 Aug 2008 17:58 Walt Butler (WaltButler(a)discussions.microsoft.com) writes: > Any update on this one? I'm having the same problem (well, very very > similar) So much I can say that it looks like a bug in SQL Server, or else you would not get these stack dumps. But I suggest that you post the output of SELECT @@version, the error messages you get and as much as information you can provide. The original poster had his problem at a customer site, and was not able to reproduce it in-house. Maybe you have more direct access to the issue? -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|
Pages: 1 Prev: Check Reporting Services Installation Programmitcally Next: Need help with a hard SELECT STATEMENT. |