+ Reply to Thread
Results 1 to 8 of 8

Thread: WUPDATE network comm error 503010069

  1. #1
    Join Date
    Nov 2007
    Location
    Malone, NY
    Posts
    69

    Default WUPDATE network comm error 503010069

    Getting this error back 503010069. User is going through a proxy -localhost :8080
    Is this reporting the Winsock error 10069?
    coffee.cup not found. Programmer halted.

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: WUPDATE network comm error 503010069

    Hello,

    Yes, error "503010069" is reporting WinSock Error 10069.

    The first 4 digits tell us where in the HTTP component the error happened (5030 = "connect" API). The code after that is the WSAGetLastError() API return code.

    Friedrich

  3. #3
    Join Date
    Nov 2007
    Location
    Malone, NY
    Posts
    69

    Default Re: WUPDATE network comm error 503010069

    Thanks - then the 10069 is that my server is actively refusing the connection. -Password issue?
    For future reference, do you have a list of those other 4 digit prefixes you could share? 5040, 5060?

    chris
    coffee.cup not found. Programmer halted.

  4. #4
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: WUPDATE network comm error 503010069

    Chris,

    Not sure if this is a password issue. 10069 is a "Disk quota exceeded" error:
    http://support.ipswitch.com/kb/WSK-19980714-EM03.htm

    5020 - After the "socket" API call.
    5030 - After the "connect" API call.
    5040 - After the "send" API call which returned a SOCKET_ERROR.
    5050 - After the "recv" API call which retunred a SOCKET_ERROR and WSAGetLastError returned WSAETIMEDOUT.
    5060 - HTTP stream did not include data package size information.
    5070 - After the "recv" API call (Atomic clock functionality only).

    999 - WinSock reported WSAECONNRESET; 10054. Connection reset by peer. That means an existing connection was forcibly closed by the remote host. The HTTP component tries to reconnect but this also fails. As a result, all sockets are closed and program is terminated.

    Friedrich
    Last edited by linder; 05-03-2010 at 08:30 AM.

  5. #5
    Join Date
    Nov 2007
    Location
    Malone, NY
    Posts
    69

    Default Re: WUPDATE network comm error 503010069

    Thanks, Friedrich. I had looked up that code before somewhere and it said "actively refused connection." Now from your link and the MSDN link below, I get the right explanation. I'm not sure though whether that is from the client or the server side.
    http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx
    coffee.cup not found. Programmer halted.

  6. #6
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: WUPDATE network comm error 503010069

    Chris,

    The connect() API returns SOCKET_ERROR -- that means it can't connect to the server. Directly after that, WSAGetLastError is called. The question is whether we can trust the return value retrieved from WSAGetLastError (especially in the Proxy Server case). I don't know

    Friedrich

  7. #7
    Join Date
    Nov 2007
    Location
    Malone, NY
    Posts
    69

    Default Re: WUPDATE network comm error 503010069

    Friedrich,

    Good point. At least knowing when the error occurred and what it was reported as, we don't have to flail around so much trying solutions. meh.
    I will post back here if I find out what actually fixes this.

    Thanks again,
    Chris
    coffee.cup not found. Programmer halted.

  8. #8
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: WUPDATE network comm error 503010069

    Thank YOU, Chris

    Friedrich

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

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