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 "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

[ Post a follow-up to this message ]

Mike,

I was getting a similar (though maybe not exactly the same) error when I
deployed a working (on Windows 2000 Server) Commerce Server 2002 solution to
a set of Windows 2003 servers (two web servers and one data server). In my
case I didn't have a firewall between the web servers and the data server
and I don't remember if the error was a Changepoint.Utility.Feature.Execute
error - just that it was a "New transaction cannot enlist in the specified
transaction coordinator" error. So, for whatever it's worth, my problem was
resolved by enabling both Network COM+ Access and Network DTC Access on both
the web servers and the data server using Add/Remove Programs. You might
want to give that a try. I don't know the why's and wherefore's of this
solution. It's what I got to by working the issue through Microsoft Priority
Support.

Good luck.

Zoe

"Mike Norman" <mnormjr@hotmail.com> wrote in message
news:f6ef8308.0404210544.5795f9ad@posting.google.com...
> 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 "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

[ Post a follow-up to this message ]