Hello folks,

In checking the Messages tab I found the following:

8/21/2007 4:46:30 PM|SETI@home|Restarting task 04mr07ab.7106.6616.10.4.58_1 using setiathome_enhanced version 527
8/22/2007 6:47:23 AM||Can't rename state file; The process cannot access the file because it is being used by another process. (0x20)
8/22/2007 6:47:23 AM||[error] Couldn't write state file: system rename
8/22/2007 6:48:23 AM|SETI@home|Task 04mr07ab.7106.6616.10.4.58_1 exited with zero status but no 'finished' file
8/22/2007 6:48:23 AM|SETI@home|If this happens repeatedly you may need to reset the project.
8/22/2007 6:48:23 AM|SETI@home|Restarting task 04mr07ab.7106.6616.10.4.58_1 using setiathome_enhanced version 527
8/22/2007 7:36:23 PM||Running CPU benchmarks
8/22/2007 7:36:24 PM||Suspending computation - running CPU benchmarks
8/22/2007 7:37:25 PM||Benchmark results:
8/22/2007 7:37:25 PM|| Number of CPUs: 1
8/22/2007 7:37:25 PM|| 1158 floating point MIPS (Whetstone) per CPU
8/22/2007 7:37:25 PM|| 2184 integer MIPS (Dhrystone) per CPU
8/22/2007 7:37:26 PM||Resuming computation
8/23/2007 4:00:29 PM||Can't rename state file; The process cannot access the file because it is being used by another process. (0x20)
8/23/2007 4:00:29 PM||[error] Couldn't write state file: system rename
8/23/2007 4:01:29 PM|SETI@home|Task 04mr07ab.7106.6616.10.4.58_1 exited with zero status but no 'finished' file

I am at a loss on what to do and would appreciate any suggestions. Thank you.

---

More disturbing is the message:

8/22/2007 6:47:23 AM||[error] Couldn't write state file: system rename

This is an indication that the person that BOINC is running under does not have write permissions to the BOINC install directory. The default install directory is c:\\program files\\BOINC, and the default permissions for a normal user prevents writing anywhere in the Program Files directory tree. This could also be causing the problem with the aborted tasks.

Potential fixes:

1) Install as a service with the service account having administrator priviledges.
2) Move the BOINC install directory away from the Program Files directory (c:\\BOINC works).
3) Grant everyone full access the the BOINC directory tree wherever it is.

Let us know which path you want to go down, and we will give you help getting there.

---

BOINC WIKI

Hi there,

I am the only one using the computer and have adminstrator privilges. Seti and Boinc are and always have been in C:\\Program files. Lets start with the easiest solution and go from there.

Thanks,

George

More disturbing is the message:

8/22/2007 6:47:23 AM||[error] Couldn't write state file: system rename

This is an indication that the person that BOINC is running under does not have write permissions to the BOINC install directory. The default install directory is c:\\program files\\BOINC, and the default permissions for a normal user prevents writing anywhere in the Program Files directory tree. This could also be causing the problem with the aborted tasks.

Potential fixes:

1) Install as a service with the service account having administrator priviledges.
2) Move the BOINC install directory away from the Program Files directory (c:\\BOINC works).
3) Grant everyone full access the the BOINC directory tree wherever it is.

Let us know which path you want to go down, and we will give you help getting there.

---

Simplest.

Stop BOINC.
Move the entire contents of c:\\program files\\BOINC to c:\\BOINC
Reinstall with the same or a newer version into the new place.
Start BOINC.

---

BOINC WIKI

Thanks John,

Folder moved and BOINC is running again. I will let you know if the error message persists. Thanks again!

George

Simplest.

Stop BOINC.
Move the entire contents of c:\\program files\\BOINC to c:\\BOINC
Reinstall with the same or a newer version into the new place.
Start BOINC.

---

Thanks John,

Folder moved and BOINC is running again. I will let you know if the error message persists. Thanks again!

George

Simplest.

Stop BOINC.
Move the entire contents of c:\\program files\\BOINC to c:\\BOINC
Reinstall with the same or a newer version into the new place.
Start BOINC.

If you are still getting the exited with no finished file, you may be one of the unlucky ones. This has been fixed in 5.10.18 and later (Alpha releases so far).

---

BOINC WIKI