Forum Discussion
'Oracle.Databases.Client' could not be instantiated
Thanks Dennis. I think my machine has both Oracle 32 and 64 bit drivers, but they were the older 11GR2 client.
Following that tip from @pquian I downloaded the "64-bit ODAC 12c Release 4 (12.1.0.2.4) for Windows x64" (ODAC121024_x64.zip), and installed it using the default settings. It now seems to be working.
It still seems like a clear bug to me that you can connect and model using some Oracle Drivers, but can't visualise until other drivers are installed. Surely all PBI tasks should use the same drivers? There are lots of other risks e.g. inconsistent drivers, performance, TNSNAMES configurations.
OK it worked ... for a while, all the way through to PBI Web querying via the Enterprise Gateway (after I installed ODAC121024_x64 on that machine).
But today it is working in PBI Desktop, but after re-publishing to PBI Web every visual returns an error:
Please try again later or contact support and provide the following details to help resolve your issue faster.
...
Digging into the PBI Gateway log I'm seeing lots of errors "Unable to find the requested .Net Framework Data Provider. It may not be installed.".
From the Settings / Gateways page the connection tests OK. I tried restarted the PBI Gateway service.
- dennisr10 years agoAdvocate II
I instaled the ODAC121024_x64.zip. I verified that my PATH was updated with the leading
c:\OracleClient\product\12.1.0\client_1;c:\OracleClient\product\12.1.0\client_1\bin;
I still get the same error with the visual.
- dennisr10 years agoAdvocate II
I "frowned" the error this time, and got a reply back...
...This is an issue several customers have hit. We've fixed it in the upcoming release....
[I asked for ETA, and they said ...]
...our monthly release will be available on Thursday, May 26th. You will be able to download it at: https://www.microsoft.com/en-us/download/details.aspx?id=45331
- Knud10 years agoFrequent Visitor
I have exactly the same problem.
The Power BI Desktop version I use is 2.36.4434.381 64-bit (juni 2016).
So the problem is still not solved?