Error message "Invalid Ruleset"

Problem 1

ELO Automation Services (ELOas) runs but the following error message is displayed in the log file: Invalid Ruleset suspended: org.xml.sax.SAXException: Invalid ruleset definition: Premature end of file.

Even though the rules are defined correctly (correct spelling, no error while parsing the xml document in IE), the file cannot be read by ELOas, i.e. the request takes place but an empty document is triggered (as can be seen by the empty lines of the log file) and an error message appears. Check whether the ELOas user has sufficient rights. Check whether the Indexserver and Document Manager of the repository in question have errors in their log files. Try using another client for testing. Instead of saving the script in a txt file in the Rules folder, save it as a separate folder in Rules (in the extra text of the folder) so that the script is regarded as a database entry.

Another approach: Check whether the most current version of ELO Automation Services is used and whether the following entry is available in the XML file at ELOprofessional\config\as-<repository name>:

<entry key="tempdir">C:\temp2</entry>

This temporary directory must exist, as otherwise an error message will appear. The user must have write access to the temp directory at the system level.

Problem 2

When creating a second rule, not every group field is available in the drop-down menu the first time.

In this case, the ELO Administration Console must be closed and opened again. Warning: This does not apply for the first rule you created!