Forum Discussion
Issue with Refresh on Power BI Service using ODBC Elasticsearch
- 1 year ago
Hi fatou
Thank you for being part of the Microsoft Fabric Community.
Please do follow the below steps to resolve the issue.- Create a minimal test with 1 table and try refreshing it in the service — confirms if it's model-related or gateway-related.. pbix
- In Power Query, check if steps support query folding ( is enabled). Lack of folding can cause service refresh issues. View Native Query
Enable gateway diagnostic logging and inspect logs at:
C:\Users\<gateway-user>\AppData\Local\Microsoft\On-premises data gateway\GatewayDiagnosticLogs - Monitor gateway server’s RAM/CPU during refresh — resource limits can silently fail large refreshes.
- Confirm DSN name and ODBC driver version match exactly between your desktop and the gateway server.
- Re-enter credentials in Power BI Service under Data Source Settings. Set privacy levels in Desktop to “Ignore” and republish.
- Use scheduled refresh instead of manual refresh — service sometimes mishandles manual triggers.
- Simplify Power Query steps to avoid memory-intensive transforms. Push filters/joins to the source query.
- If your source supports native connectors (e.g., PostgreSQL, SQL Server), use those instead of ODBC.
If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.
Your issue likely stems from ODBC driver mismatches, gateway configuration, or privacy settings in Power BI Service. Ensure the ODBC driver version matches on the gateway, verify data source mapping, and check Privacy Levels (set both to "Organizational"). Debug with a basic query to isolate the problem and check for query folding issues. Review gateway logs in Windows Event Viewer for errors, and try a scheduled refresh instead of manual. Let me know if you need deeper troubleshooting!
Thanks,Pankaj
If this solution helps, please accept it and give a kudos, it would be greatly appreciated.