I wish Stanford would just take my &#^%ing WU's!!!!!

[KFB]

I'm sorry but this is really getting old. My sig system is cranking WUs out and then they won't send. I know my 28.8 upload sux donkey balls but c'mon. Figure out how to receive a completed WU Stanford.
[and I defended them in other threads, but I'm ticked off now.]

[Kendan]

What ver. of the client are you using? This problem was fixed by several members by upgrading to the beta 2.17.

[KFB]

ok then. i will switch to the beta 217 console client. thanks for the tip.

[muddocktor]

The 2.17 client isn't helping me. I got 2.17 console running on a couple of rigs and they are backed up with completed WU's that are getting server errors evidently. And with these quick WU's that are being sent out they are stacking up. I've had problems with server 111 and 117 and a couple of times with 90. If they can't get things straightened out soon I'm going to shut some Folding down on a few rigs until they can get it straightened out.:mad:

[Kendan]

Originally posted by muddocktor
The 2.17 client isn't helping me. I got 2.17 console running on a couple of rigs and they are backed up with completed WU's that are getting server errors evidently. And with these quick WU's that are being sent out they are stacking up. I've had problems with server 111 and 117 and a couple of times with 90. If they can't get things straightened out soon I'm going to shut some Folding down on a few rigs until they can get it straightened out.:mad:

I really don't know what could be causing the problem you could try deleting the core65 and or the queue. It could be a corupted WU causing the problem, Try just core65 first because when you delete the queue those WU's will be lost.

[S_Wilson]

My machines on broadband almost never have this issue, but my machines on dialup will do this sometimes. Ploaf has posted info about using send flags if you are using text version. If you are using the graphical client, this is what I use, here is what I have done to remedy the situation.

Quit the client then establish your connection. Restart your client, the first thing it will try to do is send completed work units. I have done this as many as 5 or 6 times in row before they send. This has helped to resolve my issues and I hope it works for others. Good luck and keep folding.

[res0r9lm]

The same thing happened to me last week. took 7 or 8 days to go through but when it did I still got credit. only one wu if it was more I would have been ****ed. I think it is their servers that are the problem. good luck

[KFB]

I wrote the following "send_WU.bat" batch file to attempt to send WUs 30 times in a row (I know there is a way to make it loop, but I forgot so I use this method):

for %%x IN (1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30) DO c:\folding\fah2console217.exe -send all

For Windowz console version users:
Just copy & paste the above text into Notepad and adjust the directory and exe filename to your settings. Name the file "whatever.bat" and run it. Make sure you don't have any line breaks in the file or it will puke out on ya. Should be good for any of y'all with dialup or similar WU-sending problems for whatever reasons.
PM me if you have issues or questions.

[AMDownz23]

So has that script solved your problem KFB?

[KFB]

I wouldn't say it has "solved" my problem (mainly b/c the "problem" isn't on the client side, IMHO) - but it has definitely helped. Most of the WUs eventually get sent out. But some WU's still won't send, even if I run the script several times in a row, which equals out to 60 - 90 attempts.
It is much better than doing it manually, as the script allows it to attempt to send unattended. You can modify the script to try however many times you want. I will try to find the code for making the .bat loop, as that would streamline the code. If and when I do, I will post it.

[hooziewhatsit]

Originally posted by Kentucky Fried Bird
I will try to find the code for making the .bat loop, as that would streamline the code. If and when I do, I will post it.

The only way I know to make a .bat file loop would be to make it call itself as soon as it was done. Although with this I'm not sure how you would make it stop....

good luck, and fold on!

[res0r9lm]

wasn't able to send in work or get work. 3 hours later I'm saying wtf is going on. IM'ed jetmech to see if it was just me or what and guess what it was me. all I did was restart my computer and everything was running perfect again.

[JetMech]

Originally posted by res0r9lm
wasn't able to send in work or get work. 3 hours later I'm saying wtf is going on. IM'ed jetmech to see if it was just me or what and guess what it was me. all I did was restart my computer and everything was running perfect again. Glad to see you worked it out. This Folding definitely keeps you on your toes.:beer: :burn:

[res0r9lm]

thanks again. didn't lose too many spots actually I'm at same spot just different people are ahead of me

[JetMech]

Originally posted by res0r9lm
thanks again. didn't lose too many spots actually I'm at same spot just different people are ahead of me You're in the middle of one heck of a battle for position. It's all very motivational and can only result in more WUs done. Fold till you see smoke, then replace cpu and keep folding:D

[KFB]

Looks like Stanford has worked out the server-side issues and WU's are now uploading smoothly. The 217 client even reports a running total of completed WUs.

[AMDownz23]

Is that right? I'll just have to run a client or two and check it out.

[AMDownz23]

Nope..One machine got one of those 10 framers from .114 It finished and got my usual couldn't send results..The other machine is doing a GNRA..It won't be done till Sunday so we'll see about .115 (I think). Brutal..As far as G@H goes (no I'm not trying to convert anyone!) I have done a BUNCH of uploads and downloads and not one problem..When their stats server gets restored Sunday we should be in a higher ranking position ;)

[muddocktor]

I've had a lot better luck with server 111 today but server 117 is still a piece of *****. I have 1 comp that has had a WU in it all afternoon for 117 and I had to baby sit another through around 15 tries before it went into 117.

[AMDownz23]

What I would like to know is if G@H servers work so smoothly why the heck not setup F@H servers the same way...It seems so stupid to me. Stupid coming from Stanford makes no sense by the way.

[JetMech]

s

I think they'll work it out. They have to be aware that our ability to produce work for them is directly proportional to the support we get from them. If an individual is folding for nothing then he must consider his loses (paying extra utilities for nothing) and take actions accordingly. I hope they straighten this out because recruitment is hard enough without this kind of pressure. We've got some seriously dedicated people busting they're humps here not only folding but doing everything in their power to ensure that the work is recieved in usable condition. Correction of these problems should be priority one at Stanford. Keep pressing guy's. We've seen some improvement this week. I'm hopeful that they realize that there is still a lot of work to do.

[AMDownz23]

I agree with all of what you are saying JM...I had already planned to test run f@h every couple of weeks or so to see where they were at.