Article ID: 942665 - Last Review: October 26, 2007 - Revision: 1.1 FIX: You cannot run some SQL Server 2005 Integration Services packages in Business Intelligence Development Studio if you also run the same packages by using the Dtexec.exe utilityBug: #50001778 (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. In Business
Intelligence Development Studio, you run some Microsoft SQL Server
2005 Integration Services packages.
At the same time, you also run these packages by using the Dtexec.exe
utility. In this scenario, the execution of these packages fails intermittently. Additionally, you receive the following error message in the Dtexec.exe utility: Error:
DateTime Code: 0xC0014005 Source: Description: The connection type "ConnectionType" specified for connection manager "ConnectionManagerName" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. … Error: DateTime Code: 0xC0014005 Source: Description: The connection type "ConnectionType " specified for connection manager "ConnectionManagerName" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. End Error Error: DateTime Code: 0xC0010018 Source: Description: Error loading value "<DTS:ConnectionManager xmlns:DTS="www.microsoft.com/SqlServer/Dts <http://www.microsoft.com/SqlServer/Dts>"><DTS:Property DTS:Name="DelayValidation">-1</DTS:Property><DTS:Property DTS:Name="ObjectName">ConnectionManagerName</DTS:Property><DTS:Property DTS:Name="DTSID">{9239CBC7-B721-4E89-88" from node "DTS:ConnectionManager". CAUSEThis problem occurs because a race condition exists between the
Dtexec.exe utility and the Msdtssrvr.exe process. Therefore,
SQL Server 2005 Integration Services intermittently
cannot
enumerate connection managers. RESOLUTIONThe fix for this issue was first released in Cumulative Update 4. 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: 941450
(http://support.microsoft.com/kb/941450/LN/
)
Cumulative update package 4 for SQL Server 2005 Service Pack 2 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:937137
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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.
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: 941450
(http://support.microsoft.com/kb/941450/LN/
)
Cumulative update package 4 for
SQL Server 2005 Service Pack 2 REFERENCESFor 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
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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:935897
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems 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:
913089
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:http://go.microsoft.com/fwlink/?LinkId=71711
(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:822499
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the
following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates | Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
