I am unable to get my machine to synch with BAM or connect at all. Happened quite suddenly and I am not sure if it is a by product of updating to 7.0.25.

The following is the error that appears in Boinc Event Log.

Any help would be greatly appreciated.

I have detached and attached to BAM and reinstalled Boinc to no avail.


4/25/2012 7:41:51 PM | BOINCstatsBAM! | Message from account manager: Opening and ending tag mismatch: global_preferences line 335 and venue. Opening and ending tag mismatch: working_global_preferences line 334 and global_preferences. Opening and ending tag mismatch: acct_mgr_request line 2 and working_global_preferences. Extra content at the end of the document.

First of all, read the Bug Submit Guidelines, especially #1 and #8.

There are several threads about this subject.

Without the XML files described in #8 there is no way to tell where the problem is. What I can tell you is that BAM! uses a proper XML parser and when it complains the XML is broken it probably is.

@KaptainKarl1:

While attaching a new host to WCG, I got the same exact problem.

If you are having WCG as one of your project(s) - it's WCG causing the problem via BAM.
Seems like WCG device prefs aren't well formed.

(Possible) Cause:
Create a new prefs @ WCG or change something using the Default profile.
Attach WCG to a new host thru BAM (host config, check to add project to host).
@Host, sync with BAM
BAM is telling the host to grab new global project specific preference from WCG.
But WCG's global preferences xml is ill formed
== problem

If you attempt to remove and re-attach to BAM, you'll keep having the same problem bcoz the trouble end is WCG.

How I resolve the issue:
1] Go to WCG, modify the default Device profile settings by ensuring I set a value for everything

2] @BAM, uncheck WCG for specific host (may not be required)

3] @Host, detach from BAM

4] @Host, suspend all computing, suspend networking (IMPORTANT).
Suspending networking ensures BOINC don't go fetching global_prefs.xml from WCG.

Exit BOINC.

5] @Host, in you BOINC-Data folder, delete these 3 files:
acct_mgr_request.xml (don't worry, it's auto-generated)
acct_mgr_reply.xml (don't worry, it's auto-generated)
global_prefs.xml (you must delete this, the is the source of the problem)

6] Run BOINC, although we suspended network - we can still attach to BAM. Do so.

You should be able to attach to BAM.

Add WCG to host = success.

If you are not having WCG as one of your project:
Check/ensure global_prefs.xml aren't downloaded from any specific project where you specified specific project global preferences.

Hope the above helps or at least gives a clue.

--
terencewee*

Update:

The problem persists and had also affected my other WCG crunchers.

I had since removed 1 device profile (Work) from WCG leaving Default and School.
(2 profiles instead of 3)

WCG -> Project -> Update

Perform sync with BAM = success.

I had the same problem, Willy pointed me at this thread, and after reading it ....

I went to WGC, associated all three machines with the Default WGC location and deleted all other profiles at WGC, then updated all machines with WGC via BAM, and resynched all machines with BOINSTats Manager. Error messages this end when sycnching BAM have gone away, and no recorded messages in Notices.

At BOINCStats end, the three machines are now correctly recognised, although clearly the credit side has yet to synch in - will wait a few days to see how that goes.

Regards
Zy

I reported this problem @WCG.

This happens intermittently, after awhile (hours/days) - I'll encounter a BOINC notice reporting BAM-sync problem.

The only workaround is to delete global_prefs.xml and perform a manual sync with BAM.

I'm updating to 7.0.28 and will report back.

@Zydor:
Looks like I'm not the only one.
Thanks.

I did another attempt at fixing the broken XML in BAM! code. Although I think the problem should be solved at the source, I also think that you all want a working BAM!.

As the problem is intermittent and may take some time to fix I thank you Willy for initiating the extra effort.

You are right, we do want a working BAM.

In addition to missing </venue> tag:
As BAM caters to profiles management (and I want to manage profiles thru BAM or
use global_prefs_override.xml), it is strange to see WCG "school" preferences
being fed into E@H (and all my other running projects) work-slot init_data.xml
as <global_preferences>.

Maybe someone running WCG can confirm by taking a look inside their work-slot
init_data.xml.

Thanks again.