Skip to main content

Google Search

Custom Search

Live Search

Yahoo Search


Search the web Search this site

Unable to Enlist in the Transaction

I recently received an error while trying to run a SSIS package in Visual Studio. The full error is seen as below.

Error: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction manager has disabled its support for remote/network transactions.".

This error is happening when a component with transactions try to connect and manipulate data on a remote server.

To avoid this error, two things can be done.

* Remove the transaction handling from the component. – This should be done only if the transactions are not required or as a temporary measure.

You can do this by selecting the properties of the component, also check the package properties to make sure transactions are not enabled at the package level.

For an explanation of the options please visit the URL.

* Configure the Distributed Transaction Coordinator (DTC).

For a component to work correctly with transactions, below two things are required.
1. Running Distributed Transaction Coordinator (DTC) Service

This service should be running on the database server the component connects to and on  the machine where the package is running. This will coordinate the work between two machines / servers.

This can be checked and started by going to Windows Services.

2. Properly configuring the security of DTC.

To make the DTC service work properly, it should be given permission as required. This can be done by opening the Component Services window. In the component services window, navigate to Component Services –> Computers –> My Computer –> Distributed Transaction Coordinator. Right click Local DTC and click on Properties to open properties window.

If you are intending to run any workloads with transactions via any external servers you should enable “Network DTC Access”.

Depending on the situation you should allow Inbound, Outbound or both transaction manager communication options.

For complete list of explanations on each property please refer the following URL.

Comments

Popular posts from this blog

"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication."

If you are getting the above error while trying to connect to a database, the reason is you are using Windows Authentication to login to the SQL Server while being in another untrusted domain. For example if the SQL Server machine is a member of the CompanyDomain and if you are in MyDomain or if you are in a Workgroup the you will face the above issue while trying to connect to the SQL Server.The connection string used in the web.config while the above error is generated is as follows.



<connectionStrings>  <addname="cnnStr"connectionString="Data Source=BI-SVR;Initial Catalog=BBIDatabase;Integrated Security=True"/></connectionStrings>



There are three ways to fix this problem.1. Use the SQL Authentication to login to the SQL Server.You can get this done by changing the connection string to use SQL authentication while connecting. But you need to know the credentials of an account which is having permissions to your required database or the System Admi…

Enabling Hibernate in Windows

Some server versions of Windows are having the hibernate feature disabled by default. So if you need to change the hibernation do the following simple steps.1. Click start and type “cmd” or type command in the search box.2. Then in the search results, right click the Command Prompt and click on Run as Administrator.3. If you are prompted by the user account control click continue.4. Then,To turn hibernation on in your machine type - “powercfg.exe /h on” or “powercfg.exe /hibernate on”To turn hibernation off in your machine type - “powercfg.exe /h off” or “powercfg.exe /hibernate off”5. Lastly you can exit the command prompt by typing “exit”.Sometimes you might get an error similar to the following while trying to enable hibernation.Hibernation failed with the following error: The request is not supported. The following items are preventing hibernation on this system.
        An internal system component has disabled hibernation. This means your machine is running roles or …

Enable Hibernation and Sleep in Windows Server 2008 R2

Normally when you install Hyper-V role in your server, it will disable sleep and hibernate facilities provided by Windows.But you can avoid this by doing some alterations to Windows.Hibernate and seep features are disabled when the Hyper-V service is started, so you can regain hibernate and sleep by changing the start parameter of the Hyper-V service (hvboot).To change,1. Open the registry editor by typing “regedit” in the run window.Locate the key,HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hvboot and then set the start value of it to 3.Start property can hold the following values.0Boot (Not supported by hvboot.)1System2Auto3On Demand4Disabled Now you will have the hibernate and sleep facilities until you start the Hyper-V services in your machine. 2. Type the following command in a command prompt window with administrative rights. sc config hvboot start= demand Note that there needs to be a space between the = sign and the word demand.