I have a Windows machine with Boinc installed as a service, because vast majority of time it is a headless machine. I remember reading somewhere, but can't remember where, that some Boinc or CPDN versions are bugy regarding service installation, yet still unfixed. My Boinc service-installation machine can crunch HadAM3P -EU and -ANZ just fine, but not -PNW or HadCM3-Short.

My other non-service installation machine can run everything.

The poor service-installation machine http://climateapps2.oerc.ox.ac.uk/cpdnboinc/results.php?hostid=1352425

That's correct.
The PNW & the "short" models still have the buggy api. This only applies to Windows + BOINC 7 + a service install.

Good to know that You know about it! Now the question is, when can we get it fixed? (Also: why no info on 'News & Announcements', "Service-install doesn't work with xxx, sorry, will fix it!")

The problem has been around for over a year. I thought it had been fixed, but apparently not. When? No idea.

A week ago I turned on the HadCM3 short downloads again for a bit. 9 downloaded and ran perfectly. Not running them now as there is plenty of work around and thought I'd leave them for the linux machines. In fact I'm now having very few errors on this PC, and the PNW models also completing without error so far. This PC has always been running as a service installation and I had surmised that the earlier short model problems with the service installations had been solved. I'm still running Boinc v7.0.36.

BTW, one of the threads on this is here HadCM3 short - errors galore

---

That's right. As I suggested in message 50491 (in the middle of the thread Martin linked), v7.0.36 is actually the last BOINC version which doesn't trigger this bug - there are download links in that message for anyone who wants to try it.

For simplicity in general discussion, it's easier to say "v6 works, v7 doesn't" with respect to this particular bug, but the dividing line is actually slightly offset from the major version number change.

I downgraded Boinc to 7.0.36 and now it�s working. Thanks!

Just wondering if there has been any progress on the BOINC as Service issue as I'm in the long winded process of rebuilding and updating my PC.

I will be running the latest Win10 Pro.

Is v7.6.22 likely to have addressed the issues Richard wrote in a different thread here 50837, but I quote the relevant bits below?

[quote]
Sorry, the news I have is not good.

1) v7.4.27 in service mode won't help - it will show the same error behaviour as the v7.2.xx range. The trouble is inherent to the CPDN application, which tries - and fails - to use a new feature which was introduced at v7.0.38, and which will be the standard mechanism in all new BOINC clients for the forseeable future. (The old mechanism, which was categorised as a 'critical' weakness, lasted for six years before being replaced. Read 'foreseeable' in the context of that timescale. [trac]#336[/trac])

2) The latest information I have - email dated 12 November (2014!) - indicates that the CPDN end of the problem has not yet been addressed, and indeed will apply additionally to the new applications being requested by the researchers, and which are being tried out at the CPDN Beta site.

---

I don't remember running any "short" models for a long time.

The project has mostly moved on to 2 new model types:
WAH2 (Weather At Home 2) (wah2)
and
WAH2 Region Independent (Weather At Home 2) (wah2_ri)

I also don't know if these are affected by service/no-service, but I suspect not.
Win 10 on the other hand, is not good news, with it's unannounced reboots. :(