Host has not been reporting results to BAM for several months and was listed as eligible for delete. Attempts to sync host with BAM via boincmgr return "user not found or password wrong". This error does not occur on any other host (four other hosts reporting to BAM). Applied both options for remedies in closed thread "Can't attach a host to BAM" without success.

Suggested alternative steps?

Thanks.
Jon

If you have thrown away the acct* files (including acct_mgr_login.xml!) then the manager should ask you for your username password when you connect to BAM! If it doesn't, you didn't throw away acct_mgr_login.xml. If it does ask for username/password and you enter credential correctly it should attach.

Thank you very much for the assistance with this issue. I did remove all acct* files. The option to attach via an account manager was then presented by BOINC acctmgr but when I selected it and walked through the dialog, the connection to BAM! failed and the event log contained an error stating that the acct* files were missing.

I do not have access to the problem host at this time but will recreate the behavior tomorrow 17 October and post the exact error messages from both the dialog and event log. If required (per the posting rules), I can also post any information from the acct* file that will assist in debugging.

Thanks again.
Jon

I just finished re-executing the (1) throw away all the mgr* files (left them in the windows deleted folder); (2) invoking the boincmgr dialog to add an account manager; (3) selected BAM!. The following occurred with the associated event log messages...

After entering the appropriate account name/password, the dialog returned the message:

"You are now using this account manager" "Click Finish to close"

In the event log are the following messages:

Fetching configuration file from http://bam.boincstats.com/get_project_config.php
[error] Account manager info missing from config file


Thanks again for your assistance with this matter.
Jon

I ended up:

1. renaming my system (changed the system name at the Windows level).
2. predefining a new BAM account via the "prepare new host" dialog at the Host List option in BAM (setting the new account host name to the new name I created in Windows).
3. re-executing the BOINC manager "connect to an account manager" dialog.

BAM and the newly named host have been communicating successfully since then.

Jon