Troubleshooting › Receive HTTP 500 error in Security and Policy Interface in the Quick Links Module

Receive HTTP 500 error in Security and Policy Interface in the Quick Links Module

Symptom:

When I click the Administer Security Definitions link or Administer Compliance Policy link, I get an HTTP 500 error.

Solution:

This error indicates that the configuration file is in the wrong location or the file does not exist.

Follow these steps:

1. Look out for the following null pointer exceptions in the stack trace:

   javax.servlet.ServletException: javax.faces.el.EvaluationException: Cannot get value for expression '#{vantageTreeBean.userName}' 
   

   The presence of this exception indicates a user error.

   Note: If you find any other errors in the HTTP 500 stack trace, such as other null pointer exceptions, contact CA Technical Support.

2. Verify that the following configuration files exist in the specified directories:
   • For Compliance Policy Administration, locate the configuration file in INSTALL_DIR/config:
     • cmgr_config.xml
   • For Security Administration, locate the following configuration files in INSTALL_DIR/config:
     • acf2_config.xml for CA ACF2
     • tss_config.xml for CA Top Secret

   If the configuration file is not present, you have edited and submitted the job E1MI0014 in the CE1MJCL data set during the installation process.

   Run job E1MI0014 now.

   Important! Restart JBoss to apply the changes.

3. Verify whether you see the following message in the root cause in the stack trace.

   javax.servlet.ServletException: Cannot get value for expression '#{vantageTreeBean.model}' 
   

   This indicates a syntax error in the config.xml file.

   For Compliance Policy Administration, check the configuration file named cmgr_config.xml in INSTALL_DIR/config.

   • For Security Administration, check the following configuration files in the INSTALL_DIR/config:
     • acf2_config.xml for CA ACF2
     • tss_config.xml for CA Top Secret

   Check the options that you specified in these files. Verify that each option is closed correctly with an end tag. For example, verify that the option <ldapsuffix> is correctly paired with its end tag </ldapsuffix> (notice the backslash).