a TCP Trace would help if this is reproducible consistently. I am not
aware of any issue with that event and Chrome or Safari.
That error happens when a hyperevent is issued but the response is not
a valid XMLHTTP response = XML block with a status output. You see
this in FF and IE as well when a hyperevent crashes or fails or is
incomplete
Bill McCormick
Product Manager
Development Technologies
+1 617 621 0600
bill.mc...@intersystems.com