Re: SQL error
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Wed, 06 Sep 2006 13:35:30 -0600
It will work. How to address your situation depends on what
operating systems are involved. By default, some of the OSes
won't allow network transactions even if MSDTS is running on
both computers and even if no firewall is involved. Just
taking a guess, maybe the following applies and addresses
your issue:
You may receive a 7391 error message in SQL Server 2000 when
you run a distributed transaction against a linked server
after you install Windows Server 2003 or Windows XP Service
Pack 2
http://support.microsoft.com/?id=839279
-Sue
On Fri, 1 Sep 2006 08:24:02 -0700, Simon
<Simon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am attempting to run a stored procedure which inserts data on a remote
server but I`m getting the following
Server: Msg 7391, Level 16, State 1, Procedure ETrackerExportRoutine, Line 38
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].
MSDTC is clearly stopping the insert running inside a transaction. I am
running this on a SQL2000 standard edition box. Is there anyway to make this
work?
Si
.
- Prev by Date: Re: trouble with SSIS CPackage::LoadFromXML fails.
- Next by Date: Re: SQL linked server with ODBC
- Previous by thread: Re: SQL error
- Next by thread: SQL linked server with ODBC
- Index(es):
Relevant Pages
|
Loading
