If you're logging into Analyze and the login prompt returns an error that solely says
null, that is indicative of the Tomcat service being online but the Application service is either offline or still starting up.
This is most common after a server restart, product installation or product upgrade. The Tomcat service will start much faster than the Application service. When this happens, the product UI will be available due to the Tomcat service being online, but the login request will not be able to connect to the Application server to perform the login. The error
null is return in this scenario.
If the Application service is offline, then you need to start it for the login screen to handle the request.
If the Application service is online, you may need to wait upwards of 10 minutes for the initial startup load to complete. Afterwards, you will be able to login successfully.
If you want to know exactly when you can login again, you can monitor the lae-webapp.log file. In it, you will see these two messages before the initial startup load is complete:
INFO root:93 - Auto-loading LNA: /space/brain/app/d3sa/lib/lna/import/base-3.6.1.lna
INFO root:93 - Auto-loading LNA COMPLETE: /space/brain/app/d3sa/lib/lna/import/base-3.6.1.lna
Once the official startup load is complete, you should see this message appear:
INFO root:50 - Application Entered State: READY Steps: 0 Current Step: Ready
The system is not "ready" and may return that "null" message if you don't wait for the above READY message to appear in the lae-webapp.log file.