Comments on: A new twist to the error: “Unable to enlist in the transaction.” http://www.wadewegner.com/2007/05/a-new-twist-to-the-error-unable-to-enlist-in-the-transaction/ From the whiteboard to the keyboard Sat, 04 Feb 2012 13:53:05 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Nelson Homer Talag http://www.wadewegner.com/2007/05/a-new-twist-to-the-error-unable-to-enlist-in-the-transaction/#comment-36 Nelson Homer Talag Wed, 27 Feb 2008 08:08:37 +0000 http://www.architectingwith.net/2007/05/10/ANewTwistToTheErrorUnableToEnlistInTheTransaction.aspx#comment-36 I would like to add on this article i encountered a similar problem regarding "Unable to enlist in the transaction" we have a setup where DTC was enabled ton both Biztalk and Database servers and the netbios was also setup correctly. however the documents remain to be unprocessed. the solution i found was regarding a setup in DTC. it seems that the DTC in W2k3 by default only allows secured RPC calls and my transactions are not being listed I just changed the following system registry: [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTC] "AllowOnlySecureRpcCalls"=dword:00000000 "TurnOffRpcSecurity"=dword:00000001 and everything worked well I hope this helps I would like to add on this article

i encountered a similar problem regarding "Unable to enlist in the transaction"

we have a setup where DTC was enabled ton both Biztalk and Database servers and the netbios was also setup correctly. however the documents remain to be unprocessed.

the solution i found was regarding a setup in DTC. it seems that the DTC in W2k3 by default only allows secured RPC calls and my transactions are not being listed

I just changed the following system registry:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTC]
"AllowOnlySecureRpcCalls"=dword:00000000
"TurnOffRpcSecurity"=dword:00000001

and everything worked well

I hope this helps

]]>