|
Home > Archive > Commerce Server General > April 2004 > New transaction cannot enlist in the specified transaction coordinator - Help!!!
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
New transaction cannot enlist in the specified transaction coordinator - Help!!!
|
|
| Michael N 2004-04-21, 10:38 am |
| We have a series of COM+ components which are called from ASP pages in
our application. The components are enabled for different levels of
Transactional Support - either "Supported", "Required", or "Not
Supported", depending on the specific component. When any of the
components which are enabled as "Required" try to initiate a
connection with the database we receive the following error:
Changepoint.Utility.Feature.Execute error '8004d00a'
New transaction cannot enlist in the specified transaction
coordinator.
If we modify all the COM+ Components to be "Not Supported" rather than
"Required" we do not receive the error. The COM+ components are on a
Windows 2003 box, trying to connect to an instance of SQL Server 2000
(which is installed on a Windows 2000 box). The 2 servers are in the
same domain, but on different segments of the network. There is a
firewall between the COM+ server and the SQL server, so we have opened
a range of ports as per Microsoft's recommendations and modified the
registry with the following information:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Rpc\Internet]
"PortsInternetAvailable"="Y"
"UseInternetPorts"="Y"
"Ports" =hex(7):35,00,30,00,35,00,30,00,2d,00,35
,00,31,00,30,00,30,00,00,00,0
0,\
00
The Hosts file on the COM+ server and the SQL server have been updated
with a reference to each other's IP address
| |
| Alan Cherry 2004-04-29, 1:37 pm |
| For Windows 2003, you may need to enable Network DTC access.
See 817064 HOW TO: Enable Network DTC Access in Windows Server 2003
http://support.microsoft.com/?id=817064 for more information.
Alan Cherry, MCSE, MCP+I
Microsoft Developer Support Internet - Integration CPR
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security
This posting is provided “AS IS” with no warranties, and confers no rights.
You assume all risk for your use. © 2004 Microsoft Corporation. All rights
reserved.
--------------------
From: "Michael N" <mnormjr@hotmail.com>
Subject: New transaction cannot enlist in the specified transaction
coordinator - Help!!!
Date: Wed, 21 Apr 2004 07:00:36 -0700
Lines: 31
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <eBEcFl6JEHA.3728@TK2MSFTNGP12.phx.gbl>
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: p60.n-sfpop07.stsn.com 199.107.158.60
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.commerceserver.general:13646
X-Tomcat-NG: microsoft.public.commerceserver.general
We have a series of COM+ components which are called from ASP pages in
our application. The components are enabled for different levels of
Transactional Support - either "Supported", "Required", or "Not
Supported", depending on the specific component. When any of the
components which are enabled as "Required" try to initiate a
connection with the database we receive the following error:
Changepoint.Utility.Feature.Execute error '8004d00a'
New transaction cannot enlist in the specified transaction
coordinator.
If we modify all the COM+ Components to be "Not Supported" rather than
"Required" we do not receive the error. The COM+ components are on a
Windows 2003 box, trying to connect to an instance of SQL Server 2000
(which is installed on a Windows 2000 box). The 2 servers are in the
same domain, but on different segments of the network. There is a
firewall between the COM+ server and the SQL server, so we have opened
a range of ports as per Microsoft's recommendations and modified the
registry with the following information:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Rpc\Internet]
"PortsInternetAvailable"="Y"
"UseInternetPorts"="Y"
"Ports" =hex(7):35,00,30,00,35,00,30,00,2d,00,35
,00,31,00,30,00,30,00,00,00,0
0,\
00
The Hosts file on the COM+ server and the SQL server have been updated
with a reference to each other's IP address
|
|
|
|
|