WSAENOTSOCK (10038) error

[happiness4all]

i am using multithreaded server and getting this error when several clients communicate with server at the same instant. otherwise there is no problem..
WSAENOTSOCK (10038) its description is:
The socket input parameter is not a valid socket handle (either it never was valid, it's a file handle (not a socket handle), or if it was a socket handle, it has been closed).

but m doin nothing like this..so how to remove this error..

[Banfa]

Are you getting this error at the client or server end?

What is the networking software running at each end?

[happiness4all]

at server end..
i didnt get wat u mean by networking software running at each end.....

[Banfa]

what application running on the server is the client connecting to?

[happiness4all]

its just a simple client and server program..
established a server and binded it a particular ip and port no.
client connects to this port..and sends a msg
which server reads and replies back to the client.
m using blocking send and recv
and multithreaded server

[Banfa]

This is the error description you posted

WSAENOTSOCK (10038) its description is:
The socket input parameter is not a valid socket handle (either it never was valid, it's a file handle (not a socket handle), or if it was a socket handle, it has been closed).

This means that the socket handle you passed to the function in question is not valid. The error message given reasons why the socket input parameter would not be a valid handle, you assert that none of these cases apply.

In this case then somehow the socket parameter is not a valid for a reason not mentioned in the error message. The most likely cause is a memory corruption of some sort, which would be quite easy in a multi-thread program.

Therefore I suggest that you should examine the program code for possible causes of memory corruptions. Additionally you could try outputting the socket handle values as they are created and the outputting the handle and location when you get the error so that you can work out which socket handle it is that has been corrupted.

[mandien]

Hello to everybody,

Sorry for my english, it's not my first language.

Thanks for your help, I was with the same problem and I have found the solution
with your helpful explanations. I had the error 10038 with the recv function,
and I have printed on screen the socket number descriptor before and after
the bug. This socket number is changed by another process I think!
All you have to do, is to store the socket number descriptor before you use
the recv function and you put it back in the recv function call.
--> int dSC; // To store socket number
int socket_desc = 0; // To save socket number after socket function call
dSE = socket(AF_INET,SOCK_STREAM,0)
--> nb_char_received = recv(socket_desc, buffer, sizeof(char)*500, 0);
remark: You can print dSC and socket_desc to see that they have not the same value when the error 10038 happen.