Server Could Not be Evaluated

Which IIQ version are you inquiring about?

8.4p1

We are running into an error on the Certification Schedules and Work Item Archive pages with a popup that states:
An unexpected error occurred. The server could not be evaluated.

Does anyone know how to remediate?

Hi @Alyson_Trad

Please get the stack traces from logs, which will be helpful to analyze.
{Your specific stack trace would be key to identifying the root cause.}

log traces from the main IdentityIQ log files on your application server. This is usually identityiq.log or catalina.out (if you’re running on Tomcat).

  • identityiq.log: This is your first and most critical stop. Look for SEVERE, ERROR, or WARNING messages around the time the error occurs. Pay close attention to stack traces.
  • catalina.out (for Tomcat) or application server logs: These logs can reveal JVM-level errors, OutOfMemory errors, or issues with the application server itself.
  • Look for keywords: “server could not be evaluated,” “unexpected error,” “database connection,” “SQL,” “OOM,” “java.lang.NullPointerException,” or any other exceptions.

In log4j2.properties you will find entry like property.logLocation for exact lication.

property.logLocation=D:/Instances/Tomcat/logs/

Hi @Alyson_Trad
There will be an error code usually generated when you get that error message, using that code you can check in syslog that error message to see what type of error. Example: null pointer exception/any code error
Based on the error type, you can troubleshoot further by enabling debug loggers.

Hi @Alyson_Trad

Few remediation steps in general: {if it is an intermittent rendering issue}

  1. Clear Caches (from Debug pages - Reset Configuration Cache)

  2. Restart application server:

  • Stop IdentityIQ: Shut down your IdentityIQ application server.
  • Clear Tomcat Work/Temp: For Tomcat, clear the work and temp directories within your Tomcat installation. {just delete inside content keep the folders as it is}
  • Restart IdentityIQ: Start the application server.

You can enable the workitem and Certification logs in log4j2.properties, and check the cause of the issue. You can provide the trace of identityiq.log here.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.