Currently in an operation of the project we're doing, we use distributed transactions, everything fine until it came time to test everything and was there when ouchh! Sunday, November 9, 2008
Battery Blanket Camping
Problems and Visual Studio 2008 SP1 SCSF
Currently in an operation of the project we're doing, we use distributed transactions, everything fine until it came time to test everything and was there when ouchh!
Currently in an operation of the project we're doing, we use distributed transactions, everything fine until it came time to test everything and was there when ouchh! has been disabled network access for distributed transaction manager (MSDTC). Enable DTC for network access security settings for MSDTC using the Services administrative tool components. ---> System.Runtime.InteropServices.COMException (0x8004D024): The transaction manager has disabled its support for transactions or remote network. (Exception from HRESULT: 0x8004D024)
in System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction (propgationTokenSize UInt32, Byte [] propgationToken, managedIdentifier IntPtr, Guid & 
In my case the execution environment of the application is in network, ie the database server is on another computer. As Transaction Coordinator enabled in Windows Vista
In XP we can go to administrative tools and enter the service component and enable it, in this case, it was looking into administrative tools and it was nowhere to be seen and touches accessed via Execute: Run Type 
Once deployed within the console
Component Services-> Computers-> My Computer-> Distributed Transaction Coordinator And we have DTC (Distributed Transaction Coordinator), we'll right-click src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> their properties and that we enable the options you desire: 
Then we go to the Security tab and enable the corresponding properties, according to the environment in which we will work .
In my case I have enabled all without any restriction to do testing, but in a production environment will depend largely on the choices you have regarding network access and user privileges.
We'll get a message that has been restarted the service and since this all ready. It is necessary to mention that the Transaction Coordinator service is started, for it can go to the Services console and verify.
In a way we have set the Transaction Coordinator, now just need to give access through the firewall.
With this you can work quietly with our transactions. Additionally, they can review this article dealing
How to enable diagnostic tracing for MSDTC on a computer based on Windows Vista
Greetings! 
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment