ZombieCheck()

Question

ZombieCheck()

Dave-175556

SSC Eights!

Points: 896
More actions
April 29, 2005 at 8:12 am

#86121

Hi Everybody,
We are using SQL Server 2005 Beta 2 and Visual Studio.Net 2005 Beta1
We are getting following error randomly. Anybody has any idea, wether it's bug or is there anything we can do to fix it.
[InvalidOperationException: This SqlTransaction has completed: it is no longer usable.]
System.Data.SqlClient.SqlTransaction.ZombieCheck() +31
System.Data.SqlClient.SqlTransaction.Rollback() +66
Thank you,

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Wayne Lawton Hall of Fame Points: 3532 More actions · Answer 1

Hi Dave,

A quick google search for "ZombieCheck" turned up exactly four hits. Based on the messages in your post, I suspect you may be dealing with the first one. It appears to be a server monitoring program.

http://wyae.de/software/mosshe/

I could also be completely wrong.

Hope this helps

Wayne

Chris Hedgate One Orange Chip Points: 25041 More actions · Answer 2

No answer to your question, however I would definitely recommend you to try and getting the April CTP of SQL Server 2005 and Visual Studio 2005 Beta 2 if you are doing any serious testing/preparations for the future products. A lot has changed since SQL B2 and VS B1.

--
Chris Hedgate http://www.hedgate.net/
Contributor to the Best of SQL Server Central volumes
Articles: http://www.sqlservercentral.com/columnists/chedgate/

Frank Kalis SSC Guru Points: 111183 More actions · Answer 3

There are also beta newsgroups where you can ask about this.

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

David-368560 SSC-Addicted Points: 438 More actions · Answer 4

Here's the fix and explanation:

http://support.microsoft.com/kb/912732

Stuart Meeks Valued Member Points: 61 More actions · Answer 5

I was having the same issue. I managed to solve it by increasing the CommandTimeout property on my SqlCommand object. The error was only occuring on one machine which was fairly low spec.

My theory for the actual error is the SqlCommand object timed out and rolled back itself (before the catch block). The exception was raised and my catch block tried to roll back the transaction again causing the "already competed" error.

I'm open to other theories, though as it'll help me narrow down the root cause.

Note: I did try the fix posted above to no avail.

Enjoy!

Stu

satinderpal.singh Valued Member Points: 67 More actions · Answer 6

I am noticing the same behavior.

so far i am not able to resolve it. But on and OFF we see these errors. One more thing i am noticing in our system is that the whole system goes very very slow after zombiecheck errors. And after sometime the system starts running smooth on its own - may there is lot of load on the system causing more and more timeouts - not sure though.

the MS patch doesn't help in this.

Joseph M. Morgan SSC Journeyman Points: 90 More actions · Answer 7

My problem was similar, and it turned out that I was doing it to myself. I was running a bunch of scripts in a VS2008 project to create stored procedures. In one of the procs, I used a transaction. The script was executing the creation of the proc inside a transaction, rather than including the transaction code as part of the procedure. So when it got to the end without an error, it committed the transaction for the script. The .Net code was also using and then committing a transaction, and the zombie effect came when it tried to close the transaction that had already been closed inside the SQL script. I removed the transaction from the SQL script, relying on the transaction opened and checked in the .Net code, and this solved the problem.:-)