Message from server: Data collect version 3 _("is not available for your type of computer").

This is getting old now. Happening almost every day at 0000GMT. What is not getting reset on a re-boot?

8 Oct 2013 23:35:00 UTC - Results ready to send 2,445
8 Oct 2013 23:44:59 UTC - Results ready to send 2,097
8 Oct 2013 23:57:00 UTC - Results ready to send 1,655

9 Oct 2013 00:14:33 UTC - Results ready to send 1,409
9 Oct 2013 00:27:32 UTC - Results ready to send 1,403
9 Oct 2013 00:39:57 UTC - Results ready to send 1,399
9 Oct 2013 00:49:58 UTC - Results ready to send 1,397

9 Oct 2013 1:02:30 UTC - Results ready to send 1,396
9 Oct 2013 1:21:21 UTC - Results ready to send 1,392
9 Oct 2013 1:43:56 UTC - Results ready to send 1,392
9 Oct 2013 1:54:04 UTC - Results ready to send 1,386
9 Oct 2013 2:06:01 UTC - Results ready to send 1,383
9 Oct 2013 2:59:28 UTC - Results ready to send 1,624

9 Oct 2013 3:38:34 UTC - Results ready to send 4,735
9 Oct 2013 3:51:17 UTC - Results ready to send 6,728
9 Oct 2013 4:09:56 UTC - Results ready to send 9,158
9 Oct 2013 4:23:21 UTC - Results ready to send 10,887
9 Oct 2013 4:34:11 UTC - Results ready to send 12,188

The problem with decline of v4 WUs (no work generation) starts before 00:00 UTC (maybe (but I have no evidence) ~23:00 UTC = probably 00:00 in France summer time) and end shortly before 3:00 UTC (total 4 hours)
The no-work-generation start time may even be as early as 21:00 UTC

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Message from server: Data collect version 3 _("is not available for your type of computer").

This is getting old now. Happening almost every day at 0000GMT. What is not getting reset on a re-boot?

This just happened to me as well. I had been getting tasks up until 12 hrs ago.

Message from server: Data collect version 3 _("is not available for your type of computer").

This is getting old now. Happening almost every day at 0000GMT. What is not getting reset on a re-boot?

This just happened to me as well. I had been getting tasks up until 12 hrs ago.

Update: reset didn't work.

However, removing and then re-adding did work!

removing and then re-adding did work!

I tried your idea. No joy.

The strange thing is...
59668 WUProp@Home 10/10/2013 4:43:27 PM Starting task wu_v4_1380380781_516355_0 using data_collect_v4 version 408 (nci) in slot 0

---

The problem persisted for much longer than usual last night on both of my 32 bit Windows systems (times are UTC+1).

C2Q Q6600 XP, no WUProp work for 2:02:03:

11/10/2013 02:10:28 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 02:23:45 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 02:48:26 | WUProp@Home | Project has no tasks available
11/10/2013 03:12:24 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 04:12:31 | WUProp@Home | Scheduler request completed: got 1 new tasks

C2D T7300 Vista, no WUProp work for 1:48:24:

11/10/2013 01:29:50 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 01:43:03 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 01:54:17 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 02:18:07 | WUProp@Home | Message from server: Data collect version 3 is not available for your type of computer.
11/10/2013 03:18:14 | WUProp@Home | Scheduler request completed: got 1 new tasks

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

11 Oct 2013 20:50:49 UTC - Results ready to send 14,214
11 Oct 2013 21:03:03 UTC - Results ready to send 14,248
11 Oct 2013 21:14:19 UTC - Results ready to send 14,202
11 Oct 2013 21:28:52 UTC - Results ready to send 14,200
11 Oct 2013 21:55:43 UTC - Results ready to send 14,195
11 Oct 2013 22:11:52 UTC - Results ready to send 14,186
11 Oct 2013 22:30:19 UTC - Results ready to send 14,185
11 Oct 2013 22:52:30 UTC - Results ready to send 14,363 - Workunits waiting for validation 25
11 Oct 2013 23:11:32 UTC - Results ready to send 14,217 - Workunits waiting for validation 7

11 Oct 2013 23:38:55 UTC - Results ready to send 13,858 - Workunits waiting for validation 41	- Transitioner backlog (hours)	0
11 Oct 2013 23:53:41 UTC - Results ready to send 13,293 - Workunits waiting for validation 11	- Transitioner backlog (hours)	1

12 Oct 2013 00:57:34 UTC - Results ready to send 12,206 - Workunits waiting for validation 0	- Transitioner backlog (hours)	2
12 Oct 2013 01:15:22 UTC - Results ready to send 12,315 - Workunits waiting for validation 14	- Transitioner backlog (hours)	2
12 Oct 2013 01:25:24 UTC - Results ready to send 12,387 - Workunits waiting for validation 16	- Transitioner backlog (hours)	2
12 Oct 2013 01:41:53 UTC - Results ready to send 12,579 - Workunits waiting for validation 578	- Transitioner backlog (hours)	2
12 Oct 2013 02:16:26 UTC - Results ready to send 12,890 - Workunits waiting for validation 1,183 -Transitioner backlog (hours)	1
12 Oct 2013 02:34:03 UTC - Results ready to send 13,072 - Workunits waiting for validation 998	- Transitioner backlog (hours)	1
12 Oct 2013 02:51:20 UTC - Results ready to send 13,322 - Workunits waiting for validation 661	- Transitioner backlog (hours)	1
12 Oct 2013 03:12:54 UTC - Results ready to send 13,831 - Workunits waiting for validation 110	- Transitioner backlog (hours)	2
12 Oct 2013 03:44:59 UTC - Results ready to send 16,971 - Workunits waiting for validation 3	- Transitioner backlog (hours)	2

It looks like there is a change in the situation - now the 'Results ready to send' do not drop so much as was 3 days ago.
Anyone have a guess why there is increase in 'Workunits waiting for validation' and 'Transitioner backlog (hours)'?

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

removing and then re-adding did work!

Something worked, because I'm not getting the Server notices any more.

---