I saw this in a WU :

<message><file_xfer_error>
<file_name>long_wu_name</file_name>
<error_code>-161</error_code>
<error_message></error_message>
</file_xfer_error>

</message>

The first line seems problematic to me. If the server side XML parser works in the same way as the client side parser, it will not handle a line with more than one tag.
________________________

The same behaviour (reading XML line by line) can cause a problem in this sched_reply (from a different project) :

<result>
<report_deadline>...</report_deadline>
<wu_name>...</wu_name>
<name>...</name>
<file_ref>
<file_name>...</file_name>
<open_name>...</open_name>
</file_ref>
</result><gui_urls>

Here the result record is missing a CR at the end, which confuses the client totally, causing download errors. It even has the potential to damage client_state entries of other projects.
____________________________

It would be good to put additional CRs when those files are assembled on client and server side, just to avoid trouble.