I have checked global_prefs.xml file and all </venue> tags were in place.
But i have noticed other "anomaly" - there was a missing linefeed/line break between last </venue> tag and </global_preferences> tag (very end of file). Last line in the file was formatted like this </venue></global_preferences>
I tried to add linefeed, so corrected file now ends like this:
</venue>
</global_preferences>
And error message disappeared!
But i think this message about "Invalid global preferences supplied" itself is an error in this case! Because line breaks in xml files are optional, xml file remains correct if all necessary tags are present, lack of line break between them only affects visual readability for humans, not machines. It is still a valid file regardless of its visual formatting with spaces and line breaks.
P.S.
Funny fact: I also tried to intentionally delete line break between few other tags. And looks like E@H server is just fine with it (exactly how it should be!) - no any additional messages on event log. For some reason, it is getting angry only about the lack of a line break between </venue> and </global_preferences> tags!
Ok for me a different resolution and perhaps the error message was a red herring. I found in my Account Preferences for the Project an unused "Home" profile that dated back years ago when I ran separate Work and Home preferences. Over the years Einstein had made changes to their profile rules and the way I had the "Home" profile was invalid. I deleted the unused Home profile and the Event Log error on my BOINC client disappeared.
Thanks wonderful holidays to everyone
Bill F
In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.
Ich habe das Problem so eben gelöst doch ich weiß nicht mehr wie ich es geschafft habe.
Warum ?
weil ich vieles durcheinander ausprobiert hatte und die Fehlermeldung kommt nicht mehr nach einem Neustart des Boinc Manager.
Ich weiß nur noch das ich den eintrag so vorgenommen habe . </venue></global_preferences>
ich ging zur webseite zurück zu Einstein aktualisierte meine PC einstellungen dort.
Ich startete den Manager neu und es kam die meldung nicht mehr .
Entschuldigt bitte ich kann es nicht mehr genau sagen es ist schwer ABER DIE FEHLER MELDUNG IST WEG!!!
mfg.
I just solved the problem but I don't remember how I did it. Why ? because I had tried a lot of things mixed up and the error message no longer comes after restarting the Boinc Manager. I only know that I made the entry that way. </venue></global_preferences>
I went back to the Einstein website and updated my PC settings there. I restarted the manager and the message no longer came up.
I have checked global_prefs.xml file and all </venue> tags were in place.
But i have noticed other "anomaly" - there was a missing linefeed/line break between last </venue> tag and </global_preferences> tag (very end of file). Last line in the file was formatted like this </venue></global_preferences>
I tried to add linefeed, so corrected file now ends like this:
</venue>
</global_preferences>
And error message disappeared!
This stopped the message for me. My global prefs XML had no LF's at all.
Just added a LF after </venue>
No other project complains and I'm connected to a LOT of projects.
Shouldn't. Normally, XML only cares about matching opening and closing tags. If in doubt I always parse any XML file that I might be editing through a XML validator to check for obvious errors and a sanity check on the file content.
Definitely shouldn't! But in fact absence of LF leads to errors.
It looks like a bug in the XML parser on the E@H server, because all other BOINC projects accept the same XML preferences file from the same client without any problems, without any difference in how spaces or line feeds are placed in it (as it should be - in XML, only tags have meanings).
P.S.
Since my last post(it's been over a year now), I had to edit the file a couple more times by adding line breaks to get rid of error messages from the E@H server each time client contacts it.
I got this annoying message
)
I got this annoying message too recently.
I have checked global_prefs.xml file and all </venue> tags were in place.
But i have noticed other "anomaly" - there was a missing linefeed/line break between last </venue> tag and </global_preferences> tag (very end of file). Last line in the file was formatted like this
</venue></global_preferences>I tried to add linefeed, so corrected file now ends like this:
</venue></global_preferences>
And error message disappeared!
But i think this message about "Invalid global preferences supplied" itself is an error in this case! Because line breaks in xml files are optional, xml file remains correct if all necessary tags are present, lack of line break between them only affects visual readability for humans, not machines. It is still a valid file regardless of its visual formatting with spaces and line breaks.
P.S.
Funny fact: I also tried to intentionally delete line break between few other tags. And looks like E@H server is just fine with it (exactly how it should be!) - no any additional messages on event log. For some reason, it is getting angry only about the lack of a line break between </venue> and </global_preferences> tags!
Ok for me a different
)
Ok for me a different resolution and perhaps the error message was a red herring. I found in my Account Preferences for the Project an unused "Home" profile that dated back years ago when I ran separate Work and Home preferences. Over the years Einstein had made changes to their profile rules and the way I had the "Home" profile was invalid. I deleted the unused Home profile and the Event Log error on my BOINC client disappeared.
Thanks wonderful holidays to everyone
Bill F
In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.
Ich habe das Problem so eben
)
Ich habe das Problem so eben gelöst doch ich weiß nicht mehr wie ich es geschafft habe.
Warum ?
weil ich vieles durcheinander ausprobiert hatte und die Fehlermeldung kommt nicht mehr nach einem Neustart des Boinc Manager.
Ich weiß nur noch das ich den eintrag so vorgenommen habe . </venue></global_preferences>
ich ging zur webseite zurück zu Einstein aktualisierte meine PC einstellungen dort.
Ich startete den Manager neu und es kam die meldung nicht mehr .
Entschuldigt bitte ich kann es nicht mehr genau sagen es ist schwer ABER DIE FEHLER MELDUNG IST WEG!!!
mfg.
I just solved the problem but I don't remember how I did it. Why ? because I had tried a lot of things mixed up and the error message no longer comes after restarting the Boinc Manager. I only know that I made the entry that way. </venue></global_preferences>
I went back to the Einstein website and updated my PC settings there. I restarted the manager and the message no longer came up.
Excuse me, I can't say exactly anymore,
it's difficult BUT THE ERROR MESSAGE IS GONE!!!
Kind regards.
Mad_Max wrote: I got this
)
This stopped the message for me. My global prefs XML had no LF's at all.
Just added a LF after </venue>
No other project complains and I'm connected to a LOT of projects.
A whitespace changes parsing
)
A whitespace changes parsing result of a XML file? There's something fishy going on...
Shouldn't. Normally, XML
)
Shouldn't. Normally, XML only cares about matching opening and closing tags. If in doubt I always parse any XML file that I might be editing through a XML validator to check for obvious errors and a sanity check on the file content.
https://www.xmlvalidation.com/index.php
Definitely shouldn't! But in
)
Definitely shouldn't! But in fact absence of LF leads to errors.
It looks like a bug in the XML parser on the E@H server, because all other BOINC projects accept the same XML preferences file from the same client without any problems, without any difference in how spaces or line feeds are placed in it (as it should be - in XML, only tags have meanings).
P.S.
Since my last post(it's been over a year now), I had to edit the file a couple more times by adding line breaks to get rid of error messages from the E@H server each time client contacts it.