Hello,This is addressed to the SSIS team. I have found COM objects registration bug. The SQLTaskConnections.dll library has a couple of COM objects registered with invalid TypeLib element. If you search for GUID:EF6D5D2C-8F86-4DBE-90F9-0B289E9577C3You will find it in a couple of COM objects, but there is no such TypeLib registered. The correct TypeLib GUID should be:E8E2265A-7E92-486C-AC8F-5ECC9B22F7CAwhich I retrieved from the .tlb inside the library.I'm getting the error: Could not load file or assembly 'Microsoft.SqlServer.SQLTaskConnectionsWrap, Version=9.3.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.and I think it can be related. I have read somewhere that Microsoft has recently changed the way .NET Runtime-Callawable-Wrappers are dealing with COM objects and it is quite possible this update has broken libraries like this.Can you please someone forward this to the appropriate person responsible.Thank you,Ivan

For starters, if you think you've found a bug, please post it on http://connect.microsoft.com/sqlserver/feedback.

Did anything ever come of this bug (or reported bug)? I am receiving the same error message in SSIS when trying to import from a flat file. I am running 2005 SP2 on my local workstation. I have uninstalled and reinstalled Integration Services already.

We have reported the bug here. It will probably be included in the next SQL SP3 . You may try to manually patch the improper registration and see if it will resolve your issue.

Thanks for the reply! I am a DBA and not completely sure of what you mean by the manual patch. Would that be to update the keys that match the EF* GUID with the one you supplied ( E8*)? Thanks again!

Yes. You should edit your registry and replace each and every instance where you find the invalid GUID with the correct one.

how do we do that?