Copy data from My SQL Data base to Fabric

[Vamsi46816]

An exception occurred: We were unable to find a database provider with invariant name 'MySql.Data.MySqlClient.

I am trying to do copy data from MySQL database to fabric and I ended up with this issue. I have my on prem data gateway up and running and I have check the version of MYSQL COnnectors and machine.config file. it is all fine and I don't know what is the problen.
I finally ended up with this issue.

[burakkaragoz · Accepted solution]

Hi @Vamsi46816 ,

This error usually comes up if the MySQL .NET connector (MySql.Data.MySqlClient) isn’t installed on the same machine where your on-premises gateway is running. Even if you checked the connector version, make sure it’s actually installed on that server and restart the gateway service after installing.

You can download and install the official MySQL Connector/NET from the MySQL website. Once it’s installed, restart your on-prem data gateway service so it recognizes the change. Also, double-check that the “machine.config” file has the MySql.Data.MySqlClient entry. Sometimes the connector install doesn’t add it automatically.

If you already tried these, uninstalling and reinstalling the connector sometimes helps. Also, confirm that you’re not mixing 32-bit and 64-bit versions between the connector and the gateway.

Let us know if this helps or if you’re still having trouble.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[v-ssriganesh]

Hi @Vamsi46816,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-ssriganesh]

Hi @Vamsi46816,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-ssriganesh · Accepted solution]

Hi @Vamsi46816,
Thank you for reaching out to the Microsoft fabric community forum and thanks to @burakkaragoz for the helpful and detailed response.

Just to add to what’s already been shared since you’ve verified the connector installation and machine.config entries, and you're still facing the issue, it might be worth checking for any environmental factors that could interfere with the connector registration. For example, occasionally security software or group policy settings might restrict proper registry or config file updates, especially in corporate environments.

Additionally, ensure the gateway machine has been fully restarted after making these changes not just the service as that can help finalize certain system-level updates.

If the issue persists after these checks, feel free to share any recent logs from the gateway or Fabric activity, as that can give us more insight into where the failure is occurring.

If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

[v-ssriganesh]

Hi @Vamsi46816,
I hope the information provided has been useful. Please let me know if you need further clarification or would like to continue the discussion.
If your question has been answered, please “Accept as Solution” and Give “Kudos” so others with similar issues can easily find the resolution.
Thank you.

[burakkaragoz · Accepted solution]

Hi @Vamsi46816 ,

This error usually comes up if the MySQL .NET connector (MySql.Data.MySqlClient) isn’t installed on the same machine where your on-premises gateway is running. Even if you checked the connector version, make sure it’s actually installed on that server and restart the gateway service after installing.

You can download and install the official MySQL Connector/NET from the MySQL website. Once it’s installed, restart your on-prem data gateway service so it recognizes the change. Also, double-check that the “machine.config” file has the MySql.Data.MySqlClient entry. Sometimes the connector install doesn’t add it automatically.

If you already tried these, uninstalling and reinstalling the connector sometimes helps. Also, confirm that you’re not mixing 32-bit and 64-bit versions between the connector and the gateway.

Let us know if this helps or if you’re still having trouble.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

[suparnababu8]

Hello @Vamsi46816 

Can you please share your My SQL screenshot from where you are trying to migrate the data. Pls share the full screenshot of your My SQL database.

Thank you!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[Vamsi46816]

Hi suparnababu, 

Thanks for the response.  I think below details are enough to connect from fabric.

[suparnababu8]

Hi @Vamsi46816 

Your details are correct. But why it's throwing error. You can try Authentication kind as Windows Authentication. Let me know if it works.

Thank you!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!