Hi,

I installed BOINC on my Windows 2003 server and everythiong worked fine.

After I made the server a Domain Controleer, the service stopped working, because of the Local Account Boinc_Master does no longer exists. After I created the Boinc_Master in my domain and configured the Service to use this user for logging, it worked fine again...

Now, when I try to start the Service, it starts, but stops after a few seconds with the message 'The BOINC Service terminated unexpectedly'...

During a re-install the installer stop, because needed account cannot be created (but they already exist)..

I just read that BOINC is not supported on DC's, so normally I would not ask, but it worked and now I'm wondering why it stopped working...

Any suggestions?

Thanks
Oliver

Can you please post the whole event ID about "The BOINC Service terminated unexpectedly" ?

It's possible that the password on the service account is no longer correctly read. You can try to change it.

Passwords
Q. Can I change the password on the boinc_master and boinc_project accounts?
A. Yes you can.
You will need to need to go to the service control manager and update the password to start the service (boinc_master). (BOINC->Properties->Logon)
Next you need to use a base64 encoder to rehash the password and fill this in in the client_auth.xml file in your BOINC data directory. You can use a base64 encoder online, such as this one.

Do know that the passwords on the accounts are set to never expire.

The installer checks whether or not it's installing on a DC, which is why it gives that error. If you were to 'install' with the administrative switch "boinc_installer_name.exe /a", it would unpack without problems.

---

If you were to 'install' with the administrative switch "boinc_installer_name.exe /a", it would unpack without problems.

Be careful when doing that on a host where BOINC is already running.

Even in 'admin' mode, the installer sets up INSTALLDIR and DATADIR paths pointing to the network unpack directory, as I reported in trac ticket [trac]#847[/trac] - I've just tested v6.13.12, and it's still doing it.

If you need to unpack, it's best to do it using a BOINC-free workstation on the network.

[quote]Can you please post the whole event ID about "The BOINC Service terminated unexpectedly" ?

It's possible that the password on the service account is no longer correctly read. You can try to change it.
[quote]

I changed the login name/password, but it still does not work.

Here the complete text of two of the given events:


In Application-Event:

Type: Information
User: N/A
Source: BOINC
Category: NONE
Event ID: 1

The description for Event ID ( 1 ) in Source ( BOINC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: BOINC is initializing...
; .

---
In System-event:
Type: Error
User: N/A
Source: Service Control Manager
Category: NONE
Event ID: 7000


The BOINC service failed to start due to the following error:
The system cannot find the file specified.

----

After I tried to re-install BOINC, now I getthe following message in System-event:
Type: Error
User: N/A
Source: Service Control Manager
Category: NONE
Event ID: 7000


The BOINC service failed to start due to the following error:
The system cannot find the file specified.
----

It looks, that the re-install deleted some files from my Boinc-directory....

Is it an idea to uninstall BOINC and install it again, using the commandline swith?

Thanks
Oliver

I changed the login name/password, but it still does not work.

You can't just change the login name or password. The BOINC service will run only under the boinc_master and boinc_projects accounts (where boinc_master runs BOINC and boinc_projects run the science applications).

Changing the password on the boinc_master account, without rehashing it at base64, will also not work. It needs that level of security. And even when you rehash it to base64, it may not work.

As for the administrative installation, you will need to uninstall your present BOINC before that. That should still be possible.

---

I changed the login name/password, but it still does not work.

You can't just change the login name or password. The BOINC service will run only under the boinc_master and boinc_projects accounts (where boinc_master runs BOINC and boinc_projects run the science applications).

Changing the password on the boinc_master account, without rehashing it at base64, will also not work. It needs that level of security. And even when you rehash it to base64, it may not work.

OK, what I did earlier was:
- Create an account Boinc_Master in my domain
- I set the password
- I change the properties of my BOINC service, entered the Boinc_Master@Domain user with the corresponding password
- started the service

Even after rebooting the server it worked fine, until two days ago...

Dunno if this is still an issue, but there be prollems with that:

Domain controllers separate local user accounts from Domain accounts. BOINC is not designed to make the sandboxed accounts in Active Directory, but in the local user accounts. Domain Controllers do not have local accounts because they must run Active Directory in order to authenticate users logging on to the network. Ergo, BOINC v6, with its sandboxed accounts, cannot run on Domain Controllers.

On the client side, local user accounts and settings are ignored when the user logs on to the domain, therefore the sandboxed accounts are not seen when run in an Active Directory environment. Since BOINC is not authorized in Active Directory to make Domain accounts, or Domain Global Groups, or even Universal Groups, the sandboxed accounts can only be run when not logged on to the domain.

See: http://setiathome.berkeley.edu/forum_thread.php?id=53310&nowrap=true#888986