Error message

[awsum140]

I've been getting this

17:47:45:WU01:FS00:Connecting to web.stanford.edu:80
17:47:45:ERROR:WU01:FS00:Exception: Failed to access core package.
17:54:36:WU01:FS00ownloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah

on my laptop since last night. I am assuming, and we all know what that can do, that there is a problem at Stanford. I did re-install the client and the same message is coming up. My other machine, with a CUDA GPU also had problems getting a work unit yesterday. I am also assuming they are related problems.

Any advice is welcome.

 

[retired1]

Found a possible solution here: https://foldingforum.org/viewtopic.php?f=72&t=23255

 

[awsum140]

Thanks! That talks about a GPU sot, but it may also apply to a normal CPU slot. I'll give it a shot.

Well, that didn't work. The same error message is still coming up.

 

[awsum140]

A further update - According to another thread about specific server problems there is, indeed, a problem with assigning work units properly from FAH/Stanford.

 

[irwink]

I had the same problem on one of my machines. 2 cpu slots. You can either pause the client, delete the work folders for the affected slots, quit and restart the client. Or you can just delete the cpu slots themselves and then recreate them from within the client.

 

[awsum140]

Thanks for the advice!

I tried the delete trick and it didn't work, apparently. I actually unloaded the client, deleted the directory and restarted the client with no success. What did the trick was the delete with a reboot. I am guessing, but something seems to remain cached, somewhere, even when the client is stopped and unloaded. "Normalcy" has returned.

 

[irwink]

Thanks for the advice!

I tried the delete trick and it didn't work, apparently. I actually unloaded the client, deleted the directory and restarted the client with no success. What did the trick was the delete with a reboot. I am guessing, but something seems to remain cached, somewhere, even when the client is stopped and unloaded. "Normalcy" has returned.

I do seem to recall at least one other person in the folding forum thread that had to actually reboot to get back on track. Different versions of Windows, different configurations - I don't know. At least you're going again.