Error code -100 to -110 explained
BOINC_SUCCESS 0 - Not an error, but a good thing. Success. Everything is working as it should. Rejoice.
ERR_SELECT -100 - This error code is no longer used in any of the present versions of BOINC.
ERR_MALLOC -101 - There is a problem with the memory allocation. If insufficient memory is found to store BOINC and the project's science application plus work unit in, you'll get an error -101.
Solution: Free up memory or add more memory to your computer. See RAM Requirements for how much RAM you need free.
ERR_READ -102 - BOINC has a problem reading from the drive. Maybe you do not have rights to read from the BOINC directory.
Solution: Make sure you have rights in your operating system to read from the drive. Check your drive for consistency, in Windows using chkdsk.
ERR_WRITE -103 - BOINC has a problem writing to the disk. Maybe you do not have rights to write to the BOINC directory.
Solution: Make sure you have rights in your operating system to write to the drive. Check your drive for consistency, in Windows using chkdsk.
ERR_FREAD -104 - BOINC can't read the memory. The memory segment BOINC is trying to read from may be in use by another application.
Solution: Exit BOINC completely and restart it.
ERR_FWRITE -105 - BOINC can't write to memory. The memory segment BOINC is trying to write to may be in use by another application.
Solution: Exit BOINC completely and restart it.
ERR_IO -106
1. BOINC failed to read from or write to the disk drive. You may have problems with your hard drive.
Solution: Check your disk drive with drive tools or chkdsk.
2. BOINC failed to send or receive data through the network. The project servers may be down, a router between you and the project servers may be down.
Solution: Let BOINC retry to upload/download work by itself. No need to hamper with it.
ERR_CONNECT -107
BOINC couldn't connect to:
- a project's server.
- an account manager's server.
- Boinc Manager cannot connect to BOINC. (Yes, a localhost error is also an error -107)
ERR_FOPEN -108
1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC / BOINC Data directory and its sub-directories. Then BOINC can't find where it is running from.
Solution: Do not hide your BOINC / BOINC Data directory.
2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file.
Solution: Exit BOINC completely and restart it.
3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it).
Solution: Restart your computer.
4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC or BOINC Data directory and sub-directories. The directories their read-only attributes are set.
Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC /BOINC Data directory and subdirectories.
ERR_RENAME -109
1. BOINC has a problem renaming files. One such file that gets renamed is the client_state.xml file. If for some reason it's set to Read-Only, you will get this error.
Solution: Don't make any files Read-Only.
2. See Error 3 and its solution at ERR_FOPEN above.
ERR_UNLINK -110
This is (probably) a problem removing a file. In Unix you "unlink" the file because there could be several links (names) for the same file. When all links are gone the file is actually removed.
| Original writer | Original FAQ | Date |
|---|---|---|
| Jorden | 71 | 14-02-2008 |
