Forum Discussion

DKHUghes55's avatar
DKHUghes55
Icon for Resolver II rankResolver II
2 months ago
Solved

Report 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...
Need Help
  • DKHUghes55's avatar
    DKHUghes55
    2 months ago

    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

Parchitect's avatar
Parchitect
Icon for Solution Sage rankSolution Sage
2 months ago

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