Invalid XML character no longer causes a failed policy template run

  • 7023268
  • 14-Aug-2018
  • 14-Aug-2018


Secure Configuration Manager 7.1


This release resolves an issue where a policy template run failed with following type of error:

An invalid XML character (Unicode: 0x8) was found in the element content of the document


Ensure that you complete the following procedure:

To escape invalid characters:

  1. In the Core Services Configuration Utility, select the Advanced tab.

  2. For gladiator/securitycheckup/filter/EscapeInvalidChars, set the value to True.

  3. Restart the NetIQ Core Services service.


This issue occurred because the name of a group included one of the following character sets that must be escaped in XML: \a\b\f, or \v. For example, the group is Texas\balanced. Secure Configuration Manager could not parse the '\b' part of the name because the characters represent the backspace action in code. Alternatively, you might have encountered this issue when you ran a policy template that checks a group policy such as "Log on as a service" where the users might be similar to the following names:

  • domain\adam
  • domain\bangalore
  • domain\frank
  • domain\vance