Search MSDN. I recall there being a problem with forward only cursors and
another transaction starting.

"ian" <ian.peacock@fabsys.com> wrote:
>
>Have you set all classes within MTS to either require or use transactions?
>If not and you try to read an unassociated transaction record in another
>class you will get the error below.
>I have found that if all classes have their transactions set correctly this
>removes this problem.
>
>Another cause is debugging, you can get an internal timeout and this will
>stop any further transactions, also causing the error below.
>
>
>"bennett" <bennett@waveshift.com> wrote:
>>
>>Yes, I refreshed the service but still the same error message.
>>
>>"DaveSatz" <davidsatz@yahoo.com> wrote:
>>>Not 100%, but is the Distributed Transaction Coordinator service running
>>on
>>>the SQL server ?
>>>--
>>>HTH,
>>>David Satz
>>>Principal Software Engineer
>>>Hyperion Solutions
>>>->Using SQL Server 7.0 SP3/6.5 SP5a/Cold Fusion 4.5.1 SP2/VSS
>>>(Please reply to group only - emails answered rarely)
>>>-----------------------------------------------------------------
>>>"Bennett" <bennett@waveshift.com> wrote in message
>>>news:3b49fcf2$1@news.devx.com...
>>>>
>>>> In our web application when a SQL connection is attempted to be opened
>>I
>>>get
>>>> an error message stating: "Microsoft OLE DB Provider for SQL Server:
>New
>>>> transaction cannot enlist in the specified transaction coordinator".
>
>>Has
>>>> anyone received this error before and if so how to correct? I appreciate
>>>> any help.
>>>>
>>>> Bennett
>>>
>>>
>>
>