I have been getting the same exact thing on 3 different host PC's.

Same Problems and same thoughts :

--- - 2004-10-08 21:34:20 - Insufficient work; requesting more
--- - 2004-10-08 21:34:23 - Insufficient work; requesting more
SETI@home - 2004-10-08 21:34:23 - Requesting 6574 seconds of work
SETI@home - 2004-10-08 21:34:23 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-08 21:34:26 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-08 21:34:26 - No schedulers responded
SETI@home - 2004-10-08 21:34:26 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2004-10-08 21:34:39 - Started upload of 14mr04aa.17223.7666.729828.225_2_0
SETI@home - 2004-10-08 21:34:46 - Error on file upload: file_upload_handler: no filename; nbytes 19537.000000
SETI@home - 2004-10-08 21:34:46 - Permanently failed upload of 14mr04aa.17223.7666.729828.225_2_0
SETI@home - 2004-10-08 21:34:46 - Giving up on upload of 14mr04aa.17223.7666.729828.225_2_0: server rejected file
SETI@home - 2004-10-08 21:35:26 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-08 21:35:29 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-08 21:35:29 - No schedulers responded
SETI@home - 2004-10-08 21:35:29 - Deferring communication with project for 1 minutes and 0 seconds
--- - 2004-10-08 21:35:38 - Insufficient work; requesting more
SETI@home - 2004-10-08 21:35:38 - Requesting 6574 seconds of work
SETI@home - 2004-10-08 21:35:38 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-10-08 21:35:41 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-10-08 21:35:41 - No schedulers responded
SETI@home - 2004-10-08 21:35:41 - Deferring communication with project for 1 minutes and 0 seconds

same problem... this has happend to last 2 of my work units [last one shown here] .. Successfully uploaded on new client b4 so not firewall as some sugegsted...


2004-10-08 10:59:11 [SETI@home] Resuming computation for result 26ap04ab.3369.11424.115922.220_5 using setiathome version 4.05
2004-10-08 17:34:53 [SETI@home] Computation for result 26ap04ab.3369.11424.115922.220 finished
2004-10-08 17:34:53 [SETI@home] Starting result 14mr04aa.17223.8817.67314.224_2 using setiathome version 4.05
2004-10-08 17:34:54 [SETI@home] Started upload of 26ap04ab.3369.11424.115922.220_5_0
2004-10-08 17:34:58 [SETI@home] Permanently failed upload of 26ap04ab.3369.11424.115922.220_5_0
2004-10-08 17:34:58 [SETI@home] Error on file upload: file_upload_handler: no filename; nbytes 12680.000000
2004-10-08 17:34:58 [SETI@home] Giving up on upload of 26ap04ab.3369.11424.115922.220_5_0: server rejected file

Thanks 4 advice

Two WUs failed on upload.
Message: SETI@home - 2004-10-08 23:47:05 - Giving up on upload of ... server rejected file

Always problems with communication.
So I activated my old SETI, it works, and works, and works.
I try to work with BOINC Seti one or two hours later.

Same silly messages from BOINC
No filename? Could be. But a number of bytes is reported nevertheless. The number is reported as a real variable, should it have been an integer?
Anyway, why is BOINC deleting results whenever the upload handler is confused?

I too appear to be having a similar problem, and my firewall is set correctly. I am a little loathe to continue with Boinc/Seti if the WUs are heading into "twilight zone". Judging from the number of entries here, and the range of dates, I would sincerely hope someone at Seti is working on it?

SETI@home - 2004-10-09 02:51:39 - Permanently failed upload of 26ap04aa.7733.26562.373564.35_3_0
SETI@home - 2004-10-09 02:51:39 - Giving up on upload of 26ap04aa.7733.26562.373564.35_3_0: server rejected
SETI@home - 2004-10-09 12:34:09 - Result 26ap04aa.7733.26514.704834.229_3 exited with zero status but no 'finished' file
SETI@home - 2004-10-09 12:34:09 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-10-09 15:28:25 - Started upload of 05my04ab.18320.3008.378418.22_4_0
SETI@home - 2004-10-09 15:28:37 - Error on file upload: file_upload_handler: no filename; nbytes 21165.000000
SETI@home - 2004-10-09 15:28:37 - Permanently failed upload of 05my04ab.18320.3008.378418.22_4_0
SETI@home - 2004-10-09 15:28:37 - Giving up on upload of 05my04ab.18320.3008.378418.22_4_0: server rejected file

Two out of my five pc's are losing work. It is not a firewall issue, since they're all going through the same shared internet connection.

SETI@home - 2004-10-09 05:39:02 - Error on file upload: file_upload_handler: no filename; nbytes 9346.000000
SETI@home - 2004-10-09 05:39:02 - Error on file upload: file_upload_handler: no filename; nbytes 11373.000000
SETI@home - 2004-10-09 05:39:02 - Permanently failed upload of 14mr04aa.17223.3202.304816.127_0_0
SETI@home - 2004-10-09 05:39:02 - Giving up on upload of 14mr04aa.17223.3202.304816.127_0_0: server rejected file
SETI@home - 2004-10-09 05:39:02 - Permanently failed upload of 14mr04aa.17223.3202.304816.129_0_0
SETI@home - 2004-10-09 05:39:02 - Giving up on upload of 14mr04aa.17223.3202.304816.129_0_0: server rejected file
SETI@home - 2004-10-09 05:39:02 - Started upload of 14mr04aa.17223.3202.304816.113_2_0
SETI@home - 2004-10-09 05:39:08 - Error on file upload: file_upload_handler: no filename; nbytes 9349.000000
SETI@home - 2004-10-09 05:39:08 - Permanently failed upload of 14mr04aa.17223.3202.304816.113_2_0
SETI@home - 2004-10-09 05:39:08 - Giving up on upload of 14mr04aa.17223.3202.304816.113_2_0: server rejected file

That's so plausible, I can't believe it.

But there is no reaction from BOINC-Seti about this phenomen. It's sad.

Same deal:

SETI@home - 2004-10-09 16:38:30 - Started upload of 14mr04aa.17223.13361.928404.204_0_0
SETI@home - 2004-10-09 16:38:39 - Error on file upload: file_upload_handler: no filename; nbytes 12115.000000
SETI@home - 2004-10-09 16:38:39 - Permanently failed upload of 14mr04aa.17223.13361.928404.204_0_0
SETI@home - 2004-10-09 16:38:39 - Giving up on upload of 14mr04aa.17223.13361.928404.204_0_0: server rejected file

Is anyone working on this?

I have the same error. After resetting the project and restarting the pc it gave me this:

SETI@home - 2004-10-10 13:11:27 - Result 14mr04aa.17223.22737.761084.83_0 exited with zero status but no 'finished' file
SETI@home - 2004-10-10 13:11:27 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-10-10 13:11:27 - Restarting result 14mr04aa.17223.22737.761084.83_0 using setiathome version 4.05

The WU was not finished (43%), so why it gave me the error "exited with zero status but not finished file"?? I think it's a Boinc/seti core bug and not a server problem...

I am also having problems uploading.

It is also with work of the same date (14mr04).

Might there be a coincidence with that? Or am I just reading into it?
It would be nice to get this problem solved.

---

Hi Again,

I followed the link that was posted to see the status of the servers and sah_validate is not running, I wonder if this is the problem?

Again I see nothing from Seti themselves...

I was going to switch my PC's downtime to predator due to Seti's failure to fix this issue and predator weren't taking any registrations? On the off-chance the two issues are linked I sent the Planetary Society an email regarding this issue as they seem to be huge supporter of Boinc/Seti?

Heres hoping

---

> Again I see nothing from Seti themselves...


From the SETI@home home page:

October 9, 2004
A problem with file uploads has existed for the last few days. This problem causes file uploads to fail. We now understand the problem and are working on a fix - it will probably require upgrading your BOINC client. Please stay tuned.

---

