Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100'
-
I'm getting the following pop up message whenever I'm trying to open a SSDT solution.
Note: I have already registered the Dts.dll, but it did not make any change, also I have update the visual studio to latest update 4.
I have registered the dll by using CMD to the below location and entering regsvr32 dts.dll, it brought up a popup message saying the dll the has been registered.
C:\Program Files\Microsoft SQL Server\100\DTS\Binn
But the issue remains the same, I have to click ok on the popup msg for about 20-30 times to make it go away and the dtsx package in the solution work just fine after closing the pop up.
Can any one please help me with a solution for this.
unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{203E24BD-5203-4C76-AFC7-7C8545EBA1A0}' 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)). (Microsoft Visual Studio)
-
vamsye (12/31/2014)
I'm getting the following pop up message whenever I'm trying to open a SSDT solution.Note: I have already registered the Dts.dll, but it did not make any change, also I have update the visual studio to latest update 4.
I have registered the dll by using CMD to the below location and entering regsvr32 dts.dll, it brought up a popup message saying the dll the has been registered.
C:\Program Files\Microsoft SQL Server\100\DTS\Binn
But the issue remains the same, I have to click ok on the popup msg for about 20-30 times to make it go away and the dtsx package in the solution work just fine after closing the pop up.
Can any one please help me with a solution for this.
unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{203E24BD-5203-4C76-AFC7-7C8545EBA1A0}' 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)). (Microsoft Visual Studio)
Quick thought, the 203E24BD-5203-4C76-AFC7-7C8545EBA1A0 is indeed the correct GUID for Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100 interface (2012), are all SSIS components properly installed on this system? Are you by any chance calling this from a scrip task?
-
I'm not calling via script task, this is a regular dtsx package and it does not even have any script components in it.
This pop up comes after the validations of the connection managers and data flow tasks have been completed.
-
vamsye (12/31/2014)
I'm not calling via script task, this is a regular dtsx package and it does not even have any script components in it.This pop up comes after the validations of the connection managers and data flow tasks have been completed.
Have you checked the SSIS installation?
-
I am getting the following error in SSIS Package when I first open it up
Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject100'. This operation failed because the QueryInterface call on the COM
My solution click the ok button as many times as the pop up goes away. It is very weird but it is what it is . Only it happens to me in one of my projects
- vamsye - Wednesday, December 31, 2014 8:52 AM
I had exactly same problem working with SSIS 2014. That error occurred during validation on load, and I had to bang on OK for a minute or so to get rid of this message.
My .dtsx was pretty populated with real estate broken into seven columns to the tune of 376 DFs. Then I looked more closely, and figured what columns of
DFs that error occurred - happened to be the column 3. I rechecked all DFs in that column, and here it is - one of DFs had yellow '!' in a triangle on Source OLE DB.
That meant discrepancy b/w output and exterior fields. Interestingly, that error did not stop .dtsx from being executed.
I redid the source (and Destination) OLE DB there - and voila!!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply