Event ID 12293: Transacted Commerce Server Pipeline Failure

• Microsoft Site Server version 3.0, Commerce Edition

SYMPTOMS

If shoppers are unable to complete purchases from your Site Server 3.0 Commerce Server Store, the following error may be displayed in the shopper's browser when they attempt to complete a purchase:

Commerce.MtsTxPipeline error '8004d00a' [STORE NAME]Component Execution failed for component[0x3] hr: 0x8004D00A ProgID: Commerce.SaveReceipt.1 The operation requested by the application is not allowed if the object is closed. [Microsoft][ODBC SQL Server Driver][SQL Server]MSDTC on server 'MACHINE NAME' is unavailable. /store/include/util.asp, line 126

Event ID: 12293 The description for Event ID ( 12293 ) in Source ( Microsoft Site Server 3.0 ) could not be found. It contains the following insertion string(s): [STORE NAME]Component Execution failed for component[0x3] hr: 0x8004D00A ProgID: Commerce.SaveReceipt.1 The operation requested by the application is not allowed if the object is closed. [Microsoft][ODBC SQL Server Driver][SQL Server]MSDTC on server 'MACHINE NAME' is unavailable.

Event ID: 12293 The description for Event ID ( 12293 ) in Source ( Microsoft Site Server 3.0 ) could not be found. It contains the following insertion string(s): Error loading the pipeline configuration data from the file: C:\Inetpub\wwwroot\store\config\purchase.pcf SQLItemAdo -- {1D265C80-77B2-11D0-8D58-00C04FD7A111} Server execution failed

Event ID: 12293 Commerce Server: Connection Error: Event ID: 0 The description for Event ID ( 0 ) in Source ( COM Contexts ) could not be found. It contains the following insertion string(s): Failed to enlist in DTC: SQL state 25S12, native error -2147168242, error message [Microsoft][ODBC SQL Server Driver]Distributed transaction error.

CAUSE

The errors listed in the "Symptoms" section typically indicate a problem running a Commerce Server pipeline component under the context of the Commerce.MtsTxPipeline package. The Commerce.MtsTxPipeline package has the option Requires a transaction enabled so if this package cannot enlist in a transaction, the pipeline component fails.

To test whether the Commerce Server pipeline component is failing as a result of a Transaction Server failure, run the failing Commerce Server pipeline component non-transacted.

To run the Commerce Server Pipeline Component non-transacted, open the Util.asp file or i_util.asp file in your Commerce Store and locate the following function:

function UtilRunTxPipe(file, orderForm, pipeContext)
    set pipeline = Server.CreateObject("Commerce.MtsTxPipeline") 

function UtilRunTxPipe(file, orderForm, pipeContext)
    set pipeline = Server.CreateObject("Commerce.MtsPipeline") 

RESOLUTION

The following steps list some methods for troubleshooting failures in the Commerce.MtsTxPipeline Transaction Server Package.

1. Follow steps 1 through 4 outlined in:

   Q191168 Failed to Enlist on Calling Object's Transaction

   If connecting to an Oracle database, follow all steps outlined in Q191168.



2. Make sure that the IIS Web Server and the SQL Server are using the same version of the Microsoft Distributed Transaction Coordinator (MSDTC). The version of the MSDTC can be determined by running the MS DTC Admin Console by selecting the Start button, Run, and then typing DAC. Make sure that both computers are using the latest version of the MSDTC. The most recent version can be downloaded from

   ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/NT4_SP6/i386/dtcsetup.exe




3. Reset the DTCLog from the Advanced tab of the MS DTC Admin Console. On a busy server, consider increasing the log size.



4. Run DCOMCNFG by selecting the Start button, Run, and then selecting the Default Security tab. Edit the Default Access Permissions. Note that the local admins group might not be in there. If it is not there, add it. By default, the local administrators group is not in the list of Default Access Permissions!



5. Open the NTOP MMC, select Transaction Server, Computers, My Computer, and then Packages Installed. Right-click on the System Package and select Properties. Select the Identity tab. If the default identity is set to Interactive user (whoever is currently logged on), change this to a valid account, preferably one in the local administrators group.



6. Are IIS and/or SQL on a cluster? Cluster changes DTC's behavior. Test name resolution BETWEEN servers *within* the cluster.



