MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

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
Christian P
Posts: 5
Joined: Sun 24 May 2020 14:17

MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Christian P » Wed 27 May 2020 04:35

Hi,

I have installed the latest Devart connection manager for MySQL on a Windows Server 2016 and SQL 2019 Standard Edition. Using VisualStudio SSDT 15.9.23. I am getting below errors in SSDT when the project is configured as TargetServerVersion SQL 2019.

[SSIS.Pipeline] Error: The component metadata for "Devart MySql Source, clsid {7CDF593F-DE06-4ABD-B356-7976EF7AC8E0}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.


[SSIS.Pipeline] Error: Cannot find the connection manager with ID "{0C741C0F-3F7D-4445-9701-AF271F8ADBB0}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "Devart MySql Source.Connections[Devart MySql]" in the connection manager collection of "Devart MySql Source". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.

In above case, I created a clean project with TargetServerVersion SQL 2019, and added the connection to a package.
However if I create a project with TargetServerVersion SQL 2017 it works except when running as a SQL Server Job.

I can see that there is Devart.SSIS.MySql.150.dll in the Assemblies folder. Could it be that SSDT is selecting the wrong dll when in TargetServerVersion SQL 2019 or what I am missing?

Update:
I can see that the right .dll is used but it still doesn't work.
Devart.SSIS.MySql.MySqlSource, Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701
Last edited by Christian P on Tue 02 Jun 2020 20:27, edited 1 time in total.

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

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Shalex » Thu 28 May 2020 20:13

Our product line includes two products with SSIS functionality for MySQL. The code generated by one product will not work with another product:

"SSIS Data Flow Components for MySQL"

Code: Select all

name="UserComponentTypeName">Devart.SSIS.MySql.MySqlDestination</property>
name="UserComponentTypeName">Devart.SSIS.MySql.MySqlSource</property>
"dotConnect for MySQL Professional"

Code: Select all

name="UserComponentTypeName">Devart.SSIS.MySql.MySqlDestination, Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701</property>
name="UserComponentTypeName">Devart.SSIS.MySql.MySqlSource, Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701</property>
1. You have created your package with "dotConnect for MySQL Professional", but now trying to use it with "SIS Data Flow Components for MySQL". Is this correct? If so, you should recreate your package with "SIS Data Flow Components for MySQL".

2. Specify the capacity (x64 or x86) of your SQL Server 2019.

3. Make sure that the following assemblies are available on your workstation:

* "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Devart.SSIS.MySql.150\" (folder)

* "C:\Program Files\Microsoft SQL Server\150\DTS\Connections\Devart.SSIS.MySql.150.dll"
* "C:\Program Files\Microsoft SQL Server\150\DTS\PipelineComponents\Devart.SSIS.MySql.150.dll"

* "C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Connections\Devart.SSIS.MySql.150.dll"
* "C:\Program Files (x86)\Microsoft SQL Server\150\DTS\PipelineComponents\Devart.SSIS.MySql.150.dll"

Christian P
Posts: 5
Joined: Sun 24 May 2020 14:17

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Christian P » Tue 02 Jun 2020 21:09

Hi,

I resolved the SSDT issue with setting Run64BitRuntime to false for the project.

Answers to your questions
1) I have installed the SSIS Data Flow component from the devartssis.exe version 1.12.1167
2) SQL 2019 64-bit with CU4, Windows 2016 server with .NET framework 4.8
3) All assemblies are found in their respective folders

However, running the package as a job in SQL Server Agent is failing for me.

What I have noticed in the SSIS error log
Data Flow Task:Error: The managed pipeline component
"Devart.SSIS.MySql.MySqlSource,
Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=09af7300eec23701" could not be loaded.
The exception was: Could not load file or assembly
'Microsoft.SqlServer.PipelineHost, Version=15.100.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or
one of its dependencies. The system cannot find the file
specified..
Data Flow Task Data Flow Task (Devart MySql
Source [20])
Package:Error:
While on the server I can only find Microsoft.SqlServer.PipelineHost version 15.0.200
If this is the issue, from where can I find version 15.100 of this binary and update the server?

Cheers

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

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Shalex » Mon 08 Jun 2020 11:13

We will investigate the issue and notify you about the result.

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

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Shalex » Fri 19 Jun 2020 09:52

We have provided the internal build with the fix by email.

Christian P
Posts: 5
Joined: Sun 24 May 2020 14:17

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Christian P » Mon 22 Jun 2020 14:35

Thanks guys for resolving the issue! The re-install went perfectly and the SQL Agent Job runs now :-)

fgubabor
Posts: 1
Joined: Mon 29 Jun 2020 08:20

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by fgubabor » Mon 29 Jun 2020 08:24

Good day!

We have the exact same problem here. Would it be possible to get the "[...]internal build with the fix by email", too? Will the fix be included in the upcoming release, and when is this going to happen? Thank you very much!

Best regards,
Felix

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

Re: MySQL Connection Manager fails in project set with TargetServerVersion SQL 2019

Post by Shalex » Wed 01 Jul 2020 17:07

The internal build with the fix: https://download.devart.com/devartssis_1_13_1224.exe.

The fix will be included in the next public build as well. There is no timeframe at the moment.

Post Reply