>I'm running Visual Studio 2005 on a Windows XP machine connecting to a SQL
>Server 2000 database on my local machine.  I recently added some transaction 
>processing logic to my application using the TransactionScope object.  While
>stepping through my application in the debugger, I receive the above error. 
>If I run the application outside the debugger I don't receive the error.  For
>that matter, if I "quickly" step through my application (i.e.  minimize the
>number of breakpoints), I don't receive the error either.  This is my first
>experience using the TransactionScope object, so pardon my ignorance.  Any
>suggestions?
>
>Thanks.

"Mary Chipman [MSFT]" wrote:

> Here's what I found:
>
> XACT_E_NOTRANSACTION
> The transaction cannot be aborted because it already had been
> implicitly or explicitly committed or aborted. This call was ignored.
>
> I don't know why debugging triggers this error. Does it occur before
> or after you set the scope complete?
>
> --Mary
>
> On Thu, 16 Mar 2006 08:21:29 -0800, Lynne
> <Ly***@discussions.microsoft.com> wrote:
>
> >I'm running Visual Studio 2005 on a Windows XP machine connecting to a SQL
> >Server 2000 database on my local machine.  I recently added some transaction 
> >processing logic to my application using the TransactionScope object.  While
> >stepping through my application in the debugger, I receive the above error. 
> >If I run the application outside the debugger I don't receive the error.  For
> >that matter, if I "quickly" step through my application (i.e.  minimize the
> >number of breakpoints), I don't receive the error either.  This is my first
> >experience using the TransactionScope object, so pardon my ignorance.  Any
> >suggestions?
> >
> >Thanks.
>

>It occurs before I set scope to complete thereby causing the transaction to
>fail.
>
>"Mary Chipman [MSFT]" wrote:
>
>> Here's what I found:
>>
>> XACT_E_NOTRANSACTION
>> The transaction cannot be aborted because it already had been
>> implicitly or explicitly committed or aborted. This call was ignored.
>>
>> I don't know why debugging triggers this error. Does it occur before
>> or after you set the scope complete?
>>
>> --Mary
>>
>> On Thu, 16 Mar 2006 08:21:29 -0800, Lynne
>> <Ly***@discussions.microsoft.com> wrote:
>>
>> >I'm running Visual Studio 2005 on a Windows XP machine connecting to a SQL
>> >Server 2000 database on my local machine.  I recently added some transaction 
>> >processing logic to my application using the TransactionScope object.  While
>> >stepping through my application in the debugger, I receive the above error. 
>> >If I run the application outside the debugger I don't receive the error.  For
>> >that matter, if I "quickly" step through my application (i.e.  minimize the
>> >number of breakpoints), I don't receive the error either.  This is my first
>> >experience using the TransactionScope object, so pardon my ignorance.  Any
>> >suggestions?
>> >
>> >Thanks.
>>