The XML is valid, so it's not a bug in the client. The only potentially-problematic thing I see is long lines in the stderr text, which the so-called XML parser in BOINC might be mishandling.
PS: Note that you just publicly posted the account key of this user. -- Nicolás 2013/5/8, Nx Hien <[email protected]>: > Dr. Anderson, > > A volunteer has just uploaded this file for us, he said his client is > currently displaying the "No end tag" error message. > > Best regards, > Hien > > > ________________________________ > From: David Anderson <[email protected]> > To: [email protected] > Sent: Thursday, May 2, 2013 8:03 PM > Subject: Re: [boinc_dev] Scheduler returns "No end tag" > > > Hien: > Try contacting the volunteers and ask them for the request file. > There must be something in it that the server can't parse. > -- David > > On 02-May-2013 5:35 PM, Nx Hien wrote: >> Dr. Anderson, >> >> I could not get the request files at the time of error since they are on >> the >> client side but I instead attempted to make to server to write out the >> content of the request at the time of error (attached). The 1st half of >> the >> request is missing. This problem happens to multiple clients. >> >> Best regards, Hien _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
