I just had a similar issue and it turned out to be due to one record having a
high ASCII character or a corrupt character at the end of a text field. Had to
do a treasure hunt to find the record. The client did not have this problem
prior to updating to FMS15, but then it started killing queries after the
switch.
Dale
On Apr 7, 2017, 12:27 PM -0400, Troy Meyers <tcmeyers@xxxxxxxxxxxxxx>, wrote:
Thanks, Chris!
I presume the XML queries are identical since I'm just repeatedly refreshing
the page, which normally works, to bring on the error. Maybe the WPE is
overworked and sending something about that back?
I'm pretty sure I could reproduce it, so if there's some way to collect what
the reply was, maybe know that would help you gracefullicize it.
-Troy
Hey Troy,
I've seen that one from time to time. Basically, if FileMaker has any
sort of problem returning the requested data, it returns an HTML error
page (not valid XML). The XML parser in FX.php doesn't like this. The
page in question could be a 404, for example, or an authentication
error. I'm working on updating FX.php, and this is something that I
should handle more gracefully, since FMS doesn't.
Best,
--Chris
_____________________________________________________________________
FX.php Official Web Site -- http://fx.iviking.org/
FX.php Official Mailing List -- //www.freelists.org/list/fx.php_list
(Subscribe, unsubscribe, and more at the mailing list site!)
FX.php_List@xxxxxxxxxxxxxxxx
