Thanks for that info Falconet.

We are getting work in the test run, so the BOINC Server is clearly running.

The problem is with a misconfigured scheduler, which can be easily seen from this section of the sched_reply_www.worldcommunitygrid.org.xml file. That's the reply from BOINC server/scheduler, to a scheduler request from the BOINC client. It's not generated from within the BOINC client

Small part of the scheduler reply:

<scheduler_reply>
<scheduler_version>701</scheduler_version>
<dont_use_dcf/>
<master_url>https://master.worldcommunitygrid.org/</master_url>
<request_delay>121.200000</request_delay>
<message priority="low">Project has no tasks available</message>
<project_name>World Community Grid</project_name>

And that error emanates from here, which is where the client sends its request.:
https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi

Which replies with:

<scheduler_reply>
<scheduler_version>701</scheduler_version>
<master_url>https://master.worldcommunitygrid.org/</master_url>
<request_delay>121.200000</request_delay>
<message priority="low">Error in request message: xp.get_tag() failed </message>
<project_name>World Community Grid</project_name>
</scheduler_reply>

So, it's up to the project admins to fix it, and then the erroneous message in the client will go away.
As I understand it, all they need to do is replace https://master.worldcommunitygrid.org/ with
https://www.worldcommunitygrid.org/ in the scheduler, and the issue will be history.
Why they haven't done that already, is anyone's guess.

BOINC experts, correct me if I'm wrong.

I'm not a BOINC expert Cyclops, only a user with at least some insight into BOINC, and some logical thinking. I'm sure the team have contact with some BOINC experts. I know that Igor or Dylan have some contact with Laurence from CERN/LHC.

The instructions above, posted by entity, comes from this page:https://boinc.berkeley.edu/trac/wiki/MasterUrl
Might be easier for the admins to follow the instructions on that page.

This is a very complicated bit of BOINC, and is most certainly not 'one size fits all'.

1) I would never try to change a project url while that project is still in the process of making changes. You might make a mistake, or the project might make a mistake. Wait for the dust to settle.

2) It very much depends how you attach to a project. Different methods can have different results. The main ways are:

• Using the wizard in BOINC Manager
  
• Using the 'boinccmd' command line tool
  
• Using an Account Manager like BAM! or Science United.
  

I'll describe the BOINC Manager case in detail: we have to wait until that dust has cleared to reveal a fully working WCG, and then adapt the other cases to match the working result.

What you see in the BOINC Manager wizard is, indeed, driven by the 'all_projects_list.xml' file. That file is dynamic - changes are made all the time - and there is no single definitive version. Look at the most recent version in your local BOINC data folder, and check the datestamp. It should be updated automatically every 14 days, and hence be relatively recent. Some options defeat the automatic updating, so you need to work round those.

All_projects_list should contain two urls: one for the project's general public web site, and one for the specific purpose of attaching a BOINC client. Make sure you focus on the right one - plain <url>, not <web_url>.

The BOINC Manager wizard will use that url to send a request to 'get_project_config.php' for the project. That will return an xml file containing the definitive, active, master url for the project. Currently, WCG returns

<master_url> http://www.worldcommunitygrid.org/ </master_url>

(spaces added to defeat auto-formatting)

That may or may not be what Krembil intends to use in the future - time will tell. But I'd recommend using it for the time being.

If you use boinccmd to attach to the project, use the url in the code box above.

If you use an Account Manager to attach, you're in the hands of the AM's administrator. They may, or may not, be following Krembil's learning curve as closely as you are.