7. For information on changing SQL Server 6.5's priority boost if using SQL 6.5 see the following knowledge base article:
   
   

   Q229019 12293 Errors Occur when SQL Server Priority Boost Is Changed




8. Use RPCPing to test RPC connectivity between IIS and SQL, see the following knowledge base article:
   
   

   Q167260 XCLN: How to Use RPCPing to Test RPC Communication

   If RPCPing fails in either direction:
   
   • Is there a firewall between the Web server and the SQL Server? This may disrupt RPC Communication which is required by MSDTC. Check

     http://www.microsoft.com/com/wpaper/dcomfw.asp

     for the proper procedure for configuring DCOM/RPC through a firewall.
   
   
   
   • Since RPC connections are authenticated, check for PDC/BDC availability. Is a PDC/BDC "local" to both the IIS *and* SQL server? Or, does either server have to contact a PDC/BDC across a slow LAN/WAN link?
   
   
   
   • If RPC communications are still failing, it may be necessary to obtain a sniff trace of the network traffic between the IIS Web Server and the SQL server. See the following knowledge base article for instructions on using the Network Monitor:
     
     

     Q148942 How to Capture Network Traffic with Network Monitor

   
   
   



9. Paste the following script into Notepad and save as Default.asp. Place Default.asp into a virtual directory on an IIS web server and navigate to Default.asp from a browser. This script assumes that you have a DSN on the IIS server called pubs pointing to the pubs database, username sa and no password. This script tests the your IIS Server's ability to make a transacted database call with ADO. If this fails then the problem is MTS specific, not Commerce Server specific.




<%@ TRANSACTION = Required %>
<% Response.Buffer = True %>

<%
    REM -- Constants

    REM -- ADO command types
    adCmdText       = 1 
    adCmdTable      = 2 
    adCmdStoredProc = 4
    adCmdUnknown    = 8

    REM -- ADO cursor types
    adOpenForwardOnly = 0
    adOpenKeyset      = 1
    adOpenDynamic     = 2
    adOpenStatic      = 3

    REM -- ADO lock types
    adLockReadOnly        = 1
    adLockPessimistic     = 2
    adLockOptimistic      = 3
    adLockBatchOptimistic = 4

    REM -- Create ADO Connection and Command Objects
    Set conn = Server.CreateObject("ADODB.Connection")
    Response.Write "Connection Created.<br>"

    conn.Open "DSN=pubs;UID=sa;PWD=;"
    Response.Write "Connection Opened.<br>"
    
    Set cmdTemp = Server.CreateObject("ADODB.Command")
    Response.Write "Command Created.<br>"
    
    cmdTemp.CommandType = adCmdText
    Set cmdTemp.ActiveConnection = conn
	cmdTemp.CommandText = "select * from authors where au_id = '172-32-1176'"
	Response.Write "Command Initialize.<br>"
	
	set rs = Server.CreateObject("ADODB.Recordset")
	Response.Write "Recordset Created.<br>"
	
	rs.open cmdTemp
	Response.Write "Recordset Opened.<br>"

	lname = rs("au_lname")
	
	rs.Close 
	set rs = nothing
	Response.Write "Recordset Closed and Released.<br>"
	
	set cmdTemp = nothing
	Response.Write "Command Released.<br>"
	
	if lname = "White" then
		conn.execute "update authors set au_lname = 'Black' where au_id = '172-32-1176'"
	else
		conn.execute "update authors set au_lname = 'White' where au_id = '172-32-1176'"
	end if   
	
	conn.Close 
	set conn = nothing 
	Response.Write "Connection Closed and Released.<br>"

	' Display this page if the transaction succeeds.
	Sub OnTransactionCommit()
		Response.Write "<HTML>"  
		Response.Write "<BODY>"
		Response.Write "Transaction completed. Name was changed."
		Response.Write "</BODY>"  
		Response.Write "</HTML>"  
		Response.Flush()
	end sub

	' Display this page if the transaction fails.
	Sub OnTransactionAbort()
		Response.Clear()  
		Response.Write "<HTML>"  
		Response.Write "<BODY>"
		Response.Write "Unable to complete your transaction."
		Response.Write "</BODY>"  
		Response.Write "</HTML>"  
		Response.Flush()
	End sub
%> 

MORE INFORMATION

Steps to Reproduce the Behavior

Additional query words:

Keywords : prodCS
Version : winnt:3.0
Platform : winnt
Issue type : kbprb