Question : Error message trying to connect to Sybase server ASE 12.0

I'm trying to connect to my Sybase server ASE 12.0 but i'm getting the below error message. Any ideas?

Error:  "ct_connect(): network packet layer: internal net library error: unable
to find an available protocol driver structure."

I've found a forum that said this maybe because my OpenClient isn't setup correctly and to use the OCSCFG.EXE utility to see what protocols are defined. Not sure how to use this utility or what to look for. HELP!!!!!!!!!!!!!!!!

Answer : Error message trying to connect to Sybase server ASE 12.0

Long ago in a galaxy far away... I seem to remember there was an issue with Access and ODBC connecting to Sybase.  There was a funky registry key and setting you have to make in order to get this to work.  Let's see.  I had this stuff in a file called "ODBC You ain't gonna believe this".
--------------------------------------------------------------------------------------------------------------------------
Windows NT/2000/XP Implementation

Double click on the odbcsyb12.reg file in the t:\windows.XX\ directory (where XX is one of NT,2K,XP).

Users of Windows NT/2000/XP and Office may be required to add a registry entry to fix a problem with the Sybase ASE driver specifically related to Microsoft Access. The entry should be placed in

HKEY_LOCAL_MACHINE/Software/ODBC/ODBC.INI
for User DSNs, and

HKEY_CURRENT_USER/Software/ODBC/ODBC.INI
for System DSNs

for each Data Source. It should be named WorkArounds2 and have a string value of 40960.

This fix will need to be applied if you are receiving a "reserved error" of -7748.
--------------------------------------------------------------------------------------------------------------------------

I don't remember where I found this so I can't give credit where it is due.  I am also not certain this is your problem but if you are running an older version, you will need this anyway.

BTW, HAFAILOVER may be a networking issue.  Are you using High Availability anywhere in the organization and/or do you have more than one network adapter either on the client machine or on your server?

BTW2, for best results, you should be using "System" DSNs in ODBC, not User.

Regards,
Bill