Solution... click on http://www.worldcommunitygrid.org/forums/wcg/...=0&sort=1&rows=20 for past discussion of this [rare-ish and also client version related issue IIRC]

The WCG endorsement of v7 is now way^10 overdue.

One of my machines is now suffering from the same errors -
[error] Can't parse file info in scheduler reply: unexpected XML tag or syntax
[error] No close tag in scheduler reply

This started yesterday 15 July around 19:26 GMT immediately after receiving other messages -
Message from server: Server error: feeder not running
and
Message from server: Project is temporarily shut down for maintenance

The effect is that I can't download any further WUs. Current WUs are still processing, uploading and reporting (all Valid or PVal), but BOINC Manager still shows the completed and reported tasks as "Ready to report". Results Status also shows that I have downloaded a couple of Beta WUs but they don't show in BOINC Manager.

Adding some debug log flags results in this (times are GMT+1) -
16/07/2013 11:48:20 World Community Grid [unparsed_xml] SCHEDULER_REPLY::parse(): unrecognized <userid>nnnnn</userid>
16/07/2013 11:48:20 [unparsed_xml] APP::parse(): unrecognized: <non_cpu_intensive>0</non_cpu_intensive>
16/07/2013 11:48:20 [unparsed_xml] FILE_INFO::parse(): unrecognized: <gen

nnnnn is my Account Number, redacted just in case I should

I've rebooted - no change.
I've run the 6.10.58 installer in repair mode - no change.

The machine is a Core i5-750 (4 cores) running Windows 7 64-bit SP1.

Help! What do I try next?

Thanks, I'll let the running CEP2 WUs finish and then do that.

Edit, for completeness: Still waiting for 3 CEP2 WUs to finish, but in the meantime something changed - the "Ready to report" tasks cleared from the BOINC Manager list and a long list of other error messages appeared, e.g.
16/07/2013 14:09:01 [unparsed_xml] parse_account_file_venue(): unrecognized: <auto_opt_in>1</auto_opt_in>
Subsequently, all new tasks requests have produced this -
16/07/2013 15:35:56 World Community Grid [unparsed_xml] SCHEDULER_REPLY::parse(): unrecognized <userid>37497</userid>
16/07/2013 15:35:56 [unparsed_xml] APP::parse(): unrecognized: <non_cpu_intensive>0</non_cpu_intensive>
16/07/2013 15:35:56 [unparsed_xml] RESULT::parse(): unrecognized: <wu_name>BETA_FA
16/07/2013 15:35:56 World Community Grid [error] Can't parse task in scheduler reply: unexpected XML tag or syntax
16/07/2013 15:35:56 World Community Grid [error] No close tag in scheduler reply

Still have 2 Beta WUs in Results Status that aren't listed in BOINC Manager, so something horrible will probably happen to them when I detach . Oddly, the Sent Time advances every time there is a task request. Sorry to whoever is waiting for them to process.
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045255_ 0833_ 3-- In Progress
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045254_ 1341_ 3-- In Progress

Lots of safeties, in this case, all the bad got checked by the server as in "lets compare what you have with what we have listed you should have". This is when missing bits get resend and yes, then the 'send time gets updated, but the due date should not, unless they're very close to deadline... then something is added [but this is knowledge from when we were on heavily patched server version 601.

Smells like something 'cattivo' is evolving.

And the first Beta is Valid, the second resent one is running. It can't all be bad.
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045254_ 1341_ 3-- 703 Valid 16/07/13 15:40:35 16/07/13 16:29:11 0.78 21.5 / 21.1