Cannot get to work.....cant sparse schelduler reply????

Questions and Answers : Getting started : Cannot get to work.....cant sparse schelduler reply????

Author	Message
Carthman Send message Joined: 14 Aug 03 Posts: 1 Credit: 248 RAC: 0	Message 3544 - Posted: 2 Jul 2004, 16:49:16 UTC Last modified: 2 Jul 2004, 16:49:50 UTC
	What does all this mean and how do I get it corrected??? Thanks in advance --- - 2004-07-02 12:41:05 - Starting BOINC client version 3.19 for windows_intelx86 --- - 2004-07-02 12:41:05 - Renaming account_.xml to account.xml --- - 2004-07-02 12:41:05 - Couldn't rename account_.xml to account.xml --- - 2004-07-02 12:41:05 - Warning: not adding project account_.xml SETI@home - 2004-07-02 12:41:05 - Project prefs: no separate prefs for home; using your defaults SETI@home - 2004-07-02 12:41:05 - Host ID is 40867 --- - 2004-07-02 12:41:05 - General prefs: from SETI@home (last modified 2004-06-30 20:07:39) --- - 2004-07-02 12:41:05 - General prefs: no separate prefs for home; using your defaults --- - 2004-07-02 12:41:06 - Fewer active results than CPUs; requesting more work SETI@home - 2004-07-02 12:41:06 - Requesting 404062 seconds of work SETI@home - 2004-07-02 12:41:06 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-02 12:41:15 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-02 12:41:15 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-02 12:41:15 - Can't parse scheduler reply SETI@home - 2004-07-02 12:41:15 - Deferring communication with project for 3 hours, 15 minutes, and 26 seconds
	ID: 3544 ·

John McLeod VII Volunteer developer Volunteer tester Send message Joined: 15 Jul 99 Posts: 22343 Credit: 439,209 RAC: 396	Message 3554 - Posted: 2 Jul 2004, 17:01:22 UTC
	SETI@home - 2004-07-02 12:41:15 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-02 12:41:15 - Can't parse scheduler reply This is happening intermittently to a few users. Nobody knows exactly what is wrong, but it appears to be a server/client mismatch of some sort. Since 3.19 is the only client available, we have decided to blame the problem on the server.
	ID: 3554 ·

Questions and Answers : Getting started : Cannot get to work.....cant sparse schelduler reply????