Forum Discussion
Resolver IIReport Error Cannot connect to data source
Hi Fabric Community,
We recently starting see inttermittent issues with reports getting the error "This report couldn't access the data source."
The gateway connecttion responds and is online. The permissions on the report and the gateway connection are set correctly.
What I'm finding is these reports have two things in common. The report is set to Direct Query mode and the data source is an Oracle database.. This was working fine last week. We updated the gateway service the first part of June to the May 2026 version and everything was working then.
I checked with the Oracle team and they have not changed anything on their servers or instances. Note: the two reports access different databases and they are on different servers.
Any help or direction will be greatly appreciated.
DKHughes55
Hi all,
Thanks for the replys. I restarted the server the gateway was on and that has fixed the issue. My guess there was a netowrk change by our security team that needed to be reset.
DKHughes55
7 Replies
- Parchitect
Solution Sage
Hi,
I think its time to start debugging.
Can you test with import mode for a test report?Next check the gateway logs. Collect the on-premises data gateway logs around the exact time the report fails. The generic report message is not enough; the gateway log should show whether the failure is Oracle client, authentication, network, timeout, or query related.Let me know the results.Best regards
Parchitect - Solution Architect - AnkitKukreja
Super User
Hi! DKHUghes55
Check if this works with Import mode. It happened with us few weeks back with new update and we turned this feature off and also realized our team was using custom connector which caused this issue and now we moved to the connector provided by MS.
DKHUghes55Hi AnkitKukreja,
I tried what you suggested and it did not solve the issue. What is interesting is I created the gateway connection on another gateway server we have it works as expected, no error. The two gateways are using the same release (May26) and are configured the same way.
Any thoughts?
DKHughes55
- Parchitect
Hi DKHUghes55,
Yes — the fact that one gateway works and the other doesn't, on the same release, is actually the clue. The May 2026 gateway release has a documented issue: DirectQuery isn't enabled by default when the gateway uses the bundled Oracle provider. Whether a machine is affected depends on what's installed locally, not on the gateway config — if Oracle Managed ODP.NET (OCMT) is installed on the machine, the gateway uses that and works fine; if not, it falls back to the bundled provider and DirectQuery fails.So check whether OCMT / Managed ODP.NET is installed on your working gateway server but missing on the failing one. That would fully explain what you're seeing.
Two fixes for the failing gateway: upgrade it to the June 2026 release (built-in support, enabled by default), or apply the config workaround documented here:
https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-manage-oracle - Kagiyama_yutaka
Continued Contributor
Run Test connection on the Oracle gateway source and check the gateway log at the fail‑second, since those two places show the DirectQuery connection error in the gateway diagnostics.
v-sathmakuriCommunity Support
Hi DKHUghes55 ,
Thank you for reaching out to fabric community.
Could you review the suggestion provided by Parchitect and Kagiyama_yutaka and let us know if you have any additional questions, we are happy to address.
Thanks!!
- DKHUghes55
Hi all,
Thanks for the replys. I restarted the server the gateway was on and that has fixed the issue. My guess there was a netowrk change by our security team that needed to be reset.
DKHughes55
