BadImageFormatException. This will occur when running in 64 bit mode with the 32 bit Oracle client components installed


BadImageFormatException. This will occur when running in 64 bit mode with the 32 bit Oracle client components installed



I am getting this error while on of my .Net application are trying to make a connection to oracle database.


.Net



The error says that This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.. But I have made sure many times that the client installed in x64 bit not 32.


This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.


x64


32


Date Time: 6/8/2014 10:57:55 AM: System.InvalidOperationException: Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed. ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at System.Data.Common.UnsafeNativeMethods.OCILobCopy2(IntPtr svchp, IntPtr errhp, IntPtr dst_locp, IntPtr src_locp, UInt64 amount, UInt64 dst_offset, UInt64 src_offset)
at System.Data.OracleClient.OCI.DetermineClientVersion()
--- End of inner exception stack trace ---
at System.Data.OracleClient.OCI.DetermineClientVersion()
at System.Data.OracleClient.OracleInternalConnection.OpenOnLocalTransaction(String userName, String password, String serverName, Boolean integratedSecurity, Boolean unicode, Boolean omitOracleConnectionName)
at System.Data.OracleClient.OracleInternalConnection..ctor(OracleConnectionString connectionOptions)
at System.Data.OracleClient.OracleConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.OracleClient.OracleConnection.Open()
at CustomizedSetupInstaller.Runscripts.InitializeDBObjects(String connectionString, String dbProvider)





You're using System.Data.OracleClient. This namespace has been deprecated and will be removed in a future version of .NET. Perhaps you are using a 32-bit version of that? It is also not part of the Oracle client, so whether you are using a 32-bit or 64-bit Oracle client is irrelevant. Ideally, you should be using Oracle.DataAccess (or Oracle.ManagedDataAccess) instead.
– Luke Woodward
Jun 8 '14 at 8:48



System.Data.OracleClient


Oracle.DataAccess


Oracle.ManagedDataAccess





Minor mistake: System.Data.OracleClient is just the Provider, it also uses an Oracle Client which must match the architecture. Only Oracle.ManagedDataAccess does not require an additional Oracle client installed. Maybe the Oracle Client is x64 but your application is 32-bit, this does not work either. It is possible to install both 32-bit and 64-bit Oracle client on the same machine
– Wernfried Domscheit
Jun 8 '14 at 12:28



System.Data.OracleClient


Oracle.ManagedDataAccess




16 Answers
16



One solution is to install both x86 (32-bit) and x64 Oracle Clients on your machine, then it does not matter on which architecture your application is running.



Here an instruction to install x86 and x64 Oracle client on one machine:



Assumptions: Oracle Home is called OraClient11g_home1, Client Version is 11gR2


OraClient11g_home1



Optionally remove any installed Oracle client (see How to uninstall / completely remove Oracle 11g (client)? if you face problems)



Download and install Oracle x86 Client, for example into C:Oracle11.2Client_x86


C:Oracle11.2Client_x86



Download and install Oracle x64 Client into different folder, for example to C:Oracle11.2Client_x64


C:Oracle11.2Client_x64



Open command line tool, go to folder %WINDIR%System32, typically C:WindowsSystem32 and create a symbolic link ora112 to folder C:Oracle11.2Client_x64 (see commands section below)


C:WindowsSystem32


ora112


C:Oracle11.2Client_x64



Change to folder %WINDIR%SysWOW64, typically C:WindowsSysWOW64 and create a symbolic link ora112 to folder C:Oracle11.2Client_x86, (see below)


C:WindowsSysWOW64


ora112


C:Oracle11.2Client_x86



Modify the PATH environment variable, replace all entries like C:Oracle11.2Client_x86 and C:Oracle11.2Client_x64 by C:WindowsSystem32ora112, respective their bin subfolder. Note: C:WindowsSysWOW64ora112 must not be in PATH environment.


PATH


C:Oracle11.2Client_x86


C:Oracle11.2Client_x64


C:WindowsSystem32ora112


bin


C:WindowsSysWOW64ora112



If needed set your ORACLE_HOME environment variable to C:WindowsSystem32ora112


ORACLE_HOME


C:WindowsSystem32ora112



Open your Registry Editor. Set Registry value HKLMSoftwareORACLEKEY_OraClient11g_home1ORACLE_HOME to C:WindowsSystem32ora112


HKLMSoftwareORACLEKEY_OraClient11g_home1ORACLE_HOME


