F@H 5.03 not returning work [(wininet) - SET USE IE to NO!]

[PRJKITCH]

hi guys any ideas to why my 5.03 windows client isnt returning the work??

From log

[11:06:32] Writing local files
[11:06:32] Completed 1140000 out of 2000000 steps (57)


[12:02:46] + Attempting to send results
[12:03:17] Couldn't send HTTP request to server (wininet)
[12:03:17] + Could not connect to Work Server (results)
[12:03:17] (171.64.65.111:80)
[12:03:17] - Error: Could not transmit unit 06 (completed August 5) to work server.


[12:03:17] + Attempting to send results
[12:03:20] Error: Got status code 503 from server
[12:03:20] + Could not connect to Work Server (results)
[12:03:20] (171.64.122.76:80)
[12:03:20] Could not transmit unit 06 to Collection server; keeping in queue.
[12:21:12] Writing local files
[12:21:12] Completed 1160000 out of 2000000 steps (58)
[13:27:29] Writing local files
[13:27:29] Completed 1180000 out of 2000000 steps (59)
[14:32:59] Writing local files
[14:32:59] Completed 1200000 out of 2000000 steps (60)
[15:36:00] Writing local files
[15:36:00] Completed 1220000 out of 2000000 steps (61)

any ideas ok i know this cpu is only giving 200 ppd but is starting to get annoying
seem to have no probs with my gpu client thats going great guns as usual

[7im]

[12:03:17] Couldn't send HTTP request to server (wininet)

Tells me you need to reconfigure your client to NOT use IE SETTINGS. Connection Tab, make sure both IE and Proxy are UNCHECKED. Those are the default settings (unchecked) and work the best for most people.

[gwildperson]

Error 503 means the server is temporarily too busy to accept the upload.

If setting use_ie to no doesn't fix it, the best thing to do is ignore it since you can't do anything about it. The deadlines for projects on that server are several weeks, so there's not much danger of the WU expiring before the client retries to upload when the server is less-busy.

[7im]

GW is corect.

Please note I checked server 171.64.65.111 before posted, and it wasn't busy. Although that does not preclude Stanford from possibly having network issues instead.

Change the setting, and then post again if it doesn't work.