Forum Discussion
Advocate IDataset refresh error - timeout
Hi Gianf ,
To address this effectively, we recommend raising a support ticket with Microsoft Azure Support. This will allow the engineering team to investigate the issue in detail and provide a resolution or guidance
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you
Hi v-dineshya
We were able to solve the issue with the help of Microsoft support.
It is somewhat a workaround, but it works, so... here it is the solution.
We added an explicit longer timeout in Power Query connection to SQL Server:Sql.Database(ServerName, DbName,[CommandTimeout=#duration(0,0,45,0)])
Advocate IHi v-dineshya
I asked my system admin to perform the check you suggested againtst the gateway.
regarding #1, he say he is unable to find the gateway timeout settings in the Power Bi admin portal
about #4, we searched for Mashup.MaxPreviewExecutionTime settings in configuration file and it is not present. Since we don't know which default this setting has, we googled for this setting and... well... it found this topic only
Can you help us about this?
thank you!
Community SupportHi Gianf ,
To address this effectively, we recommend raising a support ticket with Microsoft Azure Support. This will allow the engineering team to investigate the issue in detail and provide a resolution or guidance
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you
- v-dineshya
Hi Gianf ,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.
Thank you for your understanding and participation.
- Gianf
Hi v-dineshya
The issue has not been resolved yet. I am currently in touch with Micrsosft support, hope we will solve the problem soon, as refrsh failures are increasing both in number and severity. - Gianf
Hi v-dineshya
We were able to solve the issue with the help of Microsoft support.
It is somewhat a workaround, but it works, so... here it is the solution.
We added an explicit longer timeout in Power Query connection to SQL Server:Sql.Database(ServerName, DbName,[CommandTimeout=#duration(0,0,45,0)])