January 6, 2005 at 6:44 am
Hi,
We are experiment an error when try to use a transaction in a linked server with the statement OPENQUERY.
e.g.
This query returns the error bellow:
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
I think this error occur because in my developer environment the "linked servers" are both in the one server only. In my production environment this error not occurs, probably because the servers are different computers.
January 6, 2005 at 7:05 am
We've seen this situation with a "loopback" linked server, which is what your setup is. The following Microsoft article contais a different 7391 error than what you've posted, but we received the same error you did:
INF: Troubleshooting Linked Server Error 7391 (306212)
Under Supportability Issues is where MS points out distributed transactions on loopback linked servers are not supported.
K. Brian Kelley
@kbriankelley
January 7, 2005 at 4:14 am
Thanks Brian,
I should wish a solution for this case, but at least I can explain to analysts the reason that isn't work in our developer environment.
Im my production environment the distributed transaction works fine.
- Thanks again.
- Regards
January 7, 2005 at 7:24 am
An option, if you have the capacity, is to setup a named instance and split the data sources back out in your development environment. It does mean the management of a second SQL Server, but if capacity is high enough on the existing development server, it does mean one less piece of hardware and one less OS to manage so there is some efficiency gained there.
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply