I keep getting this error message. It has been going on all day. "8/20/2005 8:39:01 PM Error on file upload: [03oc03aa.9124.306.536080.194_3_0] locked by file_upload_handler PID=8165" Anyone have any idea how to fix this? I am using CC 4.45.

Sounds like a local problem within Windows (Process ID seems to be locked)? Have you tried exiting Boinc completely, then restarting it? Else just wait it out. People have had this error on Seti proper, but the units would eventually be uploaded on their own.

---

yea I stopped and restarted the service, still no luck... :(

Sorry, can't be of much help any further. I did log the error into the Boinc Wiki. Let's see if someone picks up on it and explains what it means. :)

---

I had a similar err on normal seti but different PID number as shown below:

16/08/2005 01:14:58|SETI@home|Started upload of 17au03ab.11711.13458.286082.232_1_0
16/08/2005 01:15:01|SETI@home|Error on file upload: [17au03ab.11711.13458.286082.232_1_0] locked by file_upload_handler PID=19521
16/08/2005 01:15:01|SETI@home|Temporarily failed upload of 17au03ab.11711.13458.286082.232_1_0: transient upload error
16/08/2005 01:15:01|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 17au03ab.11711.13458.286082.232_1_0
16/08/2005 01:16:01|SETI@home|Started upload of 17au03ab.11711.13458.286082.232_1_0
16/08/2005 01:16:15|SETI@home|Finished upload of 17au03ab.11711.13458.286082.232_1_0

I sent the error logs to Paul D. Buck

Andy

I got an answer in from Paul D. Buck on this:

The PID is the server-side process ID of the handler that held the lock. This is an issue where the file should have been unlocked but some process had the file open for reading. MY BEST GUESS is that there was an interruption, the file was locked by the one process on the system, that timed out but the lock was not released and when the second attempt was tried it failed because the other process held the write lock. Which be the THIRD attempt, worked as the FIRST upload handler let go the lock. But I am missing the earlier part of the log so I cannot say for sure.

At any rate, it is all a server side problem with communication problems thrown in to create the problem.

So anyone out there with a better log can send it to Paul at p.d.buck@comcast.net

---

try a reboot??

couldn't hurt

try a reboot??
couldn't hurt

You mean a server reboot? ;-)
As I understand Paul D. Buck's explanation, a client reboot could't help.
Peter

I'm getting this error.

8/23/2005 11:27:34 AM|SETI@home Beta Test|CreateProcess() failed - The system cannot find the file specified. (0x2)
8/23/2005 11:27:35 AM|SETI@home Beta Test|CreateProcess() failed - The system cannot find the file specified. (0x2)
8/23/2005 11:27:36 AM|SETI@home Beta Test|CreateProcess() failed - The system cannot find the file specified. (0x2)
8/23/2005 11:27:36 AM|SETI@home Beta Test|CreateProcess() failed - The system cannot find the file specified. (0x2)
8/23/2005 11:27:37 AM|SETI@home Beta Test|CreateProcess() failed - The system cannot find the file specified. (0x2)
8/23/2005 11:27:38 AM|SETI@home Beta Test|Unrecoverable error for result 03oc03aa.9124.497.261062.17_3 (CreateProcess() failed - The system cannot find the file specified. (0x2))

Any idea what happend? :-( I just went in, and deleted the optimized file and put the standard version in. Dunno if that will cure it, will have to wait until the servers are all back up now. I'll let you know.

Jeremy

---

Any idea what happend? :-( I just went in, and deleted the optimized file and put the standard version in.

Jeremy, you were trying to remove the optimized application? To do that, you'll need to shut down BOINC, delete the app_info.xml file from the Beta project folder, restart BOINC and let it connect to the servers to d/l the standard application and get new WU's for it. Since the servers are down right now, that could be the source of this error message.

---

Any idea what happend? :-( I just went in, and deleted the optimized file and put the standard version in.

Jeremy, you were trying to remove the optimized application? To do that, you'll need to shut down BOINC, delete the app_info.xml file from the Beta project folder, restart BOINC and let it connect to the servers to d/l the standard application and get new WU's for it. Since the servers are down right now, that could be the source of this error message.

Hi David,

I did all of the above after I got the error. I shut down BOINC, removed the file, and restarted it, but since the servers are down, nothing I can do for now. Ill post more when things come up. Thanks for your help.

Jeremy

One new entry in the Wiki, with full explanations. ;)

(With thanks to sleepless Paul)

---

Wow, thats great. Hopefully it don't happen again. I'll probably detach the project, re-attach when SETI comes back up, and try again. If it doesn't do it then I'm not sure what else to do. I thought i got the right optimized client, and I followed the installation, so who knows. I'll double check client, and try installing it, and will have to wait and see. Thanks for all the help guys.

Jeremy

---