Very Computer

by **Daniel Faense** » Tue, 17 Jun 1997 04:00:00

Dear colleagues,
I am new to sybase, so I suppose my problem is easy solved.
Currently I develope a small program as a template for educational
purposes (learning embedded SQL). Compiling works fine (I adapted
the sample in $SYBASE/samples/esql/example1.cp).
Problems occure when running the code. The first ESQL call (that is

EXEC SQL CONNECT :username IDENTIFIED BY :password USING :server;

) leads to the error message

Open Client Message:
Message number: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (131)
Message String: ct_init(): network packet layer: internal net library
error: Error string not available

Access via isql is possible.
I would like to ask our sybase admin, but since last week it is me,
myself and I, who tried hard but was no big help.

Thank you for your help

Daniel Faensen

--
*********************************************************
Daniel Faensen
Graduiertenkolleg Signalketten in lebenden Systemen
TU Berlin Tel.: +49-30-314 73344
Franklinstr. 28-29 Fax : +49-30-314 73177

Germany http://www.inf.fu-berlin.de/~faensen
*********************************************************

by **Bj?rn Bjerkel** » Fri, 20 Jun 1997 04:00:00

> Dear colleagues,
> I am new to sybase, so I suppose my problem is easy solved.
> Currently I develope a small program as a template for educational
> purposes (learning embedded SQL). Compiling works fine (I adapted
> the sample in $SYBASE/samples/esql/example1.cp).
> Problems occure when running the code. The first ESQL call (that is

> EXEC SQL CONNECT :username IDENTIFIED BY :password USING :server;

> ) leads to the error message

> Open Client Message:
> Message number: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (131)
> Message String: ct_init(): network packet layer: internal net library
> error: Error string not available

Encountered the same problem when i wrote some ESQL programs running
Solaris 2.5. Compiled, and everything was fine, but when i tried to run
the executable, some wierd errormessages started occuring. I then tried
to execute the programs a couple of times directly after each other.
And, allways, after the second (or sometims third attempt) the program
ran fine, whithout any errors. Perhaps not suitable for educational
purposes, but it worked.

Bj?rn Bjerkeli
RNoAF, Materiel Command, CMT-project
Phone: 47-63-80-8719

Very Computer

embedded SQL: need help

embedded SQL: need help

embedded SQL: need help