Skip to Main Content

ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Unable to get 64-bit Instant Client (12.1.0) to work

user9108328Jan 30 2017 — edited Feb 8 2017

My company has had projects in which we created 32-bit Entity Framework (EF) projects against the 32-bit ODAC and successfully implement the Instant Client. Now, I'm experimenting with the 64-bit drivers against EF6. I am able to successfully compile and execute EF6 code with the 64-bit drivers on a development machine. However, if I try copying the directory of compiled files (under Debug) onto another box and try executing the code, I get an error stating that "The ADO.NET provider with invariant name 'Oracle.ManagedDataAccess.Client' is either not registered in the machine or application config file, or could not be loaded."

I've tried literally adding every single file from the Instant Client directory (XCopy version) into the executable directory and still get the same error. It seems that no matter what I do to the config file (including deleting the sections below entirely!), nothing alters the type of error.

My config file contains the following:

  <entityFramework>

    <defaultConnectionFactory type="Oracle.ManagedDataAccess.EntityFramework.OracleConnectionFactory, Oracle.ManagedDataAccess.EntityFramework" />

    <providers>

      <provider invariantName="Oracle.ManagedDataAccess.Client" type="Oracle.ManagedDataAccess.EntityFramework.EFOracleProviderServices, Oracle.ManagedDataAccess.EntityFramework, Version=6.121.2.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />

    </providers>

  </entityFramework>

Of note is the machine I'm trying to test on already has the 32-bit Oracle client installed. However, I don't see why this should affect a separate directory with my test application.

What might I be missing here?

Thank you.

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 8 2017
Added on Jan 30 2017
2 comments
974 views