Not able to get work

[IronBits]

4/5/2006 7:31:15 PM||Starting BOINC client version 5.2.13 for windows_intelx86
4/5/2006 7:31:15 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
4/5/2006 7:31:15 PM||Data directory: C:\dcprojects\BOINC
4/5/2006 7:31:15 PM||Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
4/5/2006 7:31:15 PM||Memory: 2.00 GB physical, 3.85 GB virtual
4/5/2006 7:31:15 PM||Disk: 465.76 GB total, 446.76 GB free
4/5/2006 7:31:15 PM|rosetta@home|Computer ID: 87485; location: home; project prefs: default
4/5/2006 7:31:15 PM|Leiden Classical|Computer ID: 1116; location: home; project prefs: default
4/5/2006 7:31:15 PM||General prefs: from Leiden Classical (last modified 2006-03-26 18:44:43)
4/5/2006 7:31:15 PM||General prefs: no separate prefs for home; using your defaults
4/5/2006 7:31:15 PM||Remote control allowed
4/5/2006 7:31:30 PM||request_reschedule_cpus: project op
4/5/2006 7:31:32 PM|rosetta@home|Sending scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi
4/5/2006 7:31:32 PM|rosetta@home|Reason: Requested by user
4/5/2006 7:31:32 PM|rosetta@home|Requesting 17280 seconds of new work
4/5/2006 7:31:37 PM|rosetta@home|Scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
4/5/2006 7:31:37 PM|rosetta@home|Message from server: Not sending work - last RPC too recent: 42 sec
:bang:

[Paladin*]

Not sending work - last RPC too recent: 62 sec
========

When your Manually Updating the Client/Project & your getting the (last RPC too recent message) just let it run out on it's own & you should get new work once it runs down & the Manager re-updates on it's own.

At least thats what works for me anyway ... It usually only takes 3-4 minutes for it to run down, at least on my PC's it takes that long ...