TEXIS daemon reporting error

carsten.harnisch1 · Post by **carsten.harnisch1** » Thu Jul 19, 2001 1:58 pm

I got message in the log-file of the daemon running under W2K reporting the following error/warning :

000 getsockname: WSAENOTSOCK - the descriptor is not a socket in the function: ezsportnum

(actually we are running on our own special port)

What is this error ?

Post by **mark** » Thu Jul 19, 2001 2:15 pm

That implies that you are trying to perform socket operations on a non-socket. We need more details about what you're doing and when this error is occuring.

carsten.harnisch1 · Post by **carsten.harnisch1** » Thu Jul 19, 2001 2:37 pm

seems to be continously :

000 getsockname: WSAENOTSOCK - the descriptor is not a socket in the function: ezsportnum
200 login from 192.168.0.5:1832 as at 01/07/19 16:51:53 ok
000 getsockname: WSAENOTSOCK - the descriptor is not a socket in the function: ezsportnum
200 login from 192.168.0.5:1835 as at 01/07/19 17:06:43 ok

acutally the daemon is accessed by a dll on running on the same machine.
This is what is done (pseudo code) :

serveruser (szUser);
serverpass (szPassword);
se = openserver(szServer,szPort);
n_setdatabase(se, szDatabase);
tsq = n_opentsql(se);
n_settsql(tsq, szCmd);
n_exectsql(tsq);
n_closetsql(tsq);
closeserver(se);

Post by **mark** » Thu Jul 19, 2001 4:01 pm

I guess you're running in client-server mode but on the same machine. Windows sometimes forgets that a socket is a socket when it's on the same machine. The error will not hurt and may be safely ignored.

If you're doing everything on the same machine you may be better off compiling "flat" by defining NCGDIRECT when compiling the Texis client. Then you won't need the texisdnt server.