Forum Discussion
Resolver IIOn-Premesis Gateway cannot connect to MySQl source
ibarrau and others I have finally managed to resolve this issue with the help of Microsoft.
First, there is no specific x64 version of the MySQL connector - there is a single .net connector available that works with both x86 and x64. Some people have reported having issues with some of the newer versions however, so potentially try different version numbers.Second, I've had conflicting stories on whether Personal Gateway needs to be removed however in my case it did. However, even after we had thoroughly removed personal gateway from our machine is still shows up in Power BI Service. This threw both us and the Microsoft support guys off for a little bit but to put it simply this can be ignored. The Personal Gateway will still show in Power BI Service but it isn't doing aynthing.
Regarding my specific problem, the issue was two-fold:
1. The connector was installed and being recognised by Power BI Desktop fine, however it wasn't being recognised by Power BI Service - the reason for this was that we had to restart the server with On-Premises on it. After restarting we starting making progress, so if you have not done that please do this first.
2. When you add a MySQL data source to your On-Premises connector in Power BI you must give it EXACTLY the same name as in your PBIX file.
When you connect to MySQL in Power BI Desktop you can't actually give the source a name (as far as I know) so you end up with a name similar to 43.21.34.10;database_name this is the exact name that you have to give your source in Power BI service. So both the Name and Server field will end up being identical.
Once you have done this you should be able to connect.
A couple of things to note:- Sometimes even when you think everything is configured correctly you will only have the option for a database to connect using On-Premises Personal (if you once had personal installed). This for me indicated that one or more of the data sources added to On-Premises gateway had been incorrectly named. Once all of the names matche up only then did On-Premises Gateway show up as an option.
- If you are transferring a PBIX file that was using Personal Gateway to use On-Premises gateway it will not work until ALL of the data sources are connected to On-Premises. You cannot connect if for example your MySQL connection is 100% accurate but a link to a OneDrive file is wrong.
Took a while but thankfully this is now working for us, hopefully the above helps someone.
Resolver IICan I just confirm, the error suggests installing a 64-bit verison of the connector, from what I can see there is only a 32-bit version which works on both - is this correct?
UPDATE:
I have tried testing my set-up a bit more and think there may be a deeper problem. I uninstalled Personal Gateway and then proceeded to create a completey new PBXI file.
From within that file I imported some data from a local Excel file stored in a OneDrive folder. I then published this new BI file to a brand new workspace that I created in Power BI service.
The initial update worked fine and data / reports were accessible, however when I try to refresh it fails. The message I get indicates that it is trying to refresh through the Personal Gateway despite this no longer being installed on any machines. Furthermore when I go to settings I cannot switch from the Personal to On-Premises Gateway.
Any ideas on how to completely clear out the Personal Gateway from Power BI Service?
Power ParticipantI found that the On-premises Gateway will not be enabled if any of the datasets cannot be connected to correctly by it. We did have a mySQL database to connect to but it was such a pain to try to set up that I created a SQL Server data warehouse with the relevant data in and queried that instead. Even then the SSIS connector is pretty flakey but at least I could get it to work okay.
Not that helpful I'm afraid but at least you know you are not alone.