Re: ASP problem with the Oracle ODBC driver

From: Mark Schupp (mschupp_at_ielearning.com)
Date: 10/04/04 

Date: Mon, 4 Oct 2004 16:10:39 -0700

That particular error is usually associated with a setting the Net8
configuration files.

Solution is here: http://www.lazydba.com/oracle/0__14272.html

Through Oracle 8 we normally recommend using the Microsoft ODBC for Oracle
driver because the Oracle ODBC drivers have been unstable. Starting with
Oracle 9 you have to use the Oracle ODBC drivers because the Microsoft
driver doesn't support past Oracle 8. It does appear that the latest Oracle
ODBC drivers are more reliable than they have been in the past.

You might also want to have a look at using OLEDB because ODBC is
deprecated. 

-- 
Mark Schupp
Head of Development
Integrity eLearning
www.ielearning.com
<simianphile@hotmail.com> wrote in message
news:1096924384.717419.274380@k17g2000odb.googlegroups.com...
> OK, I had a problem that I've now fixed but I can't really understand
> what was causing it in the first place.  I have an intranet site that
> uses basic authentication to allow users to view and update information
> from an Oracle DB (ver 8.1.6 -- ancient, I know).  Anyway, the site
> worked fine as long as the machine accessing the ASP page was running
> Win 2k but when an XP machine tried to view the page, the client got an
> error:
>
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Oracle][ODBC][Ora]ORA-12640: Authentication adapter initilization
> failed
>
> I tried googling the error and ran across a post that suggested using
> the Microsoft ODBC driver for Oracle rather than the Oracle ODBC
> driver.  I made the change and things are working fine now.  I guess my
> question is why did this happen?  If it was really an ODBC driver
> problem it would seem to have occured regardless or the OS of the
> requesting machine.  (After all, this is requested through HTTP)
>

Relevant Pages

  • Oracle 9.2.0.3.0 ODBC Fails
    ... We just upgrade our oracle server from 8i up to 9i and now our asp pages are ... We were using the Microsoft ODBC drivers for Oracle V ...
    (microsoft.public.inetserver.asp.db)
  • Re: Connectionstring problem
    ... this {Microsoft ODBC for Oracle}; ... your whole connection string looks like the one used for SQL ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: ODBC connection to mdb for MacIntosh
    ... >>> Microsoft Access does not exist for the Mac. ... In order to use ODBC ... >>> the data tables (the .mdb file) has to reside on a Windows computer that ... As long as the computer has ODBC drivers for an Access ...
    (microsoft.public.mac.otherproducts)
  • Re: ODBC connection to mdb for MacIntosh
    ... As long as the computer has ODBC drivers for an Access database, it does NOT have to have Access installed. ... Office 98 and 2001 it was possible to control several different types of databases directly on a single Mac without having the application on the computer. ... No, you can not put the mdb file on a mac and connect to MS Access via ODBC because MS Access only runs in windows, not on a Mac. ... If you search Google on this topic about 2 years ago there was a complete thread in the Excel for Mac newsgroup about ODBC drivers. ...
    (microsoft.public.mac.otherproducts)
  • Re: Whats so bad about ODBC
    ... It is far better to connect to Oracle using the native connectivity. ... What exactly might be a problem with ODBC? ... data to be fetched to the client, and have it filtered on the client. ... actual execution paths are often unpredictable, ...
    (comp.databases.oracle.server)