We should use the java 8 (jre 1.8.0) to run the Omada Controller.Go to HKEY_CLASSES_ROOT\jarfile\shell\open\command to check the running data of the java running environment.Input “regedit” to open the registry editor. Modify the running path of java in registry editor of windows.Use command java –jar “omada-start.jar” to start the Omada Controller.Open the CMD in windows system, use the cd command to log in to the “lib” folder of Omada Controller, such as cd C:\Users\Administrator\Omada Controller\lib.Start the Omada Controller via the CLI command.The default path of “start.bat” is C:\Users\Administrator\Omada Controller\bin\start.bat. Go to the “bin” folder of the Omada Controller installation path and double click the “start.bat”, check if we can start the Controller successfully.
Start the Omada Controller via “start.bat”.Here are some solutions to fixed this issue. Generally speaking, a high java version (we should use java 8 to run the Controller) or the wrong java start path in windows REGEDIT may cause this issue, since we need to use the java runtime environment to start the Omada Controller. Sometimes we may face the issue that the Controller start page will not pop up automatically when double click the start icon, and we can’t start the Omada Controller successfully. Suitable for Omada Controller V4.1.5 or above.
0 kommentar(er)
