People who are having task requests rejected because their quota is exhausted may wish to set 'No New Tasks' until they read that the faulty tasks have been flushed, and these new tasks are running successfully.

BOINC rebuilds the quota quickly when tasks are returned successfully, but if you're restricted to one task per day, and that one turns out to be a faulty one, you're stuck for another 24 hours.

People who are having task requests rejected because their quota is exhausted may wish to set 'No New Tasks' until they read that the faulty tasks have been flushed, and these new tasks are running successfully.

BOINC rebuilds the quota quickly when tasks are returned successfully, but if you're restricted to one task per day, and that one turns out to be a faulty one, you're stuck for another 24 hours.

Nobody on this project is restricted to one task a day but they are restricted to 2 a day because of the way computers count. 0 = 1, 1 = 2, etc

My main host got its daily quota of long workunits reduced to 1 because it had too many failures (caused by this bad batch).
Luckily there are short runs (and one other long run), so my main host is not completely shut off of this project.
This is really annoying.

It's beyond annoying. I now have 6 hosts that won't get tasks because of these bad WUs. Two of the hosts not getting tasks are the fastest ones with 1060 GPUs. Irritating.

People who are having task requests rejected because their quota is exhausted may wish to set 'No New Tasks' until they read that the faulty tasks have been flushed, and these new tasks are running successfully.

BOINC rebuilds the quota quickly when tasks are returned successfully, but if you're restricted to one task per day, and that one turns out to be a faulty one, you're stuck for another 24 hours.

I have tried this, however, without success.
The only differnce to what it was before is that now the BOINC notice does no longer refer to the task limit per day, but simply says

21/03/2017 18:36:42 | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)

Why so?

Even worse is that all my linux host got coproc error which means bad batch crash drivers.So other project did fail to.

A restart is now done and might crash again if there still is task out.

for some reason, 2 of my PCs now received new tasks, one of them was a
PABLO_contact_goal_KIX_CMYB

and even this one failed after a few seconds.
Till now I thought that only PABLO_p53 tasks are affected.

Edit: Only now I realize that on others of my PCs, during the day, had same probleme with all kinds of different WUs, not only PABLO_93.

Can it be that all recent WUs, regardless of the type, were faulty?

It's ridiculous that these bad tasks weren't canceled. How many machines have been denied work because of this laziness on the admins part? I've personally received 137 of these bad WUs so far and now have 7 machines not accepting long WUs. Multiply this by how many users? This kind of thing can also happen at other projects but they cancel the the bad WUs when informed of the problem. Why not here?

And still, for hours, the junk keeps rolling out.

If we the volunteers who donate our GPUs and electrons to help in what we're to believe is real science, I would hope the people using our resources would maybe have a little better way of administering them.

They should eliminate the "daily quota" for this particular situation. and let us crunch!

Well these broken tasks will have to run their course.

That will be a long and frustrating process, as every host can have only one workunit per day, but right now 9 out of 10 workunits is a broken one (so the daily quota of the hosts won't rise for a while), and every workunit has to fail 7 times before it's cleared from the queue.
To speed this up, I've created dummy hosts with my inactive host, and I've "killed" about 100 of these broken workunits. I had to abort some working units, but these are the minority right now.

The situation here still unchanged.
One of my 4 hosts luckily got a "good" WU some time last night and is crunching it.
On all other hosts BOINC still tells me

22/03/2017 05:14:41 | GPUGRID | This computer has finished a daily quota of 1 tasks

What I don't understand is why all these broken WUs cannot be removed from the queue, and why GPUGRID cannot somehow reset this daily quota junk.

By now, my frustration has reached quite a level :-(

Relax everone, we are where we are,I'm sure the admins are as frustrated as ourselves and are working to correct the situation.

On the bright side short WU's jus got a boost in computation.

short WU's jus got a boost in computation.

what does it help if they cannot be downloaded?

what does it help if they cannot be downloaded?

They can be downloaded, actually.

They can be downloaded, actually.

NOT on my machines. There comes the same notice re "daily quota of 1 task" ... :-(

They can be downloaded, actually.

NOT on my machine. There comes the same notice re "daily quota of 1 task" ... :-(

The quota is applied per task type. You are likely to be suffering from a quota of one long task per day: if you allow short tasks in your preferences, it is possible (but rare) to get short tasks allocated - I have two machines running them at the moment, because of that.

Here are the log entries from one of the affected machines:

22/03/2017 09:51:04 | GPUGRID | This computer has finished a daily quota of 1 tasks
22/03/2017 10:13:27 | GPUGRID | Scheduler request completed: got 2 new tasks
22/03/2017 10:13:27 | GPUGRID | No tasks are available for the applications you have selected
22/03/2017 10:13:27 | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)
22/03/2017 10:13:27 | GPUGRID | Your preferences allow tasks from applications other than those selected

They can be downloaded, actually.

NOT on my machines. There comes the same notice re "daily quota of 1 task" ... :-(

In addition to Richards response you have Long WU's running on three out of four of your machines. What more exactly do you want?

What is shown in my log is unfortunately wrong.

There is a total of 2 tasks running now. One on the slow GTX750Ti which was obviously not affacted the same way as the faster machines.
And one, to my surprise, on the GTX970.

The log, erronously shows 2 tasks on the PC with the two GTX980Ti, however, no tasks are being crunched there.

Then there is another PC with a GTX750Ti, which still shows the "quota of 1 task per day" notice.

It would of course be great if I could finally run tasks on the two GTX980ti's

Further, the log shows that a

PABLO_contact_goal_KIX_CMYB-0-4-RND2705_5

was downloaded at 10:11 hrs UTC this morning, and also errored out after a few seconds.
Can these faulty WUs indeed not be eleminated from the queue?

You are likely to be suffering from a quota of one long task per day: if you allow short tasks in your preferences, it is possible (but rare) to get short tasks allocated

that's what BOINC is showing me:

22/03/2017 13:12:42 | GPUGRID | No tasks are available for Short runs (2-3 hours on fastest card)
22/03/2017 13:12:42 | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)
22/03/2017 13:12:42 | GPUGRID | This computer has finished a daily quota of 1 tasks

So I doubt that could get short runs.
(your assumption is correct: I should be suffering on a long runs quota only, since no short runs were selected when the "accident" happened).