PDA

View Full Version : Problems Submitting WU's?


Ad Rock
03-29-07, 07:43 PM
Well I have about 5 WU's cached on one instance of my FAH set-up here on my main computer and have been unable to upload them back to Stanford. I am sometimes able to upload a WU or two but I never am able to upload all of them, and now I am pilling up more and more.

Here is the error log:

[19:37:51] + Attempting to send results
[19:38:22] Couldn't send HTTP request to server (wininet)
[19:38:22] + Could not connect to Work Server (results)
[19:38:22] (171.65.103.162:8080)
[19:38:22] - Error: Could not transmit unit 00 (completed March 20) to work serv
er.


[19:38:22] + Attempting to send results
[19:38:57] Couldn't send HTTP request to server (wininet)
[19:38:57] + Could not connect to Work Server (results)
[19:38:57] (171.65.103.100:8080)
[19:38:57] Could not transmit unit 00 to Collection server; keeping in queue.


[19:38:57] + Attempting to send results
[19:39:35] Couldn't send HTTP request to server (wininet)
[19:39:35] + Could not connect to Work Server (results)
[19:39:35] (171.64.122.141:8080)
[19:39:35] - Error: Could not transmit unit 03 (completed March 23) to work serv
er.


[19:39:35] + Attempting to send results
[19:40:13] Couldn't send HTTP request to server (wininet)
[19:40:13] + Could not connect to Work Server (results)
[19:40:13] (171.65.103.100:8080)
[19:40:13] Could not transmit unit 03 to Collection server; keeping in queue.


[19:40:13] + Attempting to send results
[19:40:52] Couldn't send HTTP request to server (wininet)
[19:40:52] + Could not connect to Work Server (results)
[19:40:52] (171.65.103.160:8080)
[19:40:52] - Error: Could not transmit unit 05 (completed March 25) to work serv
er.


[19:40:52] + Attempting to send results
[19:41:31] Couldn't send HTTP request to server (wininet)
[19:41:31] + Could not connect to Work Server (results)
[19:41:31] (171.65.103.100:8080)
[19:41:31] Could not transmit unit 05 to Collection server; keeping in queue.


[19:41:31] + Attempting to send results
[19:42:09] Couldn't send HTTP request to server (wininet)
[19:42:09] + Could not connect to Work Server (results)
[19:42:09] (171.65.103.160:8080)
[19:42:09] - Error: Could not transmit unit 08 (completed March 28) to work serv
er.


[19:42:09] + Attempting to send results
[19:42:48] Couldn't send HTTP request to server (wininet)
[19:42:48] + Could not connect to Work Server (results)
[19:42:48] (171.65.103.100:8080)
[19:42:48] Could not transmit unit 08 to Collection server; keeping in queue.


[19:42:48] + Attempting to send results
[19:43:28] Couldn't send HTTP request to server (wininet)
[19:43:28] + Could not connect to Work Server (results)
[19:43:28] (171.65.103.160:8080)
[19:43:28] - Error: Could not transmit unit 09 (completed March 29) to work serv
er.


[19:43:28] + Attempting to send results
[19:44:07] Couldn't send HTTP request to server (wininet)
[19:44:07] + Could not connect to Work Server (results)
[19:44:07] (171.65.103.100:8080)


Anyway one have any idea's for me to try?

Jon
03-29-07, 07:53 PM
Run the client with the -configonly flag to reconfigure. Set proxy and use Internet Explorer settings to "no". Start the client back up after finishing the config and see if they transmit.

pscout
03-29-07, 08:06 PM
since you say that it can sometimes xmit the wu, i doubt that it is the ie proxy issue? I would expect it to always fail or work if that was the issue.

after figuring out what your probable network issue is ... or maybe as a temp workaround .... since you said you can sometimes xmit them ...

... to speed up the attempts, stop the normal client (service?)

and run the console from a shortcut with just the "-send all" flag.

If you start the console normally, it only retries upload every 6 hours.

So you can just run with the send all repeatedly until you get them submitted.

You can open up task manager, network to let you keep an eye on any progress. If you see network activity drop to 0, just stop the "-send all" console with ctrl-c and relaunch the "-send all" shortcut.