Windows Oracle Data Access Components (MOSC)

MOSC Banner

ODAC 18.3 issue with System.BadImageFormatException

edited Sep 19, 2019 5:03AM in Windows Oracle Data Access Components (MOSC) 1 commentAnswered

Working with one of my developers who compiled their app with ODAC 18.3 via MS Visual Studio 2017.

When we first attempted to run the application on a system without the ODAC 18.3 DLL ('OraOps18.dll'), we received a System.DllNotFoundException.  Easy enough message and we placed the 32-bit OraOps18.dll in the same directory as the compiled application.  We then received a System.BadImageFormatException error when attempting to run the compiled App.  Assumed this was a 32/64 mismatch but it still doesn't play well.

The end user assets have an Oracle 11.2 instant client. Would it make any sense to have an Oracle 18.3 instant client instead?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center