Havbe you tried a manual project update? Press the topmost button in the projects tab.

Regards,
Martin

I did as suggested by martin64 and it works. Thank you!

Sekerob, could it be that for some days in september I moved my system date forward to 2014? However, after some days, I set back the actual date.

Yes, that's most certainly the cause... 375164:29:09 = 42.79 years the client would have waited before asking for work again. Once the counter starts it will keep running, even after the date was corrected back or forward.... A manual update resets those counters.

Putting in the wrong date can also result in causing distortions of the Statistics in the client (!)... but all is well now, so if you please edit the Opening Post title and insert [RESOLVED].

Maybe I'll revisited the FAQs on this and maybe the developers might want to consider some rule to periodically check if client date now and server date have come together again. It is btw the first line in the FAQ Index Error fixing chapter 4... "wrong system date?". I'll add a comment there to hit the update button as a workaround if this ''accidentally'' happens.

Happy Crunching

OK, so started a topic on this at the Developers mail list and am glad that action was taken... client 6.12 will have a date sanity check:

David 16 Dec 2010
8766 - client: if detect that system clock has been set backwards
8767 (either at startup or during execution)
8768 reset a number of "wait until X" variables;
8769 otherwise we might wait years to contact a project, restart a file xfer, etc.
8770 Notes:
8771 - there is no problem setting clocks forward; things just happen prematurely
8772 - some variables (e.g. task deadlines) are not reset,
8773 because it's not clear what to set them to

Hope it works as expected, but wont know until a new alpha build is released to test this in practice. Asked for a Notifier window to pop up, but see no comment on that, yet.

ciao ciao