I have been a user of boinc from right back in the boinc beta and this is the first time i have actualy detached from the s@h project. I know the berkeley crew are working on it and i will attach again as soon as a fix has been made. I work on these projects for the science so im not willing to let s@h eat up hours of my cpu when they can go to projects that are working like LHC and CPDN. I dont mean this in a harsh way towards the people at berkeley because they are trying to a big task where such a little error is causing mass problems. Just hopefully it wont be too long before this fix is released!

Jamie

---

This upload failing problem is also happening to me. It's intermittent, some wu's will upload fine, some will fail.

I am running v4.09 but the message that I get states that it is using v4.05 as you can see below.

--- - 2004-10-12 10:29:11 - Starting BOINC client version 4.09 for windows_intelx86
SETI@home - 2004-10-12 10:29:11 - Project prefs: using your defaults
SETI@home - 2004-10-12 10:29:11 - Host ID is 149944
--- - 2004-10-12 10:29:11 - General prefs: from SETI@home (last modified 2004-08-29 22:47:02)
--- - 2004-10-12 10:29:11 - General prefs: using your defaults
SETI@home - 2004-10-12 10:29:11 - Resuming computation for result 01mr04aa.18860.5792.90902.84_0 using setiathome version 4.05
SETI@home - 2004-10-12 10:37:15 - Computation for result 01mr04aa.18860.5792.90902.84 finished
SETI@home - 2004-10-12 10:37:15 - Starting result 01mr04aa.18860.7729.279820.224_2 using setiathome version 4.05
SETI@home - 2004-10-12 10:37:15 - Started upload of 01mr04aa.18860.5792.90902.84_0_0
SETI@home - 2004-10-12 10:37:21 - Error on file upload: file_upload_handler: no filename; nbytes 10964.000000
SETI@home - 2004-10-12 10:37:21 - Permanently failed upload of 01mr04aa.18860.5792.90902.84_0_0
SETI@home - 2004-10-12 10:37:21 - Giving up on upload of 01mr04aa.18860.5792.90902.84_0_0: server rejected file

I hope the team can fix this soon because it's no fun seeing wu's trashed.

LiveStrong,
J. Barry

---

> This upload failing problem is also happening to me. It's intermittent, some
> wu's will upload fine, some will fail.
>
> I am running v4.09 but the message that I get states that it is using v4.05 as
> you can see below.
>
> --- - 2004-10-12 10:29:11 - Starting BOINC client version 4.09 for
> windows_intelx86
> SETI@home - 2004-10-12 10:29:11 - Project prefs: using your defaults
> SETI@home - 2004-10-12 10:29:11 - Host ID is 149944
> --- - 2004-10-12 10:29:11 - General prefs: from SETI@home (last modified
> 2004-08-29 22:47:02)
> --- - 2004-10-12 10:29:11 - General prefs: using your defaults
> SETI@home - 2004-10-12 10:29:11 - Resuming computation for result
> 01mr04aa.18860.5792.90902.84_0 using setiathome version 4.05
> SETI@home - 2004-10-12 10:37:15 - Computation for result
> 01mr04aa.18860.5792.90902.84 finished
> SETI@home - 2004-10-12 10:37:15 - Starting result
> 01mr04aa.18860.7729.279820.224_2 using setiathome version 4.05
> SETI@home - 2004-10-12 10:37:15 - Started upload of
> 01mr04aa.18860.5792.90902.84_0_0
> SETI@home - 2004-10-12 10:37:21 - Error on file upload: file_upload_handler:
> no filename; nbytes 10964.000000
> SETI@home - 2004-10-12 10:37:21 - Permanently failed upload of
> 01mr04aa.18860.5792.90902.84_0_0
> SETI@home - 2004-10-12 10:37:21 - Giving up on upload of
> 01mr04aa.18860.5792.90902.84_0_0: server rejected file
>
> I hope the team can fix this soon because it's no fun seeing wu's trashed.
>
> LiveStrong,
> J. Barry
>I am having this same problem. I am a new user to Bonic, and was wondering if it was just my computer? Guess not...

