I'm going to give the above a shot:


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


In which order should I reinstall components? (DATABASE, then
WEBSERVER?)


On Sat, 01 May 2004 20:08:28 -0400, ryanr@nni.com wrote:
[vbcol=seagreen]
>Two computer setup: a database/backend server && iis/frontend server.
>
>SQL Authentication.
>
>SQL Server is not part of a cluster.
>
>CS2002 is installed, SP2 and FP1.
>
>SQL SP3 has been applied, along with a number of Windows 2003 patches.
>
>When I attempt to access the last page of Retail2002 (checkout.aspx),
>the pipeline SaveOrderAs() does not save correctly, failing with the
>error below.
>
>The checkout pipeline was modified to accomodate an email
>confirmation, but the modifications have been removed to fix this
>error.
>
>We have been having trouble with the OLAP server, in the department of
>name resolution (disk or network error, intermittent) despite the fact
>that SQL server resolution is perfect (SP3 OLAP patch has been
>applied).
>
>SQL && OLAP have been published in AD.
>
>This is a transaction failure (from all appearances), and we noticed
>it just the other day. Any ideas how to track down what exactly the
>problem is, or how to fix it?
>
>This:
>
> [COMException (0x8004d00a): New transaction cannot enlist in the
>specified transaction coordinator. ]
>  ADODB.ConnectionClass.Open(String ConnectionString, String UserID,
>String Password, Int32 Options) +0
>
>concerns me, as all the strings have checked out, as well as
>permissions (as far as I can tell).
>
>Many thanks,
>Ryan
>
>
>On Fri, 30 Apr 2004 17:48:18 GMT, huanchixonline@microsoft.com (Jason
>Xu) wrote:
> 

[ Post a follow-up to this message ]