Hi all,

I have installed the PC client for ASE 12.5 onto my brand new compaq
nx9010 (pentium 4 chip). I got past the java related install errors,
and then worked my way around the Sybase Central Java bat file fixes.

All the apps seem to be running (there was a LANG setting that kept
dsedit away for a while) - now I just can't get a connection. In
ocscfg I have set the SYBASE and SYBASE_OCS vars. When I create a TCP
based server in dsedit, the ping fails with the error:

The local machine has not set up a driver for protocol TCP.

In ocscfg the second tab (Net-Library) shows platform NT/Win95 and
protocol TCP is associated with driver NLWNSCK.

What am I doing wrong? Any help greatly appreciated.
thanks
mike

Hello,

Check your PATH environment variable. Make sure it has
"c:\sybase\ocs-12_5\dll" in it so that dsedit can find
and load "nlwnsck.dll".

If that looks OK, make sure you don't have any duplicate
Sybase libraries laying around (old installs use to install
into c:\windows\system32).

If that looks OK, make sure you have the correct version of
"nlwnsck.dll":
C:\sybase\OCS-12_5\dll>find /I"Intel" nlwnsck.dll

---------- NLWNSCK.DLL
Sybase WinSock Driver/12.5/P/PC Intel/BUILD125-005/OPT/Sat May 19 14:48:00 2001

mike reed wrote:

Thanks for your quick response Neal,

In the end, the problem was the definition of the SYBASE_OCS variable.
Somehow (me maybe?) it was set up as SYBASE_OCS=%SYBASE%\OCS-12_5.
This was obvious when I looked closely at the dsedit 'Select Directory
Service' startup dialog box. The config file appeared as:
C:\SybaseC:\Sybase\OCS-12_5\ini\libtcl.cfg

Updating SYBASE_OCS=OCS-12_5 sorted this out, and the config file
became the much-more-usable:
C:\Sybase\OCS-12_5\ini\libtcl.cfg

To be honest, I've been clicking through the 'Select Directory
Service' startup dialog box for so long that it became invisible.
Guess it's time to slow down.

mike

Sybaseneal <user (AT) invalid (DOT) domain> wrote