F@H: Completed work unit that won't transmit

[alnitak]

Guys, one of my PCs recently completed a work unit, but it has not been transmitted up to the server. Since this WU was completed the PC has been rebooted several times, and even had another WU complete and successfully transmit today. Is there a way to force this problematic WU to transmit before it expires?



[14:40:40] + Attempting to send results
[14:40:41] - Couldn't send HTTP request to server

[14:40:41] + Could not connect to Work Server (results)
[14:40:41] - Error: Could not transmit unit 04 (completed Feburary 17). Keeping unit in queue.

[14:40:41] + Working...
[14:41:08] Finished a frame (8)

 

[Reel]

bump for jilechty the F@H guru to see.

 

[ProviaFan]

LOL, I'm a F@H guru? Didn't know that. :Q

Anyway, what's probably happened is that the server that you got that particular WU from (there are many different servers assigning different kinds of WUs) went down. Occasionally, you can try sending the work unit in (a few times per day, if you can) by exiting the F@H CLI and opening a command prompt. Use cd \Program Files\Folding@Home\ (or replace with whatever directory you have it put in) to get to where the FAH3Console program is, then type fah3console -send all. That should force it to flush its queue. After that you can restart the client as you would normally. If it goes a week or so without still being able to send the WU, you might have to manually delete it from the queue (I know it sucks having to loose all that work, and have had to delete a few WUs myself 🙁). I can't remember the exact command at the moment, but a fah3console -help should inform you about it, if necessary.

Edit: This page shows the status of the various servers, if you're interested.

 

[alnitak]

All looks lost for that WU, it won't transmit at all. Never mind though, the bits for my new PC should arrive soon, and an Athlon XP 2700 running 24/7 should soon make up the lost ground!