C:WindowsSystem32ora112



Set Registry value HKLMSoftwareWow6432NodeORACLEKEY_OraClient11g_home1ORACLE_HOME to C:WindowsSystem32ora112 (not C:WindowsSysWOW64ora112)


HKLMSoftwareWow6432NodeORACLEKEY_OraClient11g_home1ORACLE_HOME


C:WindowsSystem32ora112


C:WindowsSysWOW64ora112



You are done! Now you can use x86 and x64 Oracle client seamless together, i.e. an x86 application will load the x86 libraries, an x64 application loads the x64 libraries without any further modification on your system.



Probably it is a wise option to set your TNS_ADMIN environment variable (resp. TNS_ADMIN entries in Registry) to a common location, for example TNS_ADMIN=C:OracleCommonnetwork.


TNS_ADMIN


TNS_ADMIN


TNS_ADMIN=C:OracleCommonnetwork



Commands to create symbolic links:



cd C:WindowsSystem32
mklink /d ora112 C:Oracle11.2Client_x64
cd C:WindowsSysWOW64
mklink /d ora112 C:Oracle11.2Client_x86


cd C:WindowsSystem32
mklink /d ora112 C:Oracle11.2Client_x64
cd C:WindowsSysWOW64
mklink /d ora112 C:Oracle11.2Client_x86



Notes:



Both symbolic links must have the same name, e.g. ora112.


ora112



Despite of their names folder C:WindowsSystem32 contains the x64 libraries, whereas C:WindowsSysWOW64 contains the x86 (32-bit) libraries. Don't be confused.


C:WindowsSystem32


C:WindowsSysWOW64





When running the Oracle Client installer, it asks you for a path for the Oracle Base, and one for the Oracle Home. In your instructions here, would you just tack on "OraClient11g_home1" to each of the paths you specify? So Oracle Base would be "C:Oracle11.2Client_x86" and Software Location (Oracle Home) would be "C:Oracle11.2Client_x86OraClient11g_home1"?
– sliderhouserules
Oct 23 '14 at 20:29





OraClient11g_home1 is the "Oracle Home Name" which is used to identify correct key in your registry, see How Home Selector Works. In earlier Oracle versions you had an "Oracle Home Selector" application where you can switch between different Oracle Clients installed on one machine. It is not mandatory to have the Oracle Home Name equal to your folder name where Oracle is installed. Oracle Base "C:Oracle11.2Client_x86" and Software Location "C:Oracle11.2Client_x86OraClient11g_home1" works fine.
– Wernfried Domscheit
Oct 24 '14 at 5:49



OraClient11g_home1





Ah, I see... the Instant Client only asks you for one path: the Software Location, i.e. the Oracle Home. So all of your paths above are the Oracle Home. If you choose any of the other three install types (Administrator, Runtime, Custom) it makes you choose a path for both Oracle Base and Oracle Home. If I choose "C:Oracle11.2Client_x86OraClient11g_home1" for my Oracle Home, then I need to use that path in place of your paths above...
– sliderhouserules
Oct 24 '14 at 19:17





This is very helpful. Is the 64bit xCopy package good enough or is the full 64bit client needed? I can't seem to find a download for it besides the instaclient, but I don't have the 32bit instaclient installed, rather the full client.
– Andrew Grothe
Feb 4 '15 at 15:31






what is the point of the symbolic links or modifying the registry? When left alone, the provider will find the unmanaged libraries by the path IT sets in the registry.
– b_levitt
Feb 17 '15 at 12:49



In my situation, the Oracle 11.2 32-bit client was installed on my 64-bit Windows 2008 R2 OS.



My solution: In the Advanced Settings for the Application Pool assigned to my ASP.NET application, I set Enable 32-Bit Applications to True.



Please see below for the standalone .ashx test script that I used to test the ability to connect to Oracle. Before making the Application Pool change, its response was:


[Running as 64-bit] Connection failed.



...and after the Application Pool change:


[Running as 32-bit] Connection succeeded.



TestOracle.ashx – Script to Test an Oracle Connection via System.Data.OracleClient:



To use: Change the user, password and host variables as appropriate.



Note that this script can be used in a standalone fashion without disturbing your ASP.NET web application project file. Just drop it in your application folder.


<%@ WebHandler Language="C#" Class="Handler1" %>
<%@ Assembly Name="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" %>

using System;
using System.Data.OracleClient;
using System.Web;

public class Handler1 : IHttpHandler
{
private static readonly string m_User = "USER";
private static readonly string m_Password = "PASSWORD";
private static readonly string m_Host = "HOST";

public void ProcessRequest(HttpContext context)
{
context.Response.ContentType = "text/plain";

string result = TestOracleConnection();
context.Response.Write(result);
}

public bool IsReusable
{
get { return false; }
}

private string TestOracleConnection()
{
string result = IntPtr.Size == 8 ?
"[Running as 64-bit]" : "[Running as 32-bit]";

try
{
string connString = String.Format(
"Data Source={0};Password={1};User ID={2};",
m_Host, m_User, m_Password);

OracleConnection oradb = new OracleConnection();
oradb.ConnectionString = connString;
oradb.Open();
oradb.Close();
result += " Connection succeeded.";
}
catch
{
result += " Connection failed.";
}

return result;
}
}





This worked for me as well.
– Romeo Sierra
Mar 29 at 5:57



I had the same issue on a Windows 10 PC. I copied the project from my old computer to the new one, both 64 bits, and I installed the Oracle Client 64 bit on the new machine. I got the same error message, but after trying many solutions to no effect, what actually worked for me was this:
In your Visual Studio (mine is 2017) go to
Tools > Options > Projects and Solutions > Web Projects



On that page, check the option that says:
Use the 64 bit version of IIS Express for Websites and Projects





This worked for me as well. By default IIS express will be running in 32 bit mode in VS.
– Sreekumar P
Mar 25 at 3:46



To revise IIS



Comment:



Platform: Windows Server 2008 R2 Enterprise - 64Bit - IIS 7.5



As it was pointed out in the comments, System.Data.OracleClient is deprecated. There is little reason to start using it so late in the game.



Also as pointed out in the comments (I've marked this as community wiki in observence), there is now a managed provider as part of the 12c and later versions of the odp.net package. This provider does NOT require any unmanaged dlls so this should be a non issue in that case.



If you would prefer to use the old unmanaged Oracle.DataAccess provider from oracle, the simplest solution is to set the "DllPath" configuration variable:


<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<oracle.dataaccess.client>
<add key="DllPath" value="C:oraclebin"/>
</oracle.dataaccess.client>
</configuration>



See "Search Order for Unmanaged DLLs" in http://docs.oracle.com/database/121/ODPNT/InstallODP.htm for more information





An update here, since VS2015 and Oracle 12cR3 are out... if you want to install both the 32-bit and 64-bit clients, download both ODAC packages (took me a while to find them, but just search for e.g. "oracle 64 bit odac" etc.). Install each of them to an Oracle Base path of "C:Oracle12.1.0.2.1" and then for the Software Location add "Client_x86" (or x64) onto that path. Everything that b_levitt has said then applies. Both versions are fully configured and 32-bit apps will use the 32-bit driver, and 64-bit apps will use the 64-bit driver. Easy-peasy.
– sliderhouserules
Sep 4 '15 at 21:05






Oh, and as of 2015-09-04 Oracle still hasn't released the Oracle Developer Tools for Visual Studio 2015. They promised to have it released within one month of VS2015 RTM, but it's well past that and still a no-show. :(
– sliderhouserules
Sep 4 '15 at 21:06




I had the same problem in SSIS 2008. I tried to connect to an Oracle 11g using ODAC 12c 32 bit. Tried to install ODAC 12c 64 bit as well. SSIS was actually able to preview the table but when trying to run the package it was giving this error message. Nothing helped.
Switched to VS 2013, now it was running in debug mode but got the same error when the running the package using dtexec /f filename.
Then I found this page:
http://sqlmag.com/comment/reply/17881.



To make it short it says: (if the page is still there just go to the page and follow the instrucrtions...)
1) Download and install the latest version of odac 64 bit xcopy from oracle site.
2) Download and install the latest version of odac 32 bit xcopy from oracle site.
How? open a cmd shell AS AN ADMINSTARTOR and run:
c:64bitODACLocation> install.bat oledb c:odacodac64.
the first parameter is the component you want to install. The second param is where to install to.
install the 32 version as well like this: c:32bitODACLocation> install.bat oledb c:odacodac32.
3) Change the path of the system to include c:odacodac32; c:odacodac32bin; c:odacodac64;c:odacodac64bin IN THIS ORDER.
4) Restart the machine.
5) make sure you have the same tnsnames.ora in both odac32adminnetwork and odac64adminnetwork folders (or at least the same entry for your connection).
6) Now open up SSIS in visual studio (I used the free 2013 version with the ssis package) - Use OLEDB and then select the Oracle Provider for OLE DB provider as your connection type. Set the name of the entry in your tnsnames.ora as the "server or file name". Username is your schema name (db name) and password is the password for schema. you are done!



