Hi,
when restarting my laptop after hibernation I get the following:

Restart laptop from hibernation
6/25/2007 11:24:08 AM|SETI@home|Sending scheduler request: To report completed tasks
6/25/2007 11:24:08 AM|SETI@home|Reporting 2 tasks
6/25/2007 11:24:09 AM|SETI@home|Task 14ap99aa.4157.16578.636060.3.132_0 exited with zero status but no 'finished' file
6/25/2007 11:24:09 AM|SETI@home|If this happens repeatedly you may need to reset the project.
6/25/2007 11:24:09 AM|SETI@home|Restarting task 14ap99aa.4157.16578.636060.3.132_0 using setiathome_enhanced version 515
6/25/2007 11:24:12 AM||Project communication failed: attempting access to reference site
6/25/2007 11:24:13 AM||Access to reference site failed - check network connection or proxy configuration.
6/25/2007 11:24:15 AM|SETI@home|Scheduler request failed: couldn't resolve host name
6/25/2007 11:24:15 AM|SETI@home|Sending scheduler request: To report completed tasks
6/25/2007 11:24:15 AM|SETI@home|Reporting 2 tasks
6/25/2007 11:24:26 AM|SETI@home|Scheduler request failed: HTTP file not found
6/25/2007 11:24:26 AM|SETI@home|Deferring communication for 1 min 0 sec
6/25/2007 11:24:26 AM|SETI@home|Reason: scheduler request failed
6/25/2007 11:25:31 AM|SETI@home|Sending scheduler request: To report completed tasks
6/25/2007 11:25:31 AM|SETI@home|Reporting 2 tasks
6/25/2007 11:25:53 AM|SETI@home|Scheduler RPC succeeded [server version 509]
6/25/2007 11:25:53 AM|SETI@home|Deferring communication for 11 sec
6/25/2007 11:25:53 AM|SETI@home|Reason: requested by project
Logon
6/26/2007 11:55:42 AM|SETI@home|Task 14ap99aa.4157.16578.636060.3.132_0 exited with zero status but no 'finished' file
6/26/2007 11:55:44 AM|SETI@home|If this happens repeatedly you may need to reset the project.
6/26/2007 11:56:00 AM|SETI@home|Restarting task 14ap99aa.4157.16578.636060.3.132_0 using setiathome_enhanced version 515

Setiathome works fine but it seems to me this is still a small flaw.
Greeting, Guy.

---

Yes, this is known. The error message is more informational than a true error. The WU will probably complete with no problem. By going into hibernation your system just forces the programs to go on hold but doesn't shut them down. This message is generated because the Boinc client is prevented from communicating with the project application for more than 30 seconds as it is expected to be able to do.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Yes, this is known. The error message is more informational than a true error. The WU will probably complete with no problem. By going into hibernation your system just forces the programs to go on hold but doesn't shut them down. This message is generated because the Boinc client is prevented from communicating with the project application for more than 30 seconds as it is expected to be able to do.

Are you sure this is really the case? The reason I ask is that I get exactly the same set of messages on my desktop PC, and that doesn't go into Hibernate mode at all.

25/06/2007 07:26:16|SETI@home|Starting 19jl99ab.28690.30993.1034646.3.72_2
25/06/2007 07:26:16|SETI@home|Starting task 19jl99ab.28690.30993.1034646.3.72_2 using setiathome_enhanced version 515
25/06/2007 08:12:28|SETI@home|Task 19jl99ab.28690.30993.1034646.3.72_2 exited with zero status but no 'finished' file
25/06/2007 08:12:28|SETI@home|If this happens repeatedly you may need to reset the project.
25/06/2007 08:12:28|SETI@home|Restarting task 19jl99ab.28690.30993.1034646.3.72_2 using setiathome_enhanced version 515
25/06/2007 12:11:11|SETI@home|Task 19jl99ab.28690.30993.1034646.3.72_2 exited with zero status but no 'finished' file
25/06/2007 12:11:11|SETI@home|If this happens repeatedly you may need to reset the project.
25/06/2007 12:11:11|SETI@home|Restarting task 19jl99ab.28690.30993.1034646.3.72_2 using setiathome_enhanced version 515
25/06/2007 13:39:21|SETI@home|Sending scheduler request: To fetch work
25/06/2007 13:39:21|SETI@home|Requesting 46 seconds of new work
25/06/2007 13:39:26|SETI@home|Scheduler request failed: HTTP file not found
25/06/2007 13:39:26|SETI@home|Sending scheduler request: To fetch work
25/06/2007 13:39:26|SETI@home|Requesting 46 seconds of new work
25/06/2007 13:39:31|SETI@home|Scheduler RPC succeeded [server version 509]
25/06/2007 13:39:31|SETI@home|Deferring communication for 11 sec
25/06/2007 13:39:31|SETI@home|Reason: requested by project
25/06/2007 13:39:33|SETI@home|[file_xfer] Started download of file 21jl99aa.18613.19424.753390.3.44
25/06/2007 13:39:37|SETI@home|[file_xfer] Finished download of file 21jl99aa.18613.19424.753390.3.44
25/06/2007 13:39:37|SETI@home|[file_xfer] Throughput 137482 bytes/sec
25/06/2007 15:09:54|SETI@home|Task 19jl99ab.28690.30993.1034646.3.72_2 exited with zero status but no 'finished' file
25/06/2007 15:09:54|SETI@home|If this happens repeatedly you may need to reset the project.
25/06/2007 15:09:54|SETI@home|Restarting task 19jl99ab.28690.30993.1034646.3.72_2 using setiathome_enhanced version 515
25/06/2007 16:24:17|SETI@home|Computation for task 19jl99ab.28690.30993.1034646.3.72_2 finished
25/06/2007 16:24:17|SETI@home|Starting 21jl99aa.18613.19424.753390.3.44_2

---

Yes, this is known. The error message is more informational than a true error. The WU will probably complete with no problem. By going into hibernation your system just forces the programs to go on hold but doesn't shut them down. This message is generated because the Boinc client is prevented from communicating with the project application for more than 30 seconds as it is expected to be able to do.

Are you sure this is really the case? The reason I ask is that I get exactly the same set of messages on my desktop PC, and that doesn't go into Hibernate mode at all.

As Aurora said, this is more of an informational message and doesn't necessarily happen only on hibernation. The BOINC client can be prevented from communicating to the project application due to various reasons.

For example, I also have a desktop and occasionally running quickpar or some other memory intensive application results in the same message.

If it happens very often then it indicates a problem with the computer and you should check for other causes.

Here is a link to the BOINC Wiki with a detailed explanation of this message...

---