Learn more about possible problems when Kernel 4.4: Preparing the update and implementation (on-premise installation) and how to deal with them in this article.
- Service is not restarted after installation
- Service pack cannot be installed via the command line (install_servicepacks.cmd)
- System does not start after installation/installation is aborted
- System is not restarted after installation
- Mozilla Firefox loads slowly
Service is not restarted after installation
If the system is still not available after 15 minutes, the service startup may not have been successful. If this is the case, check if “Warnings” or “Errors” occurred at the end in the deploy.<current date>.log file in the log directory below the installation directory:
If the number “0” is displayed behind both “Warnings” and “Errors”, then no errors have occurred. In this case, you can start the service with bin/start_service.cmd. With this, installation of the kernel update has been completed successfully and the AEB Engine can be used productively. If the file is missing or another value than 0 is displayed, contact the AEB support.
Service pack cannot be installed via the command line (install_servicepacks.cmd)
Installation via bin/install_servicepacks.cmd is not possible. In the log directory, the spimporter.log file contains the following error message:
“java.lang.UnsupportedClassVersionError: de/aeb/xnsg/deploy/installer/ServicepackInstaller has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0”
In such cases, upload the kernel update to the server and perform the installation from the interface (see Kernel 4.4: Preparing the update and implementation (on-premise installation)).
System does not start after installation/installation is aborted
There may not be enough space available for the installation. Make sure that there is 3GB of free space on the installation drive. If this is already the case, contact the AEB support team.
System is not restarted after installation
If your system does not restart after the kernel update, this may be due to so-called JVM arguments. This is logged in the wrapper.log file. A log entry for this error looks like this:
STATUS | wrapper | 2022/09/01 08:55:01 | Launching a JVM...INFO | jvm 1 | 2022/09/01 08:55:01 | Unrecognized VM option 'PermSize=128m'INFO | jvm 1 | 2022/09/01 08:55:01 | Error: Could not create the Java Virtual Machine.INFO | jvm 1 | 2022/09/01 08:55:01 | Error: A fatal exception has occurred. Program will exit.ERROR | wrapper | 2022/09/01 08:55:01 | JVM exited while loading the application.
Check the product_configuration.properties file of your installation for JVM arguments, e.g. PermSize=[NUMBER]. Remove the PermSize argument, as it may prevent the system from restarting after updating to the new kernel.
Mozilla Firefox loads slowly
In some cases (for example, when opening the application or switching between tabs), long loading times occur in the Mozilla Firefox browser.
In this case, in the Mozillla Firefox browser, type “about:config” in the address bar and click Enter to open the configuration menu. Confirm the Accept Risk and Continue warning message.
Now search for “accessibility.force_disabled” in the configuration menu and change the value from “0” (disabled) to “1" (enabled). Confirm this change.