Policy failed to load - "Error: Policy action not defined in or visible"
search cancel

Policy failed to load - "Error: Policy action not defined in or visible"

book

Article ID: 431598

calendar_today

Updated On:

Products

ISG Proxy ProxySG Software - SGOS

Issue/Introduction

After the upgrade policy may not load properly with following error:

  • Event log:
     "Policy failed to load because: Error: Policy action not defined in or visible from the 'Isolation_integration_headers' context:"  0 70000:64  cfg_proprietor.cpp:727 
  • https://<proxy_ip>:8082/Policy/current:
    URL_Path /Policy/current
    ; Empty CPL object; Policy could not be loaded at startup; Possible cause:
    ;     - a system downgrade occurred and policy includes features
    ;       that are not supported in this version
    ;
    ; The following compilation problems were reported:
    ; 
    ;   Deprecation warning: 'realm'; The use of mid-layer definitions is deprecated;   local:12: realm=Proxy_IWA condition=IWA_SILENT_USERS user.login.log_out(true)
    ;   Error: Policy action not defined in or visible from the 'Isolation_integration_headers' context: 'Isolation_actionAddIsolationProfileHeader'

Environment

  • Upgrade between various v7.3.x or v7.4.x versions

Resolution

Within config mode "policy-services", disable the service, then purge to return to the original built-in image, as below:

#(config policy-services)disable
#(config policy-services)purge

Check policy compilation status by exiting the policy services config mode and do "show policy listing", as below:

#(config)show policy listing

If there is no error, the issue would have been fixed.

If the above doesn't fix the issue, there may be a chance that the image used for upgrading the failing SG is corrupted. Thus, please remove the existing 7.3.x or 7.4.x  image, redo the download of the upgrade 7.3/7.4 image and reinstall the upgrade image. After successful download and installation, check the policy compilation status again as above. If still error, do the above "disable" and "purge" sequence again, then check the policy compilation afterwards.

If above options don't resolve the issue then factory reset / restore is required.