Link to home
Create AccountLog in
Avatar of aparfitt
aparfittFlag for United Kingdom of Great Britain and Northern Ireland

asked on

The application, M:\WINDOWS\system32\odbcad32.exe, generated an application error

We have 3 ODBC connections all linking to the same oracle backend they work perfectly for a while and then crunch they all pack up.

Configuring the connection in the ODBC setup and selecting Test causes the ODBC setup app to shut down.

The following error message is reported

"The application, M:\WINDOWS\system32\odbcad32.exe, generated an application error "

anyone got any ideas what is causing this?

Thanks
Avatar of sanjeev559
sanjeev559

ODBC 3.0 drivers require the 3.0 version of the ODBC Driver
        Manager (ODBC32.DLL and ODBCCP32.DLL). Because the ODBC 3.0
        Driver Manager is compatible with 2.x compliant drivers, all 2.x
        versions of the Driver Manager should be removed from your access
        path to ensure application stability.  Failing to remove older
        versions of the Driver Manager may result in application errors
        and abnormal terminations.
Avatar of Mark Geerlings
Trying to prevent or troubleshoot "application errors" in Windows is one of the most frustrating parts of supporting applications that run on Windows.  The problem is, these errors usually happen at a level that we don't have direct access to, or control over.  They happen in the interaction between the executables from Oracle (or whichever ODBC driver you are using) and the Windows operating system (which doesn't do a good job of managing memory).

One thing that you may be able to try is a complete reformat, then a re-install of Windows, then a re-install of just the  ODBC driver and the application that uses the ODBC connection to an Oracle database.  If the application works that way, then one of the other applications on the computer now has something (probably a *.dll file) that conflicts with the ODBC driver.  Sometimes then you can get around the problem by putting the particular *.dll files for each product in the directory where each program is installed, instead of having them all in C:\Windows\system32.
ASKER CERTIFIED SOLUTION
Avatar of RCorfman
RCorfman

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of aparfitt

ASKER

sanjeev559  
We have no 2.x drivers on the server.

markgeer
We have rebuilt the server from scratch several times and the error always rears it's ugly head again after a while.

RCorfman
We are using v 9.2.00 so we will try upgrading to .07 and see if that helps.

In addition we have noticed that the SQLPlusw.exe utility does not work anymore, anybody know why that would happen?

Many thanks.

It will help upgrading.  Just take care in applying the patch as it took us a lot of work to actually get it installed correctly. Many of the people applying it weren't letting it complete, or they had Oracle running when they tried to apply it, etc.

As far as sqlplusw, check to see that any shortcuts are still pointing to the right home. Also, you might use the Oracle home utility and make sure you are pointing at the right home if you have more than one.  It would help to know what error you are getting...
Hi Guys

We've not yet been able to install the latest driver however I have noticed the following and wondered if it rings any bells.

In the odbc driver configuration the drop down list for TNS Service name contains corrupted names.  I can send a screen shot if anyone would like to see it.

Cheers
Amanda

I don't get a drop-down for service names in the ODBC configuratore at all. Maybe looking in different places though. I use Microsoft's ODBC Management tool and pick Oracle's Client.  It may be that you have something else going on, but I know for fact that using the older driver produces crashes like you've been experiencing.
hi ,

i had the same sort of problem. I uninstalled all kinds of sql products like oracle , MS sql server etc and went for MS updates.
Then checked it's working fine now

Regards
sugun