Intermittent error while refreshing Mysql data

[netvalue]

Hello,

i have configured a refresh schedule of my data model linked to a Mysql istance to be execute from 8:00 to 00:00 every hour.

Sometimes i get this error:

DataSource.Error: An error happened while reading data from the provider: 'One or more errors occurred.'. Microsoft.Data.Mashup.ErrorCode = 10434. DataSourceKind = MySql. DataSourcePath = xxx. . The exception was raised by the IDbCommand interface. Table: xxx

It happens more or less two times a day, sometimes more:

The license used is PPU and if i try to update from Desktop app when from Web doesnt work, it works well.

Do you have any suggestion for how to fix it or how to debug better? "One or more errors occurred" doesn't help a lot.

Thanks a lot.

[v-kpoloju-msft]

Hi @netvalue,
Thank you for reaching out to the Microsoft fabric community forum. Thanks @Akash_Varuna, for your inputs on this issue. After thoroughly reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:

Intermittent errors during data refresh from MySQL in Fabric can be caused by network instability, database timeouts, resource limits, or connector issues. Since the refresh works in Power BI Desktop but fails in the Power BI Service, it's likely due to gateway performance or database connection limits.

Go to Power BI Service → Dataset Settings → Refresh History to find the error message. Test the connection using MySQL Workbench or any MySQL client with the same query to check if the database responds correctly. If using a Direct Query, try Import Mode (or vice versa). Change from MySQL Connector to ODBC driver to test stability.

As the issue is intermittent, please review the MySQL logs for any potential problems:

• Error logs (located at /var/log/mysql/error.log or by executing SHOW ENGINE INNODB STATUS;)
• Slow queries (execute SHOW GLOBAL STATUS LIKE 'Slow_queries';)
• Max connection limits (execute SHOW VARIABLES LIKE 'max_connections';)

If you are using an On-premises Data Gateway, please check the following. Ensure the Gateway is up to date. Review logs located at C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics\Gateway*.log. Restart the Gateway service.

Ensure the dataset size and query time are within limits for the user's PPU (Premium Per User) license. Refresh time < 2 hours. Dataset < 100 GB. Check What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn

Configure Retry Policy in Power BI Service. Power BI automatically retries refresh failures once. You can also manually trigger a retry after a failure.

Please go through the below link for more information:
Monitor and optimize on-premises data gateway performance | Microsoft Learn

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

[netvalue]

Thanks a lot.

Error message is posted in the first topic and is too generic to be useful.

Tested with MySql Workbench and all ok.

Using Import Mode but can't switch cause of customer needs.

Checked in error log and no errors.

Checked slow query and nothing.

Checked max connection and its 151.

We are not using on-premises data gateway.

We have configured retry policy to 4 attempts but fails all.

Refresh time is 1 hour and dataset is approx 6MB.

There is a way to get a detailed log from the Service version? Not the Desktop one.

[v-kpoloju-msft · Accepted solution]

Hi @netvalue,

After thoroughly reviewing the details you provided, I have identified few alternative workarounds that may help resolve the issue. Please follow these steps:

Go to Power BI Service → Dataset Settings → Refresh History. Look for any failed refresh entries and click on them to see if there are additional details provided.

In Power BI Service, you can enable diagnostic logging to capture more detailed information about the refresh process. Navigate to Power BI Service, go to Dataset Settings → Diagnostics, and enable Enhanced Refresh Errors (if available). Try another refresh and check if it provides more details.

Power BI Desktop diagnostics collection - Power BI | Microsoft Learn

Instead of MySQL, try connecting via ODBC or MySQL .NET Connector. In the refresh history, find the failed refresh entry and download the error log. This log may contain more detailed information about the error.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

[v-kpoloju-msft]

Hi @netvalue,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-kpoloju-msft]

Hi @netvalue,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-kpoloju-msft]

Hi @netvalue,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.

Thank you.

[Akash_Varuna]

Hi @netvalue If multiple datasets or reports are refreshing simultaneously, it may exceed the capacity of your workspace. This may cause so try staggering the refresh schedule to avoid conflicts. Ensure the refresh operations are not hitting capacity limits on the PPU license.

[netvalue]

Thank you, as you can see from the screenshot the scheduling happens every hour and usually takes 5 minutes (except when it goes wrong which goes up to 15 minutes) so I doubt it's a concurrency problem.

The dataset is only one and is updated fewer times than the 48 available from the PPU license.

Anyway is there a way to check if this capability is somehow exceeded or a more detailed way to debug the error?