Select the product you need help with
FIX: Error message when you run a parent package that contains some child packages in SQL Server 2005 Integration Services: "Error: 0xC001000E"Article ID: 945893 - View products that this article applies to. Bug #: 50001905 (SQL Hotfix) 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. SYMPTOMSConsider the following scenario. You have a parent package that contains some child packages in Microsoft SQL Server 2005 Integration Services. Every child package contains a script task. The names of the script tasks are the same. Additionally, every script task uses a different connection manager. In this scenario, you may receive the following error messages when you run the parent package: Error: 0xC001000E at ParentPackageName:
The connection "ConnMgrName" is not found. This
error is thrown by Connections collection when the specific connection element
is not found. Error: 0xC001000E at ChildPackageName: The connection "ConnMgrName" is not found. This error is thrown by Connections collection when the specific connection element is not found. The script threw an exception: The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there. Error Code: 2: The script threw an exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. CAUSEThis problem occurs because of script caching. By default,
the prebuild binary of a script task is added to the assembly cache. However,
the assembly cache is not
automatically updated.
This
problem occurs
when
the child package that does
not run successfully is running the script of another child package that already ran successfully. RESOLUTIONThe fix for this issue was first released in
Cumulative Update 5. For more information about how to obtain this cumulative
update package for SQL Server 2005 Service Pack 2, click the following article
number to view the article in the Microsoft Knowledge Base: 943656 Note Because the builds are cumulative, each new fix release contains
all the hotfixes and all the security fixes that were included with the
previous SQL Server 2005 fix release. Microsoft recommends that you consider
applying the most recent fix release that contains this hotfix. For more
information, click the following article number to view the article in the
Microsoft Knowledge Base:
(http://support.microsoft.com/kb/943656/LN/
)
Cumulative update package 5 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL
Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to
an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that
is provided in a SQL Server service pack is included in the next SQL Server
service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
This fix introduces a new property for the Script Task called OptimizeScriptExecution which is set to True by default. After applying this fix, if you still continue to see the errors, consider setting this property to False. This property can be found on the Script Tab of the ScriptTaskEditior dialog. Setting this to False disables the cache and prevents the script binary from being reused during execution. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONFor more information about what files
are changed, and for information about any prerequisites to apply the
cumulative update package that contains the hotfix that is described in this
Microsoft Knowledge Base article, click the following article number to view
the article in the Microsoft Knowledge Base: 943656
(http://support.microsoft.com/kb/943656/LN/
)
Cumulative update package 5 for SQL Server 2005 Service Pack 2REFERENCESFor more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
935897 For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the
following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 945893 - Last Review: October 9, 2011 - Revision: 3.0 APPLIES TO
|
Back to the top