---

This is the way I see it; The servers are obviously online since we are still able to download work units and the latest word is that it is the new BOINC client that is the problem.

I know how you feel about processing the work unit and then them not being uploaded and loosing the credit so here's a solution that you may be able to use.
If you have you general prefs set so that boinc doesn't connect without your permission then you can avoid the seti wu's uploading and go online in between if you know what I mean?
I can be a very confusing person sometimes so I hope you do understand my explanation on the uploads because I would love to see everyone get the credits they deserve

> This upload failing problem is also happening to me. It's intermittent, some
> wu's will upload fine, some will fail.
>
> I am running v4.09 but the message that I get states that it is using v4.05 as
> you can see below.
>
> --- - 2004-10-12 10:29:11 - Starting BOINC client version 4.09 for
> windows_intelx86
> SETI@home - 2004-10-12 10:29:11 - Project prefs: using your defaults
> SETI@home - 2004-10-12 10:29:11 - Host ID is 149944
> --- - 2004-10-12 10:29:11 - General prefs: from SETI@home (last modified
> 2004-08-29 22:47:02)
> --- - 2004-10-12 10:29:11 - General prefs: using your defaults
> SETI@home - 2004-10-12 10:29:11 - Resuming computation for result
> 01mr04aa.18860.5792.90902.84_0 using setiathome version 4.05
> SETI@home - 2004-10-12 10:37:15 - Computation for result
> 01mr04aa.18860.5792.90902.84 finished
> SETI@home - 2004-10-12 10:37:15 - Starting result
> 01mr04aa.18860.7729.279820.224_2 using setiathome version 4.05
> SETI@home - 2004-10-12 10:37:15 - Started upload of
> 01mr04aa.18860.5792.90902.84_0_0
> SETI@home - 2004-10-12 10:37:21 - Error on file upload: file_upload_handler:
> no filename; nbytes 10964.000000
> SETI@home - 2004-10-12 10:37:21 - Permanently failed upload of
> 01mr04aa.18860.5792.90902.84_0_0
> SETI@home - 2004-10-12 10:37:21 - Giving up on upload of
> 01mr04aa.18860.5792.90902.84_0_0: server rejected file
>
> I hope the team can fix this soon because it's no fun seeing wu's trashed.
>
> LiveStrong,
> J. Barry
>
4.09 is the BOINC version (now they want you to upgrade to 4.12), 4.05 is the SETI@home version, over which you have no control.

---

Also here (Romania). I have two wu on my laptop and two wu on my home pc "ready to report" but can't upload:

SETI@home - 2004-10-13 10:34:37 - Started upload of 14mr04aa.17223.28033.642322.131_0_0
SETI@home - 2004-10-13 10:34:46 - Error on file upload: file_upload_handler: no filename; nbytes 14446.000000
SETI@home - 2004-10-13 10:34:46 - Permanently failed upload of 14mr04aa.17223.28033.642322.131_0_0
SETI@home - 2004-10-13 10:34:46 - Giving up on upload of 14mr04aa.17223.28033.642322.131_0_0: server rejected file

---

Also here (Brazil) I have the same problem. Please BOINC team, any comments?
In additon, what kind of error is the "Error on file upload: file_upload_handler:no filename"?

> Also here (Romania). I have two wu on my laptop and two wu on my home pc
> "ready to report" but can't upload:
>
> SETI@home - 2004-10-13 10:34:37 - Started upload of
> 14mr04aa.17223.28033.642322.131_0_0
> SETI@home - 2004-10-13 10:34:46 - Error on file upload: file_upload_handler:
> no filename; nbytes 14446.000000
> SETI@home - 2004-10-13 10:34:46 - Permanently failed upload of
> 14mr04aa.17223.28033.642322.131_0_0
> SETI@home - 2004-10-13 10:34:46 - Giving up on upload of
> 14mr04aa.17223.28033.642322.131_0_0: server rejected file
>
>

---