Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
I'm working on a model that pulls from various MySQL sources then combines tables, merge, appends and re-formats.
Recently I had to update PBI Desktop, MySQL, the .Net drivers and ODBC drivers as the MySQL connection didnt work. After doing this the connector worked again, HOWEVER, I am now seeing the following error:
DataSource.Error: An error happened while reading data from the provider: 'Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).'
Details:
DataSourceKind=MySql
DataSourcePath=[My internal data source]
The model has been working for months but all of a sudden after the updates it doesnt work. It seems to be whenever I change the format of a column, but also happens on Merge and Appends too.
If I roll back the versions, then I cant use the MySQL connector at all.
EDIT: This seems to be an intermittent issue, sometimes a table will refresh without issue but if I try again immediatley afterwards it fails with this error message.
EDIT 2: This error is not replicable in MySQL Workbench
HELP!
Hi @AndyCandy ,
It looks like you are encountering an error while trying to connect to a MySQL in Power BI. The error message you provided suggests that there is an issue with the format of a GUID in your data. One possible solution is to check the data in your MySQL database to make sure that all GUIDs have the correct format of 32 digits with 4 dashes. You may also want to check if there are any null values in the GUID column, as this can sometimes cause issues with data loading. Besides that, please try to refresh the data source or check your connection settings to ensure that they are correct.
Best Regards
Thanks for the reply, but I'm afraid its not helped. I'm not using a GUID in the connection or the query. This query worked for months and then suddenly broke with this error. No changes to the model or query.
I believe that this is a bug, rather than user error.
Hi @AndyCandy ,
Whether the problem still persist? What's the version of your Power BI Desktop? The underlying data source MySQL can work all the time? Is it the latest version?
Best Regards
Yeah, you're right, unworkable was harsh - It doesnt meet my needs would be a better way of describing it.
That said, I've been working with PBI for over 6 years I think, and I've never had the problems Ive had with the MySQL connector with most of the other methods I use. But, then again, I am asking a lot of it.
Which MySQL driver version? Try going back to 2.0.28
Thanks for the reply.
Unfortunatley if I roll back to any other version I get the error:
"MySQL: We were unable to find a database provider with invariant name 'MySql.Data.MySqlClient'."
64bit?
Yes - Both before the first change which lost my ability to use the MySQL Connector and then after the fix.
I've had to resort to pumping the data I need into an AzureBlobs storgae space instead because MySQL just isnt workable in PowerBI.
I'll leave this open and keep testing from my end in case anyone else can benefit.
"unworkable" is a little harsh but it sure is very capricious. Both the drivers and the database are rather finicky.