|
|
This was _really_ annoying. The problem turned out to be
that DTC network access is disabled by default on server
2003 enterprise edition:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;329332
Even after I enabled on both machines I had to reboot the
SQL box to get things working.
I have no idea why DTCping worked just fine before
enabling.
Hope this helps someone avoid this in the future.
-Nick
HOB.com
>-----Original Message-----
>We're encoutering the often reported problem when trying
to save the basket:
>
>Error:
>New transaction cannot enlist in the specified
transaction coordinator.
>
>When we try:
>Dim mcs_form As
Microsoft.CommerceServer.Runtime.Orders.PurchaseOrder
>Dim mcs_bask As
Microsoft.CommerceServer.Runtime.Orders.Basket
>
>.... sucessfully run the pipelines ...
>
>mcs_form = mcs_bask.SaveAsOrder()
>
>Most of the posts on the groups relate back to a DTC
connectivity or firewall issue. These machines are not
seperated by a firewall and are on the same network
subnet with no filter at the switch etc. We downloaded
DTCping from microsoft and ran successfull tests on the
SQL server and the Commerce Server. RPCping also worked
perfectly both directions. The connection strings for the
Transaction Config and Transactions in commerce server
both seem to work correctly and report test successful
when we test them from with Commerce Server Manager.
>
>Commerce box is running: Commerce Server 02 Std. on
Windows 2003 Server - Web Edition with MDAC 2.8
>SQL box: SQL 2000 sp3 on Windows 2003 Std Edition
>
>Any ideas? Thanks for the help
>
>
>.
>
|
|