0 Replies Latest reply on Dec 3, 2013 4:16 AM by Daniel Sailer

    com.bladelogic.om.infra.mfw.util.BlException: ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿

    Daniel Sailer

      In case you come across these warnings in a compliancy jog:

         Info    Dec 3, 2013 8:01:48 AM    Compliance execution finished for component: ...
      Warning    Dec 3, 2013 8:01:48 AM    com.bladelogic.om.infra.mfw.util.BlException: ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿

      The issue is that in the script bmc-localEffective-settings.nsh it is expected that secedit can be run directly, which means that C:\Windows\system32 must be in the path.

      To fix this, add C:\Windows\system32 to the path or replace "secedit" with "%SystemRoot%/system32/secedit" in the script.