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?

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

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

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

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

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

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. :o meh.
I will post back here if I find out what actually fixes this.

Thanks again,
Chris

Thank YOU, Chris :)

Friedrich