When I open up my existing SSIS project, I always get this error. Does anyone know what was wrong ? TITLE: Microsoft Visual Studio------------------------------ Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.IObjectWithSite'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{FC4801A3-2BA9-11CF-A229-00AA003D7352}' failed due to the following error: The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)).

Did you get a solution to this problem? If so could you please post it?I'm having the exact same problem on my development server. Sincerely Svein Terje Gaup

I have the same problem as well, anyone know how to solve it? Many Thanks. Warren

i got it fixed without knowing how to fix it. it is kind of rediculous. Can anyone from SSIS team or any SSIS guru answer this ? Steve

I've no idea but it seems some realated with the apartment for a COM object, maybe STA which is being used in another thread. My wonder is why BIDS needs to make a RCW between managed code and unmanaged code when you're going toopen it.

Have seen this error several times opening BIDS. Just close BIDS and open it up again, error gone. Don't know why. I think it happens when I'm a little bit impatient and try to open a recent project while BIDS is not fully up and running yet. It's a bit annoying, but I don't think it'sa serious problem. Pipo1

Have this problem too - any fixes?

It seems SQL 2005 does not do a good job to tell us what the error is... Not sure if you guys did the same task I did, I got the same error when I tried to add a Maintenance Plan.I tried to find the reason/solution but no luck.. and I fixed it not because I found the answerand it is all about security... My story is... I set uptwo clustered SQL 2005 servers and tried to add a maintanience plan by using sa account authentication. However, sa account is not a network account but a SQL account. So I kept getting the error no matter I close/open how many times. And unfortunately SQL 2005 does not report this error "precisely" to me to identify where the problem is... So instead of using my local Management Tools and sa accoutn authentication, I logged in to another server on the same network domain as those two clustered servers.Then I used Management Tool installed on it and Window Authentication account which is the admin account of two clustered servers, and hahaha, it just works like I want it to. Hope this helps,Jet

HelloDoes anyone have the solution to this issue?Everytime I open a new SSIS package, i get the error"Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface...failed due to the following error: Interface not registered."Which interface do I need to register?Doesnt happen for other packages, only SSIS.Thanks!

To fix the problem do the following: 1. Open the command prompt 2. Navigate to C:\Program Files\Microsoft SQL Server\90\DTS\Binn 3. Run C:\Program Files\Microsoft SQL Server\90\DTS\Binn>regsvr32 dts.dll That should fix the problem.

CartoonKev's answeris the solution that worked for me. Thanks. Bob L AGD Chicago

Me too, thanks!

i too had the same issue! i think the problem is not with the studio or our local settings! let me explain my scenario. my OLEDB destination reffers to foriegn server. that server has got some power issues. so its down. in that time, SSIS designer unable to cast COM object in validation process. (its not an error, its an exception most probably not properly handled exception) because of that it shucks and hangs with an error message. after one day, the server has got fixed, and this error has gone! this is that wonder that happen to me! nice hug?

Hi CartoonKev, I can't find the C:\Program Files\Microsoft SQL Server\90\DTS\Binn>regsvr32 dts.dll - I have this error starting a brand new package. This is my first attempt. Any help is appreciated. CHS

Yes it worked by registering the DLL.Not sure what cause the DLL to become un registered on the server.

Awesome, Kev. That fixed the problem for me, but I still wonder why the dll became unregistered....

Awesome, Kev. That fixed the problem for me, but I still wonder why the dll became unregistered.... the dlls become unregistered by any service pack or asp.net framework installatio or uninstallation.

This Worked for Me ,Thanks Kev

This Worked too for Me ,Thanks Kevtr

Thank You. It solved the problem. Now I can created SSIS packages.Viral Dalia System/Network Administrator MCSA, MCSE, MCDBA, CCNA

Perfect solution. Fixed the problem.

The dts.dll is now in c:\Program Files\Microsoft SQL Server\100\DTS\binn in SQL Server 2008 (Enterprise evaluation version). Registering the DLL does not fix the problem on that version. You get the error when you create a new project in BIDS with the integration services template. This tempate creates a package in the solution explorer (*.dtsx). BIDS automatically attempts to open the package in the package designer and shows the COM error.

You will also get this error message if one or more of your data sources are not available. 1.) Make sure that the source server(s) are running. 2.) Make sure that the source table(s) are available. 3.) Make sure thet the current user has access to the source table(s).BalintN

I am having the same issue... registering dts.dll does not solve the problem in ver. 2008. Have you found any solution yet? Thx.