Conference orarep::nomahs::odbc_rdb_driver

1309.0. "Access violation ODBC -> SQL on VAX" by ORAREP::SWETSC::WESTERBACK (Panta rei) Thu Mar 06 1997 06:33

    We have a problem with ODBC from Windows 95 or NT 4.0 to SQL on VMS 
    after an upgrade from DECstep 6 to SEPS97, which means VMS from 6.1 
    to 6.2, SQL from 6.0-0 to 6.1-04.
    
    We use ODBC Driver for RDB 2.10.11
    
    A user tries to connect from Access 95 with ODBC using his VMS username 
    and password (which work OK for normal login)
    
    He gets an access violation on the PC (Windows 95), but in the
    sqlsrv$.log we see:
    
    0304 1434274295670  %SQLSRV-F-GETACCINF, SQL Services authorization
    failed
    0304 1434274295670  -SQLSRV-F-INVPWD, Invalid password
    0304 1434274295670  -SQLSRV-I-LOGINFAILINFO, Username: OLOFSSON;
    client: 16.203.64.221
    0304 1434274395670  %SQLSRV-F-ERRASC, Error during association
    0304 1434274595670  -SQLSRV-F-GETACCINF, SQL Services authorization
    failed
    
    If he enters an incorrect password from ODBC, it behaves OK, he gets 
    a message about invalid password, but still the same entry in sqlsrv$.log.
                                                                    
    
    This worked very well before the upgrade
    
    We see no intrusion records on the VAX, nothing in the audit file.
    
    It seems the connection to the server is OK. A SS_GENERIC logfile is
    created. If I try to open a non-existing rdb file, I get a message
    saying this file is unknown to rdb. It's only when I try to open an
    existing db I get the access violation. The db files  were successfully
    converted from 6.0 to 6.1 after upgrade. Can there be some other mismatch?
    
    I can attach to the same database from a DECstep 6 system.
    
    One other strange thing is that I installed ODBC on my own NT 4.0
    workstation to test. I get the same kind of access violations, but
    these are not logged in SQLSRV$.LOG. (only if I actually use wrong
    password). The other user is logged as in .0 every time he gets an
    access violation.
    
    Any ideas anyone?
    
    Hans

Did they upgrade SQL/Services too?

The latest version of SQL/Services is 6.1 Eco 2.

Renee

    Yes SQL Services was upgraded from 6.0 to 6.1, no ECO. Could 
    the ECO be relevant here?
    
    Hans

    OK, problem seems to be solved, we attached using class GENERIC as 
    before, but now we must use class V61, then it works.
    
    Rgds,
    Hans