Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi Power BI gurus,
For past three weeks we are running into very specific and unclear issue with our custom connector:
We have created custom connector in our company to one of Oracle's systems. The connector is used by 3 users (developers). Everything worked good for quite long time when suddenly one users after getting new PC received following error when report was published to Power BI Service:
I've found following explanation in other suvjects on this forum:
"Please refer to Custom-Data-Connectors-on-Power-BI-Service. The answer could be in blob/master/docs/m-extensions.md#implementing-testconnection-for-gateway-support."
But this didn't do the work. Furthermore, as I mentioned before this case is extremely weird - as it happens only for this one user. If I publish report using the same connector, I don't get any error. But, if I send my perfectly well-working report to user with this problem and she just opens it (without publishing), saves, closes, sends back to me and I open it and publish - I get the same error. So it's like this user's Power BI Desktop or PC is corrupting the .pbix files which use this connector.
Does anyone have any idea what might be a reason of all that? We tried hundreds of things, together with re-installation of Power BI Desktop, and nothing works...
I'll appreciate any, even the craziest ideas!
Thanks in advance!
Karol
Hi @Anonymous ,
You could collect logs from the on-premises data gateway app and temporarily enable Additional logging to gather additional log information.
Or you could leave a comment on Github issues page. And create a support ticket to get the dedicated support.
Thanks, will do that 🙂
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!