Article ID: 913817 - View products that this article applies to.
When you use Business Intelligence Development Studio to build a Microsoft SQL Server 2005 Integration Services (SSIS) package, you may experience the following behavior:
This behavior occurs because the installation of a third-party application or of a third-party driver may incorrectly set up the permissions of the registry subkeys under the
HKEY_LOCAL_MACHINE\Software\Classes\CLSIDsubtree. If the Component Category Manager encounters a registry key for which it does not have read permissions, it reports an access error and stops enumerating components. Therefore, the Component Category Manager cannot enumerate the SSIS components that have a CLSID that has incorrect permissions in the subtree.
Applications that are known to possibly cause this behavior are Lexmark printer drivers (Lexdrvx.dll) and Macromedia Flash. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/300491/ )FIX: Applications that use Component Categories Manager with non-Administrator credentials fail on Application Center
Service pack informationTo 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:
913089Note In SQL Server 2005 Service Pack 1, SQL Server will correctly report the error as follows:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
Could not enumerate the registered connections.
Even with the improved error message, you may still have to use the method in the "Workaround" section to help identify the problem registry keys and resolve the problem.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To work around this behavior, follow these steps:
http://technet.microsoft.com/en-us/library/bb490994.aspxTo use this C# code sample, you must compile it first. To compile this C# code sample, you can use the C# compiler (Csc.exe) or Microsoft Visual Studio .NET.
This behavior is by design.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Article ID: 913817 - Last Review: July 14, 2006 - Revision: 4.3