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.
Hey, everybody.
I've seen this problem occurring from time to time with users.
Is there a solution?
{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"MySQL: Fatal error encountered during data read."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"MySql"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"</ip>:;admin_ibs"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"Fatal error encountered during data read."}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: students_ibs.
Hi @KossXL ,
May I ask if your problem has been solved. If the above reply was helpful, you may consider marking it as solution. If the problem is not yet solved, please feel free to ask us a question.
Best Regards,
Ada Wang
As far as what I understand, this issue is happening in service and it is intermediate.
> can you check how these queries are running at the db end? May be you can find a detailed error message?
> if it is due to a scheduled data pipeline activity at the db end then you would not see such error if you change the schedule, have you tried changing the schedule?
Yes, I changed the refresh time today, it didn't help at all, it gave me an error
Did you get a chance to look at the query log at the db end?
Unfortunately I don't have access rights to the database query logs 😞
@KossXL
"MySQL: Fatal error encountered during data read" seems like an error thrown by the database. Is it a direct query data model?
Data import is used. What is interesting is that when updating from desktop there is no such problem, the error occurs only when scheduled update in service and then not every day.
User | Count |
---|---|
48 | |
28 | |
21 | |
19 | |
19 |
User | Count |
---|---|
51 | |
47 | |
25 | |
23 | |
20 |