Yes, I noticed a work unit that was ready to report but had zero CPU time, so I "bit the bullet" and reset the project, losing over 30 completed WU's. But at least I can now download, upload, and report.

So, the lesson learned (at least with dial up) is to check your uploaded WU's and make sure there's some CPU time recorded. If not, and you can't report work, then I guess you should will have to reset the project. I don't think the Berkeley people have the time or resources to fix problems on individual accounts and I don't expect them to do that). Hopefully this problem has already been fixed anyway.

There have been some reports on other threads of similar problems. They had to 'Reset the project' and in some cases detach and re-attach to get things working again. If you do have to do this, you will of course loose all the current work of that computer but it may be your only choice.

Yes, I know that. I get a successful upload and then click the "projects" tab and then right click the seti@home project and choose "update" from the menu. This is where I can't get any further - I always get the "no scheduler responded" message on this computer.

Look, I know the procedure -- it works on my other two computers. I was hopng to get some ideas to try that weren't the ordanary Boinc procedures that one must follow to report uploaded work. I have over 6000 credits on this computer before the last major Boinc Seti problem and my other two computer have started downloading, uploading, and reporting. This particular computer didn't and I haven't made any changes to it.

> Well, as I mentioned, I can upload okay. The "report" process is what doesn't
> work. I have over 30 WU's that are "ready to report". I've tried staying
> on-line for a few hours, letting Boinc do it's ".. deferred for 1 minute ..."
> "deferred for 10 minutes ....", etc. I've also tried "banging" the server with
> manual updates which also doesn't work. That's the mystery. Why do uploads
> work but reporting doesn't?
>

In order for the wu's 'Ready to Report' to send you must connect to the scheduler. The upload directory is separate from the scheduler. I just did a manual update to check and everything is working for me. I had 4 wu's 'Ready to Report' and when it connected to the scheduler they were sent.

SETI@home - 2004-09-09 21:23:14 - Started upload of 26ap04ab.12624.3041.854828.13_2_0
SETI@home - 2004-09-09 21:23:18 - Finished upload of 26ap04ab.12624.3041.854828.13_2_0
SETI@home - 2004-09-09 21:23:18 - Throughput 21199 bytes/sec
SETI@home - 2004-09-09 21:42:50 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-09-09 21:42:52 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Well, as I mentioned, I can upload okay. The "report" process is what doesn't work. I have over 30 WU's that are "ready to report". I've tried staying on-line for a few hours, letting Boinc do it's ".. deferred for 1 minute ..." "deferred for 10 minutes ....", etc. I've also tried "banging" the server with manual updates which also doesn't work. That's the mystery. Why do uploads work but reporting doesn't?

SETI@home - 2004-09-09 12:50:52 - Starting result 05my04aa.14696.498.1022148.206_0 using setiathome version 4.03
SETI@home - 2004-09-09 12:50:52 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:50:52 - Backing off 1 minutes and 0 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 12:51:52 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:51:52 - Backing off 1 minutes and 0 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 12:52:52 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:52:52 - Backing off 1 minutes and 0 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 12:53:53 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:53:53 - Backing off 1 minutes and 0 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 12:54:53 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:54:53 - Backing off 1 minutes and 19 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 12:56:12 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 12:56:12 - Backing off 4 minutes and 10 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 13:00:22 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -107
SETI@home - 2004-09-09 13:00:22 - Backing off 3 minutes and 28 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0
SETI@home - 2004-09-09 13:03:50 - Couldn't start upload for http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler: error -153
SETI@home - 2004-09-09 13:03:50 - Backing off 29 minutes and 3 seconds on transfer of file 26ap04ab.12624.305.273560.225_0_0

the file upload handler is offline?

> I have one particular computer that downloads and uploads Work Units with no
> problems. But I can't seem to report uploaded Work Units.
>
> My other two computer use the same phone line (dial-up) with winXP SP2. I have
> the same anti virus scanners, run Spybot and Adaware. The problem PC has the
> same processor (AMD 1900) the one of the other PC's has.
>
> The only thing I can think of that might be different is the problem PC has a
> PCI modem (US Robotics 56K Fax - I have the latest drivers) and the other two
> use on-board (motherboard) modems.
>
> I'm guessing I'm encountering a timing problem(?) because reporting accesses a
> different server (than a work unit upload)?
>
> Anyone have any guesses or a similar problem?
>

I have my 8 computers networked together sharing one internet connection over dial up. One modem and all computers are able to connect. I just have to stagger the startup when first going online for lack of bandwidth.
Soap, Ballot, Jury, Ammo. - The four boxes of liberty.
</img>

My problem isn't uploading, it only occurs when trying to report finished work units. The uploads work but the reporting doesn't.

I can plug the phone line into one of my other computers and upload and then report without problems (of course the servers have to be up, as they appear to be now).

I have one computer that has been trying to report and to download more WU's for several hours. I was assuming that the scheculer at Berkley was down or busy. The Message Tab reports that "No schedulers responded." My other units all have enough work to last for a while and havn't been trying to report any completed work.

I have one particular computer that downloads and uploads Work Units with no problems. But I can't seem to report uploaded Work Units.

My other two computer use the same phone line (dial-up) with winXP SP2. I have the same anti virus scanners, run Spybot and Adaware. The problem PC has the same processor (AMD 1900) the one of the other PC's has.

The only thing I can think of that might be different is the problem PC has a PCI modem (US Robotics 56K Fax - I have the latest drivers) and the other two use on-board (motherboard) modems.

I'm guessing I'm encountering a timing problem(?) because reporting accesses a different server (than a work unit upload)?

Anyone have any guesses or a similar problem?