Results 1 to 12 of 12

Thread: [RESOLVED] [winsock] error 10035

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Resolved [RESOLVED] [winsock] error 10035

    hi all,
    on my client/server app.. i very frequently i receive this error --error number 10035-- on winsock server.. but nothing shows on the client .. the client is still connected..or gets connected.. this happens mostly in the debugging mode.. it is quite annoying as i can't debug my codes.. i am connecting multiple clients on multiple server..

  2. #2
    Member
    Join Date
    Feb 2009
    Posts
    38

    Re: [winsock] error 10035

    Are you under Windows Vista? I seem to encounter this problem when I was running Vista and VB was unable to bind to a local port.

  3. #3

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    i am using windows 7 actually

  4. #4
    PowerPoster
    Join Date
    Jan 2008
    Posts
    11,074

    Re: [winsock] error 10035

    Error 10035:

    Problem: Resource temporarily unavailable.

    Solution: This is a temporary condition and later calls to the same routine may complete normally. The socket is marked as non-blocking (non-blocking operation mode), and the requested operation is not complete at this time.

    Since it occurs on the server side only you have no way of knowing this on the client side so I do not know how you could repeat the call.

    Are you absolutely sure there is no client side evidence of this occurance? Do you have a Winsock_Error event on the client(s) applications to trap errors when they occur?
    Last edited by jmsrickland; Mar 2nd, 2009 at 12:01 PM.

  5. #5

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    Quote Originally Posted by jmsrickland
    Error 10035:

    Problem: Resource temporarily unavailable.

    Solution: This is a temporary condition and later calls to the same routine may complete normally. The socket is marked as non-blocking (non-blocking operation mode), and the requested operation is not complete at this time.

    Since it occurs on the server side only you have no way of knowing this on the client side so I do not know how you could repeat the call.

    Are you absolutely sure there is no client side evidence of this occurance? Do you have a Winsock_Error event on the client(s) applications to trap errors when they occur?
    yes i am 100% sure there is nothing happening on the client side.. but on server side it accepts the connection and then moves on to server_error event.. i have just installed sp6 on my machine.. since then i am not having any problem.. i will give it a day ..if everything works fine i shall mark this thread resolved.. for even i did google around about this error.. everyone were facing problems like mine but there was no solution .. anywayz thank you jmsrickland u are always there to help ..

  6. #6

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    the problem still exists.. after a successful connection why does the server throw an error number 10035?

  7. #7
    PowerPoster
    Join Date
    Jan 2008
    Posts
    11,074

    Re: [winsock] error 10035

    OK, I will ask you again. Do you have a Winsock_Error(Index) event in your client application and are you checking for any and all errors? If an error occurs at the server side an error should also occur at the client side.

  8. #8

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    Quote Originally Posted by jmsrickland
    OK, I will ask you again. Do you have a Winsock_Error(Index) event in your client application and are you checking for any and all errors? If an error occurs at the server side an error should also occur at the client side.
    no nothing happens on the client side.. if i don't add the sub "winsock_error()" on the server side..then it works fine.. what i mean is ..even with the error the connection is still there and works most of the time... i rechecked and rechecked my codes and i found out that although different socks from the client are being connected to different socks in the server .. the data arrival event is handled by the same socks for different client.. is this an issue ??

  9. #9
    PowerPoster
    Join Date
    Jan 2008
    Posts
    11,074

    Re: [winsock] error 10035

    the data arrival event is handled by the same socks for different client.. is this an issue ??

    Yes! Different clients must have different sockets on the server side

  10. #10
    PowerPoster
    Join Date
    Feb 2006
    Posts
    22,294

    Re: [winsock] error 10035

    This error usually occurs in programs that do not drive output using the SendComplete event. If you call SendData a subsequent time without waiting for SendComplete on the previous send you can get this error if there is no room in the underlying socket's send buffer.

    Getting the error on Accept seems very odd, but it seems to be possible... hmm, are you sure you don't SendData right away? I've never seen this.

  11. #11

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    phew! i finally got it working.. i can connect more than 3000 sockets from the client side to the server which in turn will use the same amount of sockets..
    no problem while connecting ..or sending messages..how over i have one issue.. i don't know if its normal or my codes.. as the socks on the client side send data the data arrival in the server is fired only after all the socks in the client side sends the data.. it would be better if the data are process as it is being sent.. i am uploading my project perhaps one of you could take a look if you are free.. thank you..
    Last edited by pannam; Mar 4th, 2009 at 07:33 PM.

  12. #12

    Thread Starter
    Hyperactive Member
    Join Date
    Feb 2008
    Posts
    327

    Re: [winsock] error 10035

    now, all's working fine.. i made some adjustments. and its all done.. now.. the transactions take simultaneously ..for those who want multi connection [maximum connection]on multiple server ..this might come handy.. i am uploading the project..
    Attached Files Attached Files

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width