Forum Discussion
Impactful IndividualError in refresh on service using MySQL RDS data source
Hi Anonymous & 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
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 Anonymous & 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
Hi visheshjain ,
Thanks for reaching out to the Microsoft Fabric Community forum.
To troubleshoot the issue, Please try these stepsLog 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
Hi Anonymous & 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