ERROR: The ODBC engine cannot be found. 2

[briglass]

Hello,

I'm trying to help a client solve a problem they are having in SAS, although they live across the country and I am unable to play with their system. We are corresponding via email.

I had him send me the SAS log for the SAS job in question, and the error was:

Connect to odbc ("dsn=MS Access 97 Database; DBQ=&MDBFILE");                           
ERROR: The ODBC engine cannot be found.

I asked him to check his Data Source ODBC Connections in the Control Panel and this is what he sent me back:


Here's what was listed under the 'User DSN' Tab:


dBase Files Microsoft dBase Driver (*.dbf)
dBase Files-Word Microsoft dBase VFP Driver (*.dbf)
Deluxe CD Microsoft Access Driver (*.mdb)
Excel Files Microsoft Excel Driver (*.xls)
FoxPro Files-Word Microsoft FoxPro VFP Driver (*.dbf)
MS Access Database Microsoft Access Driver (*.mdb)
Visual FoxPro DataBase Microsoft Visual FoxPro Driver
Visual FoxPro Tables Microsoft Visual FoxPro Driver

Here's what was under the 'System DSN' Tab:

AS400 Microsoft Access Driver (*.mdb)
ECDC Music Microsoft Access Driver (*.mdb)
MS Access 97 Database Microsoft Access Driver (*.mdb)


~

The only thing I notice that is different between his configuration and my configuration is that I have only ever seen "MS Access 97 Database Microsoft Access Driver (*.mdb)" under the 'User DSN' tab, I have never seen just plain "MS Access Database Microsoft Access Driver (*.mdb)"

I'm not sure if this has anything to do with the problem.

Does anyone have any ideas as to why this might be occuring?




Thanks, (-:
Brian

 

[jymm]

a while back I had problems with an ODBC connection to an access db within SAS --- turned out that the problem was capitilazation...

My Program was looking for 'Plant' an their ODBC connection was configured as 'plant' (or maybe it was 'PLANT')... ANYWAY - once they got the ODBC configured the same it was gravy ---

not sure this will help, but it is worth a try

 

[klaz2002]

Brian,

The first thing that your client should do is run the PROC SETINIT to see if they have the SAS ODBC engine licensed. On a windows OS the capitilization shouldn't be an issue. (I just checked and SAS ignores the different case, but you seem to have the AS400 so maybe....)

Another thing that worked for me connecting to Ms SQL server was the DSN param should only have the name of the dsn file. Leave out the second peram. Use another way to get to the correct table. In my case I put the userid and the password after the dsn param.

Ex.
libname test odbc dsn="mysql db" uid:user1 pwd:xx;

I hope that this helps.

PS Connect to uses the ACCESS engine but check the setinit anyway you may find something.

Let us know how corrected the problem.

Klaz

 

[briglass]

Here is how his output read (note: I removed his site name and site number for privacy purposes).

NOTE: Copyright (c) 1999-2001 by SAS Institute Inc., Cary, NC, USA.           
NOTE: SAS (r) Proprietary Software Release 8.2 (TS2M0)                        
      Licensed to VETERANS MEDICAL RESEARCH FOUNDATION, Site 0038844124.      
NOTE: This session is executing on the WIN_PRO  platform.                     
                                                                              
                                                                              
                                                                              
NOTE: SAS initialization used: 
real time           6.20 seconds
cpu time            1.74 seconds
                                                                              
1    proc setinit; run;

NOTE: PROCEDURE SETINIT used:
      real time           0.17 seconds
      cpu time            0.06 seconds
                                                                              
Original site validation data 
Site name:    'SITE NAME'.
Site number: 12345678.    
Expiration: 14DEC2004.     
Grace Period:  45 days (ending 8JAN2005).   
Warning Period: 45 days (ending 14MAR2005).
System birthday: 23NOV1992.Operating System:   WIN.
Product expiration dates:
---Base Product     14DEC2004

Thanks, (-:
Brian

 

[briglass]

Crud, well I didn't delete the site name and number in both places... just ignore it?

Thanks, (-:
Brian

 

[klaz2002]

Brian,
Looks like your client didn't license the ODBC engine.
Klaz

 

[ChrisW75]

Yep, no licence to SAS/ACCESS for PC so you have no ODBC Engine to access.

There may be other ways around it though, check out this on SAS Support

http://support.sas.com/techsup/unotes/V6/F/F453.html

Enjoy.

 

[briglass]

Thanks guys!

I told him my software is fine, he's just a bum. But not in those words!



Thanks, (-:
Brian

 

[Giraffe69]

Brian,
If your client can run SAS on a server aswell as locally it may be that the client and server have different products licensed. You could try remote submitting proc setinit to see if access to odbc is present.
Just a thought

 

[briglass]

Giraffe69-

Thanks for the response. How would I go about that?




Thanks, (-:
Brian

 

[Giraffe69]

try

rsubmit;
proc setinit; run;
endrsubmit;

 

[Giraffe69]

Brian
Ignore me - sas/connect would be required on the client to connect to a server - I can see from the setinit above that this isnt present.
sorry