OLE DB or ODBC error: [DataSource.Error] MySQL: Fatal error encountered during data read.

[Anonymous]

Hi all, 

I encountered the error message when applying query changes as below:

OLE DB or ODBC error: [DataSource.Error] MySQL: Fatal error encountered during data read.

I have checked the DB connection and the database all work fine. Can anyone advise? 

[Syed_Abbas-7]

I would suggest refresh first in query editor and apply it. Later click close option and move to dashboard. It worked for me.

[Prajna]

Hi, 

I'm getting same error while importing a view from MySQL.
The data has around 1 lakh record and I haven't applied any steps others than importing the view from MySQL.
Any help would be appreciated.

Thank you.

[surajpandita1]

Try updating sql-netconnector and power bi. Hope this works for you.

[hilmandenis]

In my case, the root cause is probably a hardware issue. Because when I try to refresh it from my laptop, no matter how Applied Steps is arranged, it still shows the error. But when I give it to my manager, it's just working fine 😐

[Salvador]

Hello,

Have you checked all the steps in the query editor in case any of them gives an error? (You might have to do a refresh on the query editor)

[Anonymous]

@Salvador,

I have done the refresh and checked the query editor and everythings seems fine in query editor with no error return. 

[Anonymous]

I managed to get rid of this error message by redoing the query steps, one by one. After completing one step then i click on close and apply and save after the applying steps succeed and repeat for second steps.

Anyway, i would like to know the root cause of it so that i can prevent it in future. 

[Anonymous]

Hello. 

You redo the query steps in the power query editor in powerbi?

Im kind of new in this and im trying to stablish a connection to mysql. 

I´ll be waiting for an answer. 

Best Regards

[Salvador · Accepted solution]

Hello @Anonymous,

I'd say there was an error on one of the steps, perhaps it wasnt shown on the query editor, (you'd need to refresh in every single step), and there's also the possibility that some data that wasnt being loaded in the query editor was causing the error (i.e, a  # when a numeric value is expected, i've suffered a couple of times by replacing # by empty spaces after setting the data type to numeric, even tough it might work in the query editor, when the full data set is loaded it will give an error)

[Digger]

it is not true, when i refresh single table which give error on main refresh, error does not appears