• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SetiQueue error! Cruncher can't submit!

C

conjur

No Lifer
12:44pm: s@h_wrk Returning passing through request response
12:44pm: s@h_wrk Passthrough: Seti@home status: ErrorCode 0x00000064 100
12:44pm: s@h_wrk Passing through request send_result_get_user_stats
12:44pm: s@h_wrk Queued passthrough request
12:43pm: SetiQueue needs updated? (Current: 3.03.2.2b, SetiQ Server: 3.03.2.2a)
12:43pm: Revision 3.03.2.2b started



Uhh....help?

I have one of my dual XP1800+ rigs stuck at the moment. Not sure if others are affected as none are close, at this moment, to being ready to send a completed WU to the queue.

I've bounced both machines and no luck. Networking is fine on both, too.
 
Check out doomer post. Been happening to a lot of folks. Try restarting your q if that don't work wiz has had luck replacing the user_sah file.
 
Check out doomer post. Been happening to a lot of folks. Try restarting your q if that don't work wiz has had luck replacing the user_sah file.
Click to expand...
You MUST replace your user_info.sah file on any stalled clients. Just restarting the queue will not work. At least that's the way it was on my three stalled clients. I also cleared all of the waiting wu's from my setiqueue in case any more nasties were lurking around in there.
 
My main machine has apparently gotten ahold of one or two of these WU's. It is stuck on one. Odd thing it still continues to send WU's after the stuck one. I'll try clearing the SAH file.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top