I'm hoping someone can give me a few ideas how to resolve the following. Installed 4.25 on a Windows 2000 server box attached to the S@H project only. It all seemed fine and downloaded the .exe .pdb and it's first WU's, however when trying to start processing them I'm getting the following error repeatedly and the WU's fail listing computation error.

19/05/2005 08:31:26|SETI@home|resume_or_start(): unexpected process state 7
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|Unrecoverable error for result 03fe05ac.27320.1538.311076.188_2 (CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20))

Any idea's?

I'm hoping someone can give me a few ideas how to resolve the following. Installed 4.25 on a Windows 2000 server box attached to the S@H project only. It all seemed fine and downloaded the .exe .pdb and it's first WU's, however when trying to start processing them I'm getting the following error repeatedly and the WU's fail listing computation error.

19/05/2005 08:31:26|SETI@home|resume_or_start(): unexpected process state 7
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:26|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20)
19/05/2005 08:31:27|SETI@home|Unrecoverable error for result 03fe05ac.27320.1538.311076.188_2 (CreateProcess() failed - The process cannot access the file because it is being used by another process. (0x20))

Any idea's?

This may help, look Here:
http://boinc-doc.net/_phpMyFAQ/index.php?action=artikel&cat=291825&id=459&artlang=en

Paul D. Bucks' excellent BOINC documentation is here: http://boinc-doc.net/

---

Thanks for that, I had looked at that before and I should have added that I've restarted the server but it still happens.

As mentioned in that FAQ entry though, this must be one of those other times...
"Then again, there are all those other times we can recall …"

Thanks for that, I had looked at that before and I should have added that I've restarted the server but it still happens.

As mentioned in that FAQ entry though, this must be one of those other times...
"Then again, there are all those other times we can recall …"

In that case, you probably need to use Task Manager and see what processes are running (make sure you have 'show processes from all users' ticked). You're looking for any BOINC or SETI processes to see what might be accessing the file.

You say it is a server, is it possible that a workstation is running BOINC and using the same folder (shared)?

---

Windows also can "lock" and leave locked files. I get this all the time when I am doing some clean-up work with looking at files with a program, closing the program, deleting files in a directory and then when you try to delete the directory, Windows says the directory is in use by a program.

The only way to clear the lock is to reboot the machine. So, I am not saying that this is exactly what is going on here... but it is a similar type of problem.

---

Well I gave it a second reboot when I got chance and it's now crunching away :)