Skip to main content

"Cannot load ODP.NET Provider" Error While Attempting Admin Database Installation Test Connection

Article # 3040761 - Page views: 155


Why does this error appear during an Insight installation?



The error occurs when Oracle's data access library, Oracle.DataAccess.dll isn't properly installed and registered on the machine's Global Assembly Cache ("GAC").



There are many reasons for this, however, here are some areas to review to help resolve this. Though this example uses Insight v6.3, these steps can be applied to any supported version of Insight and Oracle.


  • New versions of Oracle Server software, including the Express edition, may install the data access files, but they are not registered by default. Refer to related Oracle documentation and on-line resources for details on how to register ODP.Net. If you are installing Insight v6.3.x, steps to do that using Oracle's OraProvCfg.exe utility are provided in the Insight Installation Guide. Here is an example of a successful registration after following those two steps:
    • gac register.jpg


  • Verify your ODP.Net libraries are installed at a machine-wide level into the GAC, that path is similar to the following (this applies to Oracle's 64-bit data access library installation):

gac file system.jpg


NOTE: For v6.x, the 64-bit .Net library must be registered into the path shown above. If your assembly shows registered into C:\Windows\Microsoft.NET\assembly\GAC_32 folder, that will not work and must be corrected (even of both folders have them). If you require both bit-levels, consult with your Oracle resources for resolution. 

After resolving this issue, you must restart Insight Installation Manager to retest the connection to your Admin database. If issues exist, review wcfDataService.log for errors. If "object reference not set to instance of an object" errors are documented there, be sure your TNSNames.ora file contains an entry for the Oracle service. Restart IIS and Scheduler if changes are made.

Oracle documentation also states that extracting their installers into directories with spaces isn't supported. It is also recommended to extract their installers close to the drive letter rather than under directories and sub-directories (e.g.: D:\Folder1 rather than D:\Folder1\folder2...etc.)

Level of Complexity 



Applies to  

Product Version Build Environment Hardware





Article # 3040761