Updated Gateway Issues

[ybarsabal]

My tech team just updated our PBI Gateway to the latest version, and now we're running encountering failed refreshes with these two messages. The reports or schedules have not changed, so it seems like the updated Gateway is somehow problematic. We have reports on PBI.com, normal service (not Premium or Fabric). We have a PBI Gateway setup so our reports can connect to a SQL server. Some refreshes are successful, but many are failing. What could be the issue?

• Timeout expired. The timeout period elapsed prior to completion of the operation.
• Evaluation ran out of memory and can't continue. (this was happening yesterday)

Here were the full errors for example:

• Data source error{"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":"Timeout expired. The timeout period elapsed prior to completion of the operation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}} Table: Common Students RLS.
• Data source error: {"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":"Evaluation ran out of memory and can't continue."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}],"exceptionCulprit":1}}} Table: District Fail.

[rohit1991 · Accepted solution]

Hi @ybarsabal ,

The Power BI Gateway update appears to have introduced performance issues, leading to failed refreshes due to timeouts and memory exhaustion. Since no changes were made to the reports or schedules, the problem likely stems from the gateway's new configuration, increased resource consumption, or an issue with data source connectivity post-update. The timeout error suggests that queries are taking longer to execute, possibly due to network latency, query inefficiencies, or SQL Server performance bottlenecks. 

The memory evaluation error indicates that the Power Query engine within the gateway is running out of resources while processing large datasets. To resolve this, first, check the gateway server's CPU and memory usage to ensure it has sufficient resources. 

Additionally, verify that the SQL Server connection settings (such as timeouts and query optimizations) are correctly configured and that the latest version of the gateway matches the compatibility requirements of your reports. You can also try restarting the gateway service, reducing the data load per refresh, or splitting large queries into smaller, more efficient ones. If the issue persists, consider rolling back to a previous stable version of the gateway or checking the Power BI support forums for known issues with the latest update.

Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.

Connect with me on LinkedIn: Rohit Kumar

[v-aatheeque]

Hi @ybarsabal ,

we 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 our response has addressed by @rohit1991 @GilbertQ your query, please accept it as a solution so that other community members can find it easily.

[v-aatheeque]

Hi @ybarsabal ,

If our response addressed by the community member for your query, please mark it as Accept Answer and click Yes if you found it helpful.

Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[v-aatheeque]

Hi @ybarsabal ,

Thanks for reaching out to Microsoft Fabric Community Forum.
@GilbertQ  Thanks for your prompt response, In additon to that 

• Apply filters in Power Query or the SQL Query itself to reduce dataset size, Avoid loading unnecessary columns.
• If using Import Mode, check if switching to Direct Query helps reduce memory usage.
• Sometimes, simply restarting the On-Premises Data Gateway can resolve the issue. Ensure that the gateway up-to-date and configured correctly.

If a community member’s response addressed your query, please mark it as "Accept Answer" and click "Yes" if you found it helpful.

If you have any further questions, feel free to ask.

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-aatheeque]

Hi @ybarsabal ,

If our response addressed by the community member for your query, please mark it as Accept Answer and click Yes if you found it helpful.

Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[GilbertQ]

Hi @ybarsabal 

But I would recommend doing is confirming with your team who looks after the gateway to make sure that it still has enough memory and enough CPU if it is only an update to the gateway software that should then be fine, but I have a suspicion that maybe they'll also change some of the hardware configurations.