Power BI service connecting to Windows AWS VM gateway and data source

[Dutchwan21]

Hi, very new user to Power BI. However, I have managed to install, configure and develop reports in Power BI Desktop, and then publish results to Power BI Server (Service). I have configured a Windows 2012 R2 server with Power BI gateway and MYSQL Connector net 8.0.30. Both seem to be working. 

In my Power BI service, the on premises gateway is working/running but when I attempt to connect the mysql data source (mysql db running on linux in Dreamhost) I get the following error:

Details: 2012VM: 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 

I have also configured my local device (laptop) similarly and everything works, but I need the data source available 24/7 and running a laptop like that is not ideal. 

I have researched this on the forums and followed all the advice to no avail. Is there something I am missing, or have not configured?

Please help. Thanks

[lbendlin · Accepted solution]

I didn't know 8.0.30 is out. What I do know is that 8.0.29 will not work with Power BI due to a known bug.  Not sure if they fixed that in 8.0.30, but it may be worth going back to the last known good configuration which is 8.0.28 .

[Anonymous · Accepted solution]

I am also experiencing this issue with 8.0.30. I will try going back to 8.0.28 to see if that works!

[lbendlin · Accepted solution]

I didn't know 8.0.30 is out. What I do know is that 8.0.29 will not work with Power BI due to a known bug.  Not sure if they fixed that in 8.0.30, but it may be worth going back to the last known good configuration which is 8.0.28 .

[Dutchwan21]

Thank you so much for your assistance lbendlin....that has fixed the issue within mintues. I wish I had posted 2 weeks ago. In all my research no-one advised that 8.0.29 contained a known bug, and 8.0.30 has obviously not fixed it as yet. Again thank you.