Re: dreaded insert/exec MSDTC issue in virtual server 2005
- From: ericmoyto@xxxxxxxxx
- Date: 22 Mar 2006 12:42:11 -0800
I wish I could point you in the direction of an answer to resolve this
but I can only say that we are experiencing a similar issue. We have a
Windows 2003 SP1 web server that has been set up as a virtual server
and we are utilizing MSDTC on it to speak to a "real" Windows 2003
machine that is runing SQL2k with SP4. When we try to unitilize our
application it will not run because the web server can not "enlist in
the specified transaction coordinator." I hope someone does get a
resolve since we would like to know the solution also.
Gary wrote:
I created two virtual servers 2005 with os of windows server 2003 and SQL2K (
with SP4) installed. I tried to insert some rows into a local table returned
from a remote stored proc call like :
insert #RemoteData exec <RemoteServer>.<DB>.<owner>.<procname>
I can run exec the proc without the insert perfectly well. also
insert #RemoteData select * from <RemoteServer>.<DB>.<owner>.<table>
can work as well. But as I run the insert/exec, the MSDTC common error 7391
comes up
Server: Msg 7391, Level 16, State 1, Line 1
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 checked the local and remote side DTC status( both is running), I enabled
Network Access following the steps from microsoft KB articles and restart DTC
and SQL server, I turn RPCSecurity off in registry), both servers are in the
same domain, there is no firewall setting. I run dtcPing in two sides, both
can communicate each other. Also inside the code, I set XACT_ABORT on, but
all these ways seem not resolved this issue.
Due to the fact that local and remote server are virtual server, I tried to
take a physical server as local/remote server ( which has the same
configuration as server 2003/sql2k), and one virtual server as remote/local
server . In this case, this insert/exec can work perfectly. BUT, if both
local/remote servers are virtual servers, insert/exec error always occurs.
Any pointer/suggestions is highly appreciated
.
- Prev by Date: Re: Save OLEObject "value" from MS Access db as MS Word doc
- Next by Date: Problem in dataset Filling...While Using OLEDB Connection...
- Previous by thread: Requirements to use COLLATE
- Next by thread: Problem in dataset Filling...While Using OLEDB Connection...
- Index(es):
Relevant Pages
|
|
