This particularly happens, when using DirectSqlAccessor, and for example DB log get full

System.InvalidOperationException occurred
  Message=This SqlTransaction has completed; it is no longer usable.
  Source=System.Data
  StackTrace:
       at System.Data.SqlClient.SqlTransaction.ZombieCheck()
  InnerException:

I've sent you a test sample. This is a problem because this error hides the original error that has caused the transaction abort

asked Dec 13 '11 at 10:32

xumix's gravatar image

xumix
36914067

edited Dec 13 '11 at 10:35

As far as I can judge, the transaction is already rolled back at this point, so there is nothing to roll back. But case with hiding the original exception should be checked by us.

(Jan 18 at 00:18) Alex Yakunin Alex%20Yakunin's gravatar image

True. Exception hiding is THE problem, since it is impossible to discover the actual error

(Jan 25 at 04:05) xumix xumix's gravatar image

One Answer:

We'll fix the issue in one of nearest releases.

--
Truly yours,
Captain Obvious =)

answered Jan 26 at 02:22

Alex%20Yakunin's gravatar image

Alex Yakunin
2916111

edited Jan 26 at 03:04

Dmitri%20Maximov's gravatar image

Dmitri Maximov
180229

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA