InvalidCastException on SSIS Package Execution

Discussion of issues, suggestions and bugs of Devart SSIS Data Flow Components, our product line for building SSIS-based ETL solutions, performing data access to popular cloud applications and databases.
Post Reply
twong
Posts: 4
Joined: Thu 21 Dec 2017 19:40

InvalidCastException on SSIS Package Execution

Post by twong » Fri 22 Dec 2017 15:20

I'm receiving the following error message when executing my SSIS Package (dtsx) on my 2014 SQL Server Instance

Code: Select all

				System.InvalidCastException: [A]Devart.SSIS.Salesforce.SalesforceConnectionManager cannot be cast to [B]Devart.SSIS.Salesforce.SalesforceConnectionManager. 
					Type A originates from 'Devart.SSIS.Salesforce.120, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701' in the context 'Default' at location 
						'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Devart.SSIS.Salesforce.120\v4.0_1.0.0.0__09af7300eec23701\Devart.SSIS.Salesforce.120.dll'. 
					Type B originates from 'Devart.SSIS.Salesforce.110, Version=1.0.0.1, Culture=neutral, PublicKeyToken=09af7300eec23701' in the context 'Default' at location 
						'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Devart.SSIS.Salesforce.110\v4.0_1.0.0.1__09af7300eec23701\Devart.SSIS.Salesforce.110.dll'.
My SSIS project is targeted to SQL Server 2012 which means the Devart Lookup controls I'm using are the 110 version. If I change the target to "SQL Server 2014", the controls are then the 120 version and I don't have this casting issue anymore. However, I have 30 other SSIS projects that are running into this issue and I don't want to manually upgrade and recreate every package.

Is there a better/easier way to upgrade the controls?

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: InvalidCastException on SSIS Package Execution

Post by Shalex » Wed 27 Dec 2017 11:07

twong wrote:My SSIS project is targeted to SQL Server 2012 which means the Devart Lookup controls I'm using are the 110 version. If I change the target to "SQL Server 2014", the controls are then the 120 version and I don't have this casting issue anymore.
That is a recommended fix.
twong wrote:However, I have 30 other SSIS projects that are running into this issue and I don't want to manually upgrade and recreate every package.

Is there a better/easier way to upgrade the controls?
Unfortunately, there is no another way to fix the issue.

Post Reply