This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Omada v4.1.5 won't execute
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I installed v4.1.5 from scratch on a W10 Pro computer and added Java. It ran 1 time and I setup the EAP225 Outdoor and logged out. Now the Omada Controller will not run. This is the shortcut property. "C:\Users\User\Omada Controller\lib\omada-start.jar" . There is no error message, no login prompt. It doesn't seem to do anything. I disabled security and using Java defaults. Run as Administrator and User Access Controls disabled.
Dear @Lowie,
I installed the Omada V4.1.5 on Windows 10 and it runs without such issues.
For your reference, there are some solutions to the “exe files are not opening” issue found from the Internet.
- Solution 1
1) Press Windows + R key and type cmd in the box to open the command
2) Type sfc /scannow and press Enter to run SFC scan
3) Wait for the scanning process to 100% complete
4) Reboot the PC and check it works.
- Solution 2
1) Press the Windows + R key and type Regedit in the box to open the Registry Editor window
2) In the left menu, click on the HKEY_CLASSES_ROOT to expand the section
3) Scroll down to find out the .exe registry and click on it
4) On the right side of the window, double-click on the Default and ensure the Value Data is set as exefile
5) Back to the left menu, scroll down to find out exefile>shell>open>command and click on command.
6) On the right side of the window, double-click on the Default and ensure the Value Data is set as "%1" %*
- Solution 3
1) Press the Windows + R key and type Regedit in the box to open the Registry Editor window
2) Locate to the path HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>Windows>CurrentVersion and click on CurrentVersion
3) On the right side of the window, double-click on the ProgramFilesDir and ensure Value Data is set to C:\Program Files
If you use x64 bit, then click on the ProgramFilesDir (x86) and ensure the Value Data is set to C:\Program Files (x86)
Hope the information above is helpful.
Dear @Lowie,
Would that work if you run start.bat (it's in the under the bin folder from the path where you installed the Controller)?
Hi,
According to the server.log, we guest it may be because you have use the high version JAVA to start the Omada SDN controller, since the SDN controller can only start via JAVA8. I think you can check if you have install other JAVA version in the windows10 PC.
1. Please use Win+R button, and enter "regedit" to open the REGEDIT of the window, go to \HKEY_CLASSES_ROOT\Applications\javaw.exe\shell\open\command to check the install path of javaw.exe, such as
if it is not the java1.8, it means you have used other java version to start the Omada Controller and cause this issue
2. You can also go to C:\Program Files\Java to check the java version.
Hi,
We have checked one PC which has the similar issue and find it may be the java installation issue.
Please use "win+R" and the "regedit" to open the REGEDIT of windows. Go to \HKEY_CLASSES_ROOT\Applications\javaw.exe\shell\open\command to check the
The correct command data, has "-jar".
The command data which has the issue, miss the "-jar".
Solution:
1. Please use the CMD to go the the xxx\Omada Controller\lib path, start the Omada Controller via the command java -jar "java-start.jar", check if we can start the controller in this way.
2. If you can start the Omada Controller in step1, you can go to the REGIDIT to add -jar in the command \HKEY_CLASSES_ROOT\Applications\javaw.exe\shell\open\command.