VBA/ODBC Error. Provider Not Found.Driver not I

manO-kumar · November 14th, 2004, 12:54 PM

Hi,
   I am facing an issue which is bugging me for almost 3 weeks .

    We have a solution which has excel as front end and connecting to Oracle database using ADO . This is working properly on almost 2000 XP machines . However this is not working on two machines which is giving me Provider not found error .

Operating system : Microsoft XP Service pack 1a
Oracle database Version : 8.1.7
Oracle Client : 8.1.7

I tried DSN less connection using Microsoft ODBC Driver for Oracle and Oracle ODBC Driver .

Both the machines are having Oracle Client Installed
Both the machines are upgraded to XP Service Pack 1a which has MDAC V2.7 installed as Microsoft site suggested ...
The MSDTC registry folder is having full authorization.
Path include both Oracle\bin and window System folders.

If you test using ODBC connection utility on these machines , it's working fine . However connection using ADO is always failing giving me Provider not found error .

cnnRwSM = New ADODB.Connection
        cnnRwSM.ConnectionString = "DSN=SM;UID=SM;PWD=xxxx"
        cnnRwSM.Mode = ADODB.ConnectModeEnum.adModeReadWrite
        cnnRwSM.Open

Also I tried Oracle Driver
     cnnRwSM.ConnectionString = "Driver={Oracle ODBC Driver};DBQ=SMBSP.WORLD;UID=SM;PWD=xxxx"
        cnnRwSM.Mode = ADODB.ConnectModeEnum.adModeReadWrite
        cnnRwSM.Open

I tried to specify both Microsoft & Oracle Provider names too .

I checked both OracleOciLib registory entry which is pointing to oci.dll and tried ociw32.dll too

I am not where to go from here ..

I am not sure whether MDAC files are corrupted ..However not sure to proceed ...

Any help is greatly appreciated .

thanks
Manoj

mmcdonal · November 15th, 2004, 04:06 PM

Hi,

   Do a search for the following file: "TNSNAMES.ORA"

   This file keeps connection information for your Oracle databases. You will probably have several versions of this on your computer.

   Sometimes you can have this problem if the entries are not in the right order, or there are conflicting versions of the file. You will find more than one of these files on these computers.

   The users probably did some updating or have connected to different Oracle databases in the past.

   What you may want to do, after backing up these files, or course, is to open them with Notepad, compare entries, and consolidate the files so that all source names are in the same file. Then mess around with the order of the entries, moving your Excel apps database further up the list.

   When you are done, copy the file to all the locations where you found it. If you have more than one ORA directory, then this could definitely be a problem.

   Be careful with the syntax and just be sure to copy it so that you don't leave out a character.

   Anyway, it doesn't sound like a DSN issue.

   Maybe this will help.

Thanks,

mmcdonal

manO-kumar · November 24th, 2004, 12:59 PM

Hi mmcdonal,
thanks for the response .

verifying TNSNAMES.ORA is of course the first step I checked after installing the Oracle Cleint . That did n't give any result .

since ODBC test is working fine using DSN , there is no problem till the ODBC connection.

Now I am more worried about the MSDTC entries (MTxOCI) in the registory . Can someone suggest the correct entries for Oracle 8 software It is pointing to oci.dll now ...

Any other suggestions are appreciated ..

thanks
Manoj