Validation of XML ruleset files

Archiving tasks that are enabled for custom filtering validate ruleset XML against the schema, ruleset schema.xdr, when they start archiving items. If any of the XML is invalid, the tasks stop and you must correct any errors before restarting them.

To avoid disrupting tasks because of syntactic errors, it is a good idea to validate your XML file before it is accessed by the tasks. You could use a third party tool, such as the graphical XML Editor in Liquid XML Studio:

http://www.liquid-technologies.com/XmlStudio/Free-Xml-Editor.aspx

When using the tool, specify the namespace as:

x-schema:ruleset schema.xdr

The schema file, ruleset schema.xdr, is shipped in the Custom Filter Rules folder . The schema must be referenced at the start of any ruleset files as follows:

<?xml version="1.0"?>
<RULE_SET xmlns="x-schema:ruleset schema.xdr">

If the file contains non-ANSI characters, ensure the correct encoding is set on the first line and save the file using the appropriate encoding.

Note:

All the XML tags and predefined values shown in upper case in this document are case-sensitive and must be entered as upper case in the ruleset file. Values entered should also be treated as case-sensitive.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.