Article ID: 914375 - Last Review: October 9, 2011 - Revision: 3.0

FIX: You may receive an error message when you run a package that calls other child packages in SQL Server 2005 Integration Services

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
BUG #: 406357 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

On This Page

Expand all | Collapse all

SYMPTOMS

When you run a package that calls other child packages in Microsoft SQL Server 2005 Integration Services (SSIS), one or more of the child packages may fail. Additionally, you may receive the following error message:
Error: 2005-09-06 15:07:47.14
Code: 0xC001402C
Source: @PR018_SS8PR032 Connection manager "ETC"
Description: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.".
End Error
This problem occurs when the following conditions are true:
  • The TransactionOption property is set to the Required value.
  • You use the Microsoft OLE DB Provider for SQL Server on the source database and on the destination database. The databases are on the same server computer.
  • The Microsoft Distributed Transaction Coordinator (MS DTC) service is enabled.
Back to the top

CAUSE

This problem occurs because only one request can own a transaction at a time. Therefore, when a transaction enlistment request occurs on the specific transaction that is running, the transaction enlistment fails.
Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089  (http://support.microsoft.com/kb/913089/ ) How to obtain the latest service pack for SQL Server 2005
Back to the top

WORKAROUND

To work around this problem, you can rely on implicit transaction management and set the TransactionOption property to the Supported value.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 1.
Back to the top

MORE INFORMATION

The scope of the fix is the Data Flow task level. If you have multiple Data Flow tasks that will join a distributed transaction, you may still encounter the error described in the Symptoms section. After you install the hotfix or SQL Server 2005 Service Pack 1, you can avoid the problem and use the fix by moving these connections and tasks that are spread across multiple data flow tasks into a single data flow task. This hotfix will still use parallel execution and avoid the problem. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
Back to the top
Keywords: 
kbsql2005ssis kbsql2005sp1fix KB914375
Back to the top