Dataset refresh manually, but fails when scheduled

[M0hamedFazil]

Hi team, 

I have a Dataset whose refresh need to be scheduled. Initially when I triggered the refresh it throws up a error with code "-2147467259". I searched and found the error was because of transformation. I fixed the error and tried refreshing the data. it refreshed successfully. When I scheduled the dataset it returns the same error. but not when refreshed manually. I have attached the full error below.

Thanks in advance.

[ValidateMarkupTags]{"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":"[ccon]MySQL: Fatal error encountered during data read.[/ccon]"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10478"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"MySql"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"[ccon][ccon]134.913.2.29</ip>[/ccon]<ip><ip>134.913.0.0</ip></ip>;Purchase[/ccon]"}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"[ccon]Fatal error encountered during data read.[/ccon]"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: Sale.

Regards

Fazil M
 

[M0hamedFazil · Accepted solution]

Finally, found the solution.
I have found the root of the problem and it seems to be the appending of two tables. I have checked with different possibilities and all the way seem to refresh, but not the append one.

initially, I appended the large table with small one and this throws the error. By appending the sammler table to large table, The problem is fixed. 

I can now schedule the refresh and the dataset is refreshed at the scheduled time

Regards 
Fazil M

[ibarrau]

I'm glad to read you have found it deeping dive into the desktop transformations.

Regards

[v-aatheeque]

Hi @M0hamedFazil ,

Thanks for reaching out to the Microsoft Fabric Community Forum.

In addition to @ibarrau let me add more insight to the above :
Error Code: DM_GWPipeline_Gateway_MashupDataAccessError

This indicates there is a problem in the data pipeline while accessing or processing the data from the source.

Here are some steps to troubleshoot and resolve the issue:

1. Ensure that your Power BI gateway (if using one) is connected to the data source properly and that there are no issues with the connection.
2.Verify that the credentials used to access the data source are correct and have the necessary permissions.
3.Try refreshing the data to see if the error occurs consistently or intermittently.
4.Ensure the ODBC driver is installed on all machines running the Power BI Gateway.
Check if there are any specific configuration requirements for the ODBC driver in terms of networking, permissions, or service accounts.
5.Go to the Power BI Service, navigate to the Data Source Credentials section under your dataset settings, and ensure they are correct.Test the credentials by manually refreshing the dataset.

You can check the similar solved case : Solved: New ErrorCode=-2147467259 - Microsoft Fabric Community

If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.

If you continue to face issues, feel free to reach out to us for further assistance!

[M0hamedFazil]

HI @v-aatheeque 

Sorry for the delay in response as I'm struck with different work.

I tried and check all the solutions you listed, I can't see to find the problem till now. Now when manually refreshed it throws the same error, which didn't happend before.

Thanks for checking on 

Regards 
Fazil M

[ibarrau]

Hi. Open de PowerBi Desktop original file. Refresh it. If it finishes correctly, then open the Query Editor and look for errors manually. Check at the buttons looking for Keep rows with error, something is odd and it might be a small issue in data that is preventing the refresh.

I hope that make sense

[M0hamedFazil]

Hello @ibarrau ,

The Dataset refreshs manually and I have checked with all the transformations, I checked with the errors too. I didn't ignore any and I corrected those errors. Thanks for the reply and I will let know if I got to find the solution.


Regards 
Fazil M

[v-aatheeque]

Hi @M0hamedFazil 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know

Thank you.

[v-aatheeque]

Hi @M0hamedFazil ,

If our previous response was helpful, please consider clicking "Accept Answer" and selecting "Yes" for whether the answer was helpful. If you have any further questions or need additional assistance, please don't hesitate to reach out.

Thanks for using Microsoft Fabric Community.

[ibarrau]

Hi. That's strange. Try setting other timelines for the refresh. The error sounds like the mysql has some troubles for responding the data. Usually a mashup error means there might be an issue with a value of the data that you have to find it with Desktop. However this time shows that mysql might have a problem, and if it works in another time, it can be an issue of the server or db at that specific time. It could be overloaded.

I hope that helps,

[M0hamedFazil]

Hi @ibarrau 

Thanks for the reply

I'm sure that there is no issues with the connectivity of data source.

Checked with all the transformation and the problem still persists.


Regards 
Fazil M