I constantly get the following error messages when trying to upload results. I am becoming more and more discouraged with the whole process. Guess I can always go back to Seti@Home Classic. Any chance there is a fix to this??

Thanks.

Bill Bryan

SETI@home - 2004-10-07 16:17:36 - Resuming computation for result 26ap04aa.7733.30466.486066.222_4 using setiathome version 4.05
--- - 2004-10-07 17:04:55 - May run out of work in 0.10 days; requesting more
SETI@home - 2004-10-07 17:04:55 - Requesting 6721 seconds of work
SETI@home - 2004-10-07 17:04:55 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
--- - 2004-10-07 17:05:14 - Can't resolve hostname setiboinc.ssl.berkeley.edu (host name not found)
SETI@home - 2004-10-07 17:05:14 - scheduler init_op_project to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -113
SETI@home - 2004-10-07 17:05:14 - init_op_project failed, error -113
SETI@home - 2004-10-07 19:07:45 - Computation for result 26ap04aa.7733.30466.486066.222 finished
SETI@home - 2004-10-07 19:07:46 - Starting result 14mr04aa.17223.3345.361092.210_3 using setiathome version 4.05
SETI@home - 2004-10-07 19:07:46 - Started upload of 26ap04aa.7733.30466.486066.222_4_0
SETI@home - 2004-10-07 19:07:55 - Error on file upload: file_upload_handler: no filename; nbytes 12886.000000
SETI@home - 2004-10-07 19:07:55 - Permanently failed upload of 26ap04aa.7733.30466.486066.222_4_0
SETI@home - 2004-10-07 19:07:55 - Giving up on upload of 26ap04aa.7733.30466.486066.222_4_0: server rejected file

Not an answer I know!!!, But... I too am experiencing this problem. Just to narrow it down a little,... For me this only occurs with Windows XP Pro. Not sure if I'm just lucky but, XP Home and 98SE seem to be working OK now.

im having the same problem n im running W2K server :-(

last WU got this
SETI@home - 2004-10-08 16:20:41 - Error on file upload: file_upload_handler: no filename; nbytes 12083.000000
SETI@home - 2004-10-08 16:20:41 - Permanently failed upload of 14mr04aa.17223.9746.928404.133_1_0
SETI@home - 2004-10-08 16:20:41 - Giving up on upload of 14mr04aa.17223.9746.928404.133_1_0: server rejected file

Im starting to get tired of this..... after all... *we* are trying to help with the projects but boinc just doesnt seem to be up to the task IMO

Steve

I don't think it has anything to do with the OS (I have win2k), rather a problem on their end, because everyone is seeing this. But until they get it fixed i'm running classic, there's no sense in processing in vain.

I am experiencing this also on my Win2K prof. machines. I hope somebody in Berkeley reads this board. The status pages still shows their opinion that everything is OK now. Well... it isn't really....

Im also recieving errors:

SETI@home - 2004-10-08 08:43:41 - Computation for result 26ap04aa.7733.24336.134656.44 finished
SETI@home - 2004-10-08 08:43:41 - Starting result 06my04ab.10554.11249.729828.242_5 using setiathome version 4.05
SETI@home - 2004-10-08 08:43:41 - Started upload of 26ap04aa.7733.24336.134656.44_4_0
SETI@home - 2004-10-08 08:43:48 - Error on file upload: file_upload_handler: no filename; nbytes 15624.000000
SETI@home - 2004-10-08 08:43:48 - Permanently failed upload of 26ap04aa.7733.24336.134656.44_4_0
SETI@home - 2004-10-08 08:43:48 - Giving up on upload of 26ap04aa.7733.24336.134656.44_4_0: server rejected file

Im currently crunching a S@H WU and if this one fails i think im going to detach from s@h till the problem is fixed. Hopefully i wont have to do that, but i cant have s@h eating my cpu cycles then rejecting the result :|.

Jamie

I’m still getting these errors on some of the results that I submit:

SETI@home - 2004-10-08 09:09:54 - Started upload of 4mr04aa.17223.8432.640888.146_2_0
SETI@home - 2004-10-08 09:09:59 - Error on file upload: file_upload_handler: no filename; nbytes 10734.000000
SETI@home - 2004-10-08 09:09:59 - Permanently failed upload of 14mr04aa.17223.8432.640888.146_2_0
SETI@home - 2004-10-08 09:09:59 - Giving up on upload of 14mr04aa.17223.8432.640888.146_2_0: server rejected file

Are there just bad batches of WU’s out there that need to work their way thru the system and be rejected like this? If there’s a problem with the WU’s, is there a process to filter them for the errors and repair them before distributing them for processing? Or is the problem with the SETI@Home application or the BOINC client? Inquiring minds want to know…