Omada v4.1.5 won't execute
Omada v4.1.5 won't execute
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi All,
If you happen to have the same problem mentioned in this topic, please refer to the following FAQ to fix the issue.
- Copy Link
- Report Inappropriate Content
Dear @JoyriderBC,
There is no error message, no login prompt. It doesn't seem to do anything.
Please check the Tray bar on your W10 Pro computer and see whether the Omada V4.1.5 icon is hidden there. If yes, click on the icon there to launch the Omada Controller.
If it doesn't show up in the Tray bar, try launching a web browser and visit http://localhost:8088 or https:localhost:8043 to check if you can access the management interface of Omada Controller. Besides, you may also try rebooting the computer and see if it helps.
- Copy Link
- Report Inappropriate Content
I got the same problem here.
I ordered a pair of EAP245. Not yet delivered.
I thought let me install the software already.
The first time it starts perfectly (see server1.log)
The second time there is no login prompt? As you can see in server2.log the software hangs on: Starting facade module.
When I reinstall the software the same thing happens
Specs:
Win10
Omada_Controller_V4.1.5_Windows
Java 8 installed
[server1.log]
2020-11-02 01:28:37 [log4j-thread] [INFO]-[SourceFile:29] - success to load configuration omada.properties
2020-11-02 01:28:37 [main] [INFO]-[SourceFile:314] - Starting facade module...
2020-11-02 01:28:38 [JavaFX Application Thread] [INFO]-[SourceFile:110] - Omada controller starting...
2020-11-02 01:28:38 [main] [INFO]-[SourceFile:75] - going to start local mongod.
2020-11-02 01:28:38 [main] [INFO]-[SourceFile:360] - use 64 bit mongod.exe
2020-11-02 01:28:38 [main] [INFO]-[SourceFile:158] - mongodb process id is 5640
2020-11-02 01:28:38 [main] [INFO]-[SourceFile:139] - Mongo DB server started
2020-11-02 01:28:49 [main] [INFO]-[SourceFile:35] - monitor context initialing...
2020-11-02 01:28:50 [main] [INFO]-[SourceFile:299] - restart all customize tasks.
2020-11-02 01:28:51 [device-discovery-server] [INFO]-[SourceFile:54] - Start device discovery server
2020-11-02 01:28:51 [device-manage-server] [INFO]-[SourceFile:111] - Start device manage server
2020-11-02 01:28:51 [device-adopt-server] [INFO]-[SourceFile:82] - Start device adopt server
2020-11-02 01:28:51 [main] [INFO]-[SourceFile:126] - no need to compatible db.
2020-11-02 01:28:51 [main] [INFO]-[SourceFile:20] - Omada Controller started
[server2.log]
2020-11-02 01:30:23 [log4j-thread] [INFO]-[SourceFile:29] - success to load configuration omada.properties
2020-11-02 01:30:23 [main] [INFO]-[SourceFile:314] - Starting facade module...
Does anyone have an idea what's wrong?
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
- Solution 1 Fail
- Solution 2 Fail
- Solution 3 Fail
All three options are unsuccessful, i think it has to do with java.
I am now back on version omada 3.2.10, it works perfectly.
it's just strange that it works the first time.
I can login on the user interface no problems.
After a reboot, omada doesn't want to work anymore.
No popup whatsoever.
:(
- Copy Link
- Report Inappropriate Content
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)?
- Copy Link
- Report Inappropriate Content
I am having the exact same problem. Immediately following install it ran itself successfully and stayed up for days. I restart the machine and it won't launch from the start menu shortcut. However, trying to uninstall it led to it complaining that it WAS running, though the web server wasn't reachable.
Running from the start.bat script is the only way it would start up successfully. I assume the link 4.1.5 is setting up in the start menu/desktop is pointing just to a particular jar file with java and isn't actually launching the prerequisites or other services it needs to succeed.
- Copy Link
- Report Inappropriate Content
Okay we have made some progress.
V4.1.5 works when I run it with the bat file.
As a test I have V4.1.5 uninstalled and install version V4.2.4.
The same problem occurs, i only can run it with the bat file.
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
- java version "1.8.0_271"
- Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
- Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
When I installed Omada v4.1.5 he asked to install java 8 as well.
So I just got the latest version from the java site.
I am now running Omada v4.2.4 and still start it with the bat file.
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5208
Replies: 11
Voters 0
No one has voted for it yet.