Error in refresh on service using MySQL RDS data source

[visheshjain]

Hello everyone,

My data source is MySQL hosted on AWS RDS, for all my tables.

There are 2 main tables, 1 with 6.8 million rows and another with 2.5 million rows, amongst few other small tables with 200,000 rows, 65000 rows and few more lookup tables with less than 100 rows.

I have published the report to service and I am getting this error for the refresh.

The MySql source doesn't support encrypted connections. The exception was raised by the IDbCommand interface.

I want to refresh the report on the service WITHOUT USING A GATEWAY.

I have checked the PBI desktop file and removed encryption from data source settings but still I am getting the refresh error in Service.

Please can someone help me fix this issue.

If you want any further details, please let me know.

Thank you,

Vishesh Jain

[v-nmadadi-msft]

Hi @visheshjain 

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.

Thank you.

[visheshjain]

Hi @v-nmadadi-msft & @collinq 

I have gone over the information provided and as per your suggestions, I am trying to configure the data source in the gateway.

However I am getting this error.

I have connected Power BI desktop to the SQL db and the credentials are correct as well, yet I am seeing this error.

Please provide if you have any further suggestions.

Thank you,

Vishesh Jain

[v-nmadadi-msft]

Hi @visheshjain  ,
Thanks for reaching out to the Microsoft Fabric Community forum.

To troubleshoot the issue, Please try these steps

Log on to the SQL server itself and test the SQL connectivity directly from that machine. Use a tool such as SSMS or sqlcmd, and make sure you connect using the same server name, the same authentication method, and the same credentials that you configured in the gateway data source. This step is critical because the connection fails from the SSMS server, it will also fail when the gateway attempts to connect.

Additionally, to test if the gateway has access to all the required ports, run the network ports test. The results of the test are either Completed (Succeeded) or Completed (Failed, see last test results). If the test succeeded, your gateway successfully connected to all the required ports. If the test failed, your network environment might be blocking these required ports and servers.
Troubleshoot the on-premises data gateway | Microsoft Learn


I hope this information helps. Please do let us know if you have any further queries.
Thank you

[visheshjain · Accepted solution]

Hi @v-nmadadi-msft & @collinq 

Thank you for taking the time to respond to the issue.

So the gateway has been configured properly and the refresh has worked, but with minor tweaks to your suggested solutions.

Here are my findings and if anyone would like to add more then I'm all ears.

1. The 'Personal Cloud Connect' where a gateway is not required for the refresh, will probably work for small datasets but not a full fledged report. (This is my experience and I would like to hear any suggestions on how to eliminate the gateway WITHOUT COMPROMISING SECURITY)

2. Using the gateway works but you have to install a MySQL connector on the machine with the gateway, so that the gateway knows how to talk to the SQL server.

3. For MySQL install the .Net 8.4 connector and not the latest (as of Jan 2026) 9.0 connector.

4. Make sure you have only 1 MySQL connector installed, cause if 2 connectors are installed, the gateway might not know which one to use.

I hope this helps anyone else with the same issues.

Thank you,

Vishesh Jain

[collinq]

Hi @visheshjain ,

I do not think that you can refresh this without a gateway.  Power BI requires a gateway for MySQL connections.  If you don't want to use an ENTERPRISE gateway, and you have the right permissions, you can use a PERSONAL gateway but MySQL requires a gateway of some sort.

That said, if you really want to get into the weeds and try workarouns, you can expose MySQL endpoints to the cloud (huge potential security risk) or enable SSL or TLS on your MySQL server and create a certificate for it then you should be able to get around it as well.  I don't recommend either of those but if you absolutely do not want a gateway then those are workarounds that you can do.  BUT, as always, do so at your own risk!

[visheshjain]

Hi @collinq,

This is my configuration in the PBI service for the data source and I have entered the credentials in the 'Data Source Credentials' tab.

I tried something else; I removed all the tables except for the 6.8 million rows table and published it to the service with the same configuration and the refresh worked.

Are there any other suggestions that might be useful, apart from using a gateway?

Thank you,

Vishesh Jain

[v-nmadadi-msft]

Hi @visheshjain ,

You need to install the Oracle MySQL Connector/NET package before using this connector in Power BI Desktop. For Power Query Online (dataflows) or Power BI service, if your MySQL server isn't cloud accessible and an on-premises data gateway is needed, the component Oracle MySQL Connector/NET must also be correctly installed on the machine running the on-premises data gateway.

Power Query MySQL database connector - Power Query | Microsoft Learn

I hope this information helps. Please do let us know if you have any further queries.
Thank you