Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Got the error message 'XML error: Not well-formed (invalid token) at line 1' after upgrading FileMaker 17 to 2023 #50

Open
kmunaispits opened this issue Dec 7, 2023 · 2 comments

Comments

@kmunaispits
Copy link

I am currently grappling with an issue following the upgrade from FileMaker Server 17 to FileMaker Server 2023. Specifically, we are encountering difficulties accessing and manipulating data through the FileMaker PHP-API. The error message 'XML error: Not well-formed (invalid token) at line 1' consistently appears, hindering our system's functionality.

In light of this challenge, we are reaching out to seek your expertise and guidance on potential solutions. Have there been any reported compatibility issues between the FileMaker PHP-API and FileMaker Server 2023, and are there recommended steps to address the 'XML error' we are encountering? Your timely assistance in resolving this matter is highly appreciated.

@airmoi
Copy link
Owner

airmoi commented Dec 26, 2023

Hi @kmunaispits,

Did you get it to work ? This error basically means the XML engine is not activated on your serve it does not respond with a valid XML packet.
Please ensure you have enabled Custom Web Publishing as well as PHP
You can check if it is properly enabled by open this address in your browser (you should have a proper xml response) :
https:///fmi/xml/fmresultset.xml

@qt2git
Copy link

qt2git commented May 10, 2024

Hii airmoi

I get the same error on a FMS 20.3.2 Server:
An error occured XML error: Not well-formed (invalid token) at line 1 - Code : -1
XML ist enabled and I get a correct answer when calling /fmi/xml/fmrestultset.xml
PHP and CWP do not exist on the 20.3.2 version anymore, but the Data API is enabled.

What can be the reason for this - do you have a solution for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants