SQLBase 09293 GCI NDL Error
Tor-Arne W. Berger
ODBC supplied from Crystal (Seagate) a driver which is made by Intersolv.
When trying to connect, I get the above described error. According to
error.sql:
09293 GCI NDL Cannot load any communication DLLs, network may not be
installed
Reason: This error is currently undocumented.
Remedy: Contact your local Centura Software Corporation certified
technical support center for assistance.
I can connect fine from SqlTlk16. My parameters in SQL.INI define both 16
and 32 bit connectivity as per Centuras specifications. I use TCP/IP to
connect from SqlTlk16 to by NT 4.0 server.
Getting help from Centura on this is like pulling teeth - and like the
dentist you also have to pay for it. Since this is an error they haven't
bothered to document they should provide some tech info for free - at least
a white paper or something. Anyhow, enough griping, I'll let them know at
the user conferece.
If anyone out there can help me, I would greatly appreciate it!
Tor-Arne
email: t_be...@email.msn.com
Michael Vandine (Centura)
Can you please post your sql.ini file. There's a large community here that
should be able to help you with your problem if you give us enough
information...
Michael Vandine (Centura - Asia Pacific)
[TeamAssist]
-----------------
Tor-Arne W. Berger wrote in message <6vgl61$5m...@horizon.centurasoft.com>...
Carsten Barner Nielsen[TAO]
>I am trying to connect from Crystal Reports 6.0
Maybe a stupid question, but is that a 16 bit or 32 bit 'thing' ?
> to SQLBase 6.1.2
What's that ? Do you use a 16 bit version (DBWSVR.EXE) or 32 bit
DBNT*SV:EXE) ?
>using the ODBC supplied from Crystal (Seagate) a driver which is made by Intersolv.
Pls, supply more info, is that supplied driver 16 bit .or. 32 bit ?
I'd recommend you use a 32 bit version of Crystal with 32 bit ODBC and
32 bit SQLBase.
>Getting help from Centura on this is like pulling teeth - and like the
>dentist you also have to pay for it.
I have heard that in Sweden they pull out teeth's at 1/10 the price !
>Since this is an error they haven't
>bothered to document they should provide some tech info for free - at least
>a white paper or something. Anyhow, enough griping
I'm not the one to defend Centura, error or not, ODBC work perfectly
ok if you set it up correct .....
>I'll let them know at the user conferece.
Interesting ... I'll be all ears !
You may want to download ODBCT16.exe & ODBCT32.exe included in
ODBCtest.zip from http://inside.centurasoft.com --> 3 Party Section,
as 'they' write in the docs: "Pls, verify your ODBC connection before
you try to connect from SW/CTD (.or. Crystal)"
Regards,
Carsten Barner Nielsen
[TeamAssist]
ISS Data A/S, Copenhagen, Denmark
email: iss...@image.dk
Joachim Meyer
I've had some similar problems as well.
On my site it helped to point a searchpath to the Centura directory, so that
the client can find it's DLLs.
You should also make sure, that you specified the right COMDLLs in your
SQL.INI
--
Joachim Meyer
BASYS EDV-Systeme GmbH
Jo...@basys-bremen.de
Visit the CenturaFAQ at
http://ourworld.compuserve.com/homepages/ThomasAlthammer/
Tor-Arne W. Berger
32 bit SQLBase for NT, 32 bit ODBC drivers for 32 bit Crystal Reports, 16
bits SQLWin apps using the database with 16 bit TCP/IP client drivers.
SQL.INI follows at the end.
Note that I have advanced somewhat, I now get a 401 DBA COD - Cannot open
database error as I try to log on. My SQLWin apps using TCP/IP and 16 bit
native connectivity still works like a charm.
[win32client.dll]
comdll=sqlodb32
[win32client]
clientname=ODBCUser
[odbcrtr]
odbctrace=off
odbctracefile=sql.log
[win32client.ws32]
serverpath=server1,10.0.0.2/*
[win32client.odbc]
[winclient.dll]
comdll=sqlwsock
[winclient.sqlwsock]
serverpath=server1,10.0.0.2/*