Javascript error .. invalid XML character

Error processing flow configuration: org.mozilla.javascript.EcmaError: TypeError: Character reference "&#3" is an invalid XML character. (initJavaScriptContext#1)

All of a sudden we are getting the above error in our TEST system for ALL of our process flows. (we are still on v10 IPA and Landmark and LSF.) I was testing something new and found the problem but it started on the 18th of March. Apparently we put a windows update, etc... in place that night. My SysAdmin has a ticket open with Infor and has tried backing out a few of the updates, but we are still getting this error. I'm clueless, I have no idea what this error is referring to, especially since it is happening on process flows that have been in place an working for quite a while. The error occurs when or before it hits the Start Node. Has anyone seen this before? Any suggestions?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

unknown

Well dang! That worked! Thank you both JD and Russel. It was the new configuration with a ^ in the password for the FTP. I tried just deleting the password but that didn't work. I deleted the entire configuration and now everything is working again.

THANKS!

All comments

russel-cornelson

@herzfeldtj

The error message is telling you that one of your configurations has invalid XML character in it.

Before the start node executes the system will load ALL configuration sets in your system into the workunit so it doesn't need to look them up from the database at execution time. So it can be any configuration on any configuration set.

Unless there is more to that error above, I can't narrow it down any further. You are looking for an invalid configuration added to Infor Process Automation on the 18th of March. Backing out patches/updates won't fix it because its data related to that invalid config.

Hope this information helps, and if you have a stack trace that goes along with that error you should send it we can likely find the type of configuration it is with more of the error to look at.

john-miller

A long time ago, the first time I tried to upload a public key, I messed up and installed the key encrypted, and it gave me a similar error. If you're on V10 IPA, this is not an issue as V10 IPA does not have Encryption or Decryption nodes.

To check if someone entered a new or updated an existing configuration, query your PfiConfigurationProperty table and sort on CSTimeStamp descending then USTimeStamp descending.

russel-cornelson

JD you are likely onto something. Not with encryption, but with public keys.

If there is no additional error in the LPA node log that indicates a stack trace error that we can use. Start looking for recently created "File Transfer" configurations.

These could have SFTP private keys; which is more likely to be stored as XML.

john-miller

Now that you say FTP Configuration, I once messed up a password and received a global failure too.

ewingm

If the password contains a caret '^' character, does the system treat it as a caret? Or, does it treat it as part of a Control Character sequence?

unknown

THANKS!

Copyright © 2025 Infor. All rights reserved.