ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

3
votes

We have an ASP.net web-app running in the following environment -

Existing Environment

Operating System : Windows 2003

Framework : .NET Framework : 2.0

IIS : 6.0

Database : Oracle 10g

We wished to upgrade this to the following environment

Present Environment

Operating System : Windows 2008 R2 x64

Framework : .NET Framework : 2.0

IIS : 7.0

Database : Oracle 11g

While doing so, we face the below issue

ODBC Connection Issue on Windows Server 2008 R2 64 bit

ODBC connection could not be established from the ASP.net Web Application in Windows Server 2008 R2.

Application throws an Error : ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.

Connection String : 

<add name="ConnectionString" connectionString="Driver=Oracle in XE;Dsn=winerenew;uid=winere;pwd=winere;dbq=XE;dba=W;apa=T;exc=F;fen=T;qto=T;frc=10;fdl=10;lob=T;rst=T;btd=F;bam=IfAllSuccessful;num=NLS;dpm=F;mts=T;mdi=F;csr=F;fwc=F;fbs=64000;tlo=O" providerName="System.Data.Odbc"/>

Application works perfectly in windows 2008 x86.

We have tried the following ways to resolve this issue in Windows Server 2008 x64,

1) Enabled the 32-Bit Application in the Application Pool (IIS 7)

2) Executed the ODBC 32 Bit driver with the following command C:\Windows\SysWOW64\odbcad32.exe

3) Installed the oracle 64-bit ODBC driver.

The above methods doesn't seem to solve this issue. Could anyone tell me the problem behind it and the solution to solve this issue?

1
asp.netoracleodbcwindows-server-2008-r2
Is ODBC driver visible in both 32 and 64 bit versions of odbcad32.exe? Is it possible to configure DSN via this interface? - Michał Niklas
Yes,it is visible in both 32 and 64 bit versions of odbcad32.exe and we have configured the DSN in the name of winerenew - user1611540

1 Answers

-1
votes

If you have working DNS then you can enable tracing ODBC calls from odbcad32.exe. Then test Oracle connection from any ODBC editor/tool (I often test it with simple Python program that uses odbc module). Such tracing will create file with a successful attempt to connect to database. After connecting do database close program, stop tracing and rename trace file.

Now you will have to create such tracing for your application: enable tracing, start your program, try to connect do database, close program, stop tracing. You have two files with attempts to connect to database via ODBC: one successful and one with failure. Compare them.