Again, you can find the very detailed solution and much more in the original site.



This was the only thing which worked for me and did not mess up my environment.



Cheers!
gcr





Please describe (in your own words) what the instructions told you to do. The page you link to could easily disappear, and then we are all still none the wiser as to how to solve this error.
– Martijn Pieters
May 1 '16 at 14:03



I developed desktop application using C#.net with 2.0 framework along with system.data.oracleclient for connecting oracle db and I was facing similar error message ,"Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed."



following solutions were applied



now, it work because application is set for 32bit and oracle 32bit client installed over Win2012 R2 server, hopefully will work for you.



BadImageFormatException occures when a 32bit (x86) dll calls a 64bit dll or vice versa. If using AnyCPU for your entry executable then when run on a 64bit machine it will run as 64bit, however if that then calls a 32bit dll you get the exception which is why AnyCPU isn't always the answer.



I tend to build everything as 32bit (x86) as we still have to interface with some old components done in VB6 (32bit (x86)). While performance might be better for 64bit machines if we where to build in AnyCPU reliability is more important for us.



I would suggest trying to build all you components in 32bit (x86), unless you are doing some really intensive stuff I doubt it will make much difference.



As apc mentioned that error occurs "when a 32bit dll calls a 64bit dll or vice versa". The problem is that if you have build using AnyCPU and are running on a 64bit environment then the application will run as 64bit.
If rebuilding explicitly for 32 and 64 bit is not an option then you could use a microsoft utility called corflags.exe which comes with the Windows SDK. Basically, you can modify a flag in the exe of the program you are executing to tell it to run as 32bit even if the environment is 64bit.



See here for information on using it



I would like to add a resolution that worked for me.
Setup: Oracle 11g 64 bits running on Windows 2008 R2 (64 bits OS)



Client is a .net framework 3.5 application (ported from 2.0) compiled with x86 platform setting.



I had the exact same issue of BadImageFormatException. Compiling to 64 bits eliminates the exception but it was not an option for me as my app is using 32 bits activex components who do not work in 64 bits.



I solved the issue by downloading Oracle Instant Client 11 (this is just a bunch of DLL than can be xcopied) from Oracle website, and copying the files in my application files directory. See here : http://www.oracle.com/technetwork/database/features/oci/instant-client-wp-131479.pdf



This has solved the issue, from ProcMon tool I can see that the locally copied oci.dll gets loaded by System.Data.OracleClient and everything is fine.



It could probably be done by changing environment settings like proposed above, but this method has the advantage of not altering any settings on the server configuration.



I got this issue for a console Application.
In my case i just changed the Platform Target to "Any CPU" which you can see when you right click your solution and click on properties , you will find a Tab "Build" click on it you will see "Platform target:" change it to "Any CPU", which will solve your issue



this solution work for me ,



To revise IIS


Select Application Pools.
Clic in ASP .NET V4.0 Classic.
Select Advanced Settings.
In General, option Enable 32-Bit Applications, default is false. Select TRUE.
Refresh and check site.



Comment:



Platform: Windows Server 2012 Standart- 64Bit - IIS 8



Mine is the console application (it should work for the windows application as well) and I had same problem.
To solve it I used PlatformTarget as x64 as my System.Data.OracleClient.dll (64 bit file) is at C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.5. This will explicitly use 64 bit version of Oracle Client.
This might help you if your solution works only on 64bit and if you are not using 32 bit dlls like dlls made in VB.
I hope it will help you.



Please download the correct version of Oracle Client like Oracle Client 11.2 32-Bit; which resolved the problem for me.



Make sure that registry HKEY_LOCAL_MACHINESOFTWAREORACLEODP.NET4.112.# DIIPath key is pointing to 32 bit Oarcle client BIN directory.
For example, DIIPath value can be C:appUser_name11.2.0client_32bitbin



Just build your code in x86 mode not in AnyCpu.






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Popular posts from this blog

api-platform.com Unable to generate an IRI for the item of type

How to set up datasource with Spring for HikariCP?

PHP contact form sending but not receiving emails