Issue with Refresh on Power BI Service using ODBC Elasticsearch

[fatou]

Bonjour,

Je rencontre un problème d'actualisation des données sur le service Power BI avec une source de données ODBC. Mon rapport fonctionne parfaitement sur Power BI Desktop et s'actualise sans erreur.

       Détails du problème :

 J'utilise Power BI Premium par utilisateur (PPU).

 La passerelle est en ligne et un autre ensemble de données s'actualise avec succès.

 J'ai vérifié que le connecteur ODBC est correctement configuré sur le serveur de passerelle.

 L’authentification est correcte et les informations d’identification sont correctement stockées dans le service Power BI.

 Il n'y a aucun message d'erreur dans l'historique d'actualisation, mais les données ne se chargent pas après l'actualisation.

Tests effectués :

 J'ai testé la connexion ODBC dans Excel et SSMS, et cela fonctionne bien.

 J'ai publié un nouveau fichier Power BI Desktop sur Power BI Service avec le même modèle, mais l'actualisation ne fonctionne toujours pas.

 Questions:

 Pourquoi mon ensemble de données s'actualise-t-il avec succès dans Power BI Desktop mais ne parvient-il pas à charger les données après l'actualisation sur Power BI Service ?

 Existe-t-il des limitations spécifiques à ODBC qui pourraient empêcher le chargement des données sur le service Power BI, même s'il fonctionne localement ?

 Existe-t-il un moyen de forcer une actualisation complète ou d’accéder à des journaux plus détaillés pour diagnostiquer le problème ?

Merci d'avance pour votre aide ! 

[v-csrikanth]

Hi @fatou 

As per Microsoft community guidelines, we will now proceed to close this thread to keep discussions focused and manageable. If you still need assistance, you're welcome to start a new thread in the community at any time.

We appreciate your understanding and participation.

Best regards,
Cheri Srikanth

[fatou]

Hello, sorry for the lack of feedback—I was unavailable. I tested all the methods, but nothing worked. I also changed the source, switching from ODBC to the Elastic API for the update, but it’s still the same issue: the data updates on the desktop, but not on the service, and there’s no error.

[fatou]

Hello, sorry for the lack of feedback—I was unavailable. I tested all the methods, but nothing worked. I also changed the source, switching from ODBC to the Elastic API for the update, but it’s still the same issue: the data updates on the desktop, but not on the service, and there’s no error.

[v-csrikanth]

Hi @fatou 

We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.
Thank you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[v-csrikanth · Accepted solution]

Hi @fatou 

Thank you for being part of the Microsoft Fabric Community.
Please do follow the below steps to resolve the issue.

1. Create a minimal test with 1 table and try refreshing it in the service — confirms if it's model-related or gateway-related.. pbix
2. 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
3. Monitor gateway server’s RAM/CPU during refresh — resource limits can silently fail large refreshes.
4. Confirm DSN name and ODBC driver version match exactly between your desktop and the gateway server.
5. Re-enter credentials in Power BI Service under Data Source Settings. Set privacy levels in Desktop to “Ignore” and republish.
6. Use scheduled refresh instead of manual refresh — service sometimes mishandles manual triggers.
7. Simplify Power Query steps to avoid memory-intensive transforms. Push filters/joins to the source query.
8. 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.

[v-csrikanth]

Hi @fatou 
It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered?
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

Best Regards,Community
Support Team _ C Srikanth.

[fatou]

Hello Srikanth, thank you for your feedback. I have tried all the proposed solutions but I still have the same problem.

[v-csrikanth]

Hi @fatou 

You can follow these steps to verify gateway configuration-

Go to Power BI Service > Settings > Manage Gateways.
Make sure that the ODBC data source is correctly configured and pointing to the correct ODBC connection on the gateway machine.
If your ODBC data source requires a specific driver version, confirm that it's installed on the gateway machine.

Sometimes, in Power BI Service there can be a mismatch in the authentication method.
So, try re-entering them in the Power BI Service to ensure there’s no issue with authentication.

Go to Power BI Service > Settings > Data Source Credential.

By following these above steps, you will be able to refresh in Power BI service.

Hope this helps!

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.

[pankajnamekar25]

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.