[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::odbc_rdb_driver

Title:DEC ODBC Driver
Notice:DEC ODBC Driver V2.0 Now Available
Moderator:SQLSRV::MAVRIS
Created:Tue Dec 29 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1357
Total number of notes:4864

1346.0. "FTLEXEERR" by ORAREP::NNTPD::"aumayrw@mail.dec.com" (Werner Aumayr) Tue May 27 1997 15:16

Customer has:

OpenVMS Alpha V6.2
Rdb V6.1-0
odbc-Treiber V 2.00.1111

Win 3.1, Access 2.0

There occur two mysterious failures:

1.  It sometimes happens:

ODBC-call failed.
[DEC][ODBC][RdB]%SQLSRV-F-FTLEXEERR, Fatal executer errot
%SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XL,
PC=!XL, 
PS=!XL
(#-2035)


2. snd sometimes

[DEC][ODBC][RdB] send () Ret-1 Err#10038 WSAENOTSOCK
File descriptor not a socket (#-2003)


Any ideas?????

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
1346.1Start with sys$manager:sqlsrv$.logSQLSRV::MAVRISSue Mavris - smavris@us.oracle.comTue May 27 1997 16:1330
>1.  It sometimes happens:
>
>ODBC-call failed.
>[DEC][ODBC][RdB]%SQLSRV-F-FTLEXEERR, Fatal executer errot
>%SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XL,
>PC=!XL, 
>PS=!XL
>(#-2035)

This means the execute server access violated and terminated.  To find out 
why, look at sys$manager:sqlsrv$.log.  It should have an entry for the failed 
execute server and should point to the execute server log file.  The execute 
server log file should point to a dump file that can help us determine the 
cause of the accvio.  Please make the executor log and dump file available to 
us.

>2. snd sometimes
>
>[DEC][ODBC][RdB] send () Ret-1 Err#10038 WSAENOTSOCK
>File descriptor not a socket (#-2003)

This usually means the SQL/Services server is not running.  Check to make 
sure SQL/Services is running on the node you're directing your connect to.  
If SQL/Services terminated abnormally, there should be information in 
sys$manager:sqlsrv$.log to help determine the cause of the termination.  If
SQL/Services is running when you get this error, verify that it is listening 
on the transport you're using from your ODBC client (sqlsrv$.log will also 
give you this information).

Sue
1346.2148.87.13.1::EKREISLEErich KreislerThu Jun 05 1997 08:056
> rdb 6.1-0

make sure you have the latest 6.1 versions installed:
Rdb 6.1A ECO 1 and SQl/Services 6.1-02

erich