I have been experiencing many failures with the current Python application on several servers. I have 2 out of 5 systems running the Python tasks successfully. The other 3 systems tasks fail with compute error in about 15 seconds. The Python VM's don't even show up in VBox so they are not getting that far.

What I can see from the system events log is 10016 errors from DCOM server. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{74AB5FFE-8726-4435-AA7E-876D705BCBA5}
and APPID
{EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
to the user DL360G8-02boinc_master SID (S-1-5-21-138663538-4015345470-751189161-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The two that are working run Windows server 2019 and 2022. Two of the ones that are failing run 2012 R2 and the other is running 2019. All of them have been updated with Boinc version 7.20.2 with the default VBox version 6.1.34.

I did have a different issue with Hyper-V running on one server so I removed that but still cant figure it out. I have already tried a number of things to fix this but cannot find a working combination or what is different between the ones that are working and not.

Deinstalled/reinstalled BOINC including VBox
Updated VBox to the more recent version 6.1.36
Deinstalled BOINC and VBox and installed as Administrator
Tried editing the CLSID and APPID permissions in the registry and the DCOM config

I gave up after that. It shouldn't be that complicated.

Here are links to a few of the failing stderr output files for reference. They are all the same.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247574
https://boinc.bakerlab.org/rosetta/result.php?resultid=1492248465
https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247745
https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247240

Any further thoughts would be appreciated.

Update -

I found the problem causing this with BOINC being installed as a Service Install. That makes it run under the boinc_master account which does not have the correct privileges.

The BOINC application needed to be installed without the service install box checked which allows it to run under the Administrator account.

I was able to deinstall the BOINC program and re-install it with the correct setting. So far it seems to be running the python tasks so I'm pretty sure it will work now.

I also found out that if you run too many python tasks it can fill up your disk. If you don't have a lot of disk space, you might need to limit how many tasks run with an app_config file.

Jeff