Error processing flow configuration: org.mozilla.javascript.EcmaError: TypeError: Character reference "" 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?
I was testing changes so I had uploaded a new version of my flow when I found the error. I'll double check but our version of IPD and the Rich Client shouldn't have changed. Are you thinking that if the Windows updates on the IPD device (computer) are not the same as the Windows updates on the Landmark/IPA server that might cause an issues?
It turns out it was a new System Configuration who's FTP info had a carat (^) and other special characters in the password.<!--StartFragment-->
Below was posted by Russel C. on the Infor support forum, which helped us figure it out:
"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"
<!--EndFragment-->