Linked Server and Distributed Transactions

We have a developer that is trying to do a distributed
transaction using a View that in turn uses a Linked
Server.
The Linked server is the MSSQL 2000 server, so both
databases reside on the same server.
She is receiving the following error:
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
provider returned message: New transaction cannot enlist
in the specified transaction coordinator.]
Has anyone see this error? Is it an Option in the OLE
DB Provider or a Linked Server Option that is the problem?
I am able to do distributed transactions inside a MSSQL
Trigger that goes out to an Oracle DB and inserts data,
without an error. So, I am not sure why MSSQL cannot
use a Linked Server for a "local" database connection?
Any help is much appreciated,
MarkHi Mark,
"Mark" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:016401c3c668$e315c8e0$a401280a@.phx.gbl...
> We have a developer that is trying to do a distributed
> transaction using a View that in turn uses a Linked
> Server.
> The Linked server is the MSSQL 2000 server, so both
> databases reside on the same server.
> She is receiving the following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
> provider returned message: New transaction cannot enlist
> in the specified transaction coordinator.]
> Has anyone see this error? Is it an Option in the OLE
> DB Provider or a Linked Server Option that is the problem?
> I am able to do distributed transactions inside a MSSQL
> Trigger that goes out to an Oracle DB and inserts data,
> without an error. So, I am not sure why MSSQL cannot
> use a Linked Server for a "local" database connection?
> Any help is much appreciated,
> Mark
>
Seems to be a Loopback-Situation.
See http://support.microsoft.com/?kbid=306212 and follow the Link "Loopback
Linked Servers"...
Patrick