Bug #107316 MySQL 8.0.29 introduces a bug which prevents use of the Connector software
Submitted: 17 May 13:03 Modified: 11 Aug 15:05
Reporter: Marcus Harris Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S2 (Serious)
Version:8.0.29 OS:Windows (10 Enterprise (20H2))
Assigned to: CPU Architecture:x86 (OS Build 19042.1645)

[17 May 13:03] Marcus Harris
We use the MySQL Connector/Net software on a PC which whose dedicated purpose is to function as an on-premises data gateway for Power BI applications developed by our team.

Version 8.0.29 of the Connector/Net software was installed on the PC to support connectivity between the data gateway software and the MySQL DBs managed in our internal network.  Since that software was installed, it has never worked -- not once.  We consistently receive the following error every time we attempt to create a DSN on Microsoft's Power BI website (https://app.powerbi.com) or using the Microsoft Power BI desktop software installed directly on the machine:

Unable to connect: We encountered an error while trying to connect to . Details: "We could not register this data source for at least one of the gateway instances within this cluster. Please find more details below about specific errors for each gateway instance."Hide details
Activity ID:          fb9718c1-c632-4f1b-861e-c28248b0c2a1
Request ID:         89e553d9-fd68-4391-eeda-a49673a37acd
Cluster URI:        https://wabi-north-europe-redirect.analysis.windows.net/
Status code:       400
Error Code:         DMTS_PublishDatasourceToClusterErrorCode
Time:     Wed May 04 2022 18:04:29 GMT-0400 (Eastern Daylight Time)
Service version: 13.0.18173.56
Client version:   2204.4.11089-train
CSF Data Gateway (Testing):       Unable to connect to the data source undefined.
Underlying error code:  -2147467259
Underlying error message:          MySQL: We were unable to find a database provider with invariant name 'MySql.Data.MySqlClient'. This error could've been the result of provider-specific client software being required but missing on this computer. To download client software for this provider, visit the following site and choose the 64-bit (x64) version of, at minimum, 'MySQL Connector/Net': https://go.microsoft.com/fwlink/?LinkId=278885
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.ClientLibraryName: MySQL Connector/Net
Microsoft.Data.Mashup.ValueError.DataSourceKind:       MySql
Microsoft.Data.Mashup.ValueError.DataSourcePath:       csfci.ih.lucent.com;harrism
Microsoft.Data.Mashup.ValueError.DownloadLink:          https://go.microsoft.com/fwlink/?LinkId=278885
Microsoft.Data.Mashup.ValueError.Reason:        DataSource.MissingClientLibrary

The problem here is there are no problems with any of the resources installed on that machine.  The MySQL drivers are there and should be visible to the Power BI application, but for whatever reason they are not.  This issue has been raised w/Microsoft's Power BI support organization and they are unable to determine why this is happening, either.

We always maintain a backup on-premises data gateway machine in our network, so after multiple failures using 8.0.29 on three different PCs, I did a quick version check on the backup gateway box because it's the only one functioning as expected.  That's where we saw it.

Version 8.0.28 of the Connector/Net software works perfectly with the on-premises data gateway software on the backup machine.

To test this, I took the following steps on two of the other three (3) machines we've tried testing 8.0.29 on:

1. Uninstall Connector/Net 8.0.29.
2. Reboot the target machine.
3. Download and install Connector/Net 8.0.28 (from the MySQL archive area).
4. Use the Power BI Desktop software to create a local DSN connection to our MySQL DB.
5. Create a DSN for the target data gateway via the Power BI website (https://app.powerbi.com).

In both cases we've tested thus far, uninstalling 8.0.29 and installing 8.0.28 worked perfectly.  No issues.

Something is wrong w/8.0.29 and it needs to be reviewed.

How to repeat:
1. Install 8.0.29 on the target machine.
2. Attempt to create a DSN (User or System -- it doesn't matter) connecting to a MySQL database on the local network.

In each of our test cases, we never got to a screen which allowed us to enter the server address, login, or password.  The errors showed up before any of that happened.

Suggested fix:
I have no idea?  There's got to be something in that point release that's significant enough to hide the availability of that software from the applications seeking to use it?
[19 May 11:47] MySQL Verification Team
Hello Marcus Harris,

Thank you for the bug report.

Ashwini Patil
[13 Jun 17:55] Philip Zubaly
I have an issue with the 8.0.29 .NET Connector which also may be at the root of this problem.  I upgraded to 8.0.29 from 8.0.20, and after that, my applications could not find the provider.  I found that the reason is that the <system.data><DbProviderFactories> section of the machine.config was cleared when I installed 8.0.29.  

I then removed the 8.0.29 connector and reinstalled it with the same results.  Then I removed the connector again and installed the 8.0.28 connector and the required DbProviderFactories entry was written into the machine.config properly.  I will be moving to 8.0.28 instead of 8.0.29 because of this issue.
[20 Jun 9:13] Michael Shparber
Same here! Thanks for this post!
[7 Jul 10:54] Stuart Cuthbertson
Just want to add that I'm also affected by this bug. Recently set up Power BI Desktop on a new laptop, and installed the Connector/NET v8.0.29 as the current version, in order to use a MySQL source with PBI Desktop. No success, all the same symptoms as previously noted here - and as soon as I uninstalled and installed .28 instead, it worked fine.
[28 Jul 20:28] William Lob
This remains an issue with 8.0.30.

Removal of 8.0.30 and replacement with 8.0.28 version of Connector/NET resolves the issue, similarly to reports for 8.0.29.
[1 Aug 6:02] Sam Benson
And I thought upgrades were supposed to fix bugs.
[1 Aug 14:17] Daniel Valdez
Posted by developer:

Just wanted to let you know that this issue it's been addressed.
[1 Aug 15:38] Marcus Harris
Daniel (Valdez),

Thanks for your comment but you didn't mention either of these things:

1. Which release has the issue has been fixed in?  And...

2. When we can expect to be able to download the updated release and use it?

If you have this information available, can you share it with us?  Thanks!
[1 Aug 16:03] Daniel Valdez
Hi Marcus,

The fix is not yet available in any of the releases yet.
We will work on it to include it on the next release. Sadly we are not
permitted to share the release dates.

[1 Aug 16:49] Marcus Harris
Thanks, Daniel!  No worries!

Looking forward to seeing this issue finally resolved.  Have a great day!
[11 Aug 15:05] Christine Cole
Posted by developer:
Fixed as of the upcoming MySQL Connector/NET 8.0.31 release, and here's the proposed changelog entry from the documentation team:

Incomplete dependencies prevented Connector/NET from installing and
running properly.

Thank you for the bug report.