Omada Controller v4.x.x fails to start due to MongoDB
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Controller v4.x.x fails to start due to MongoDB
Originally running Omada Controller v4.3.5 successfully. After long absence from office, finding software no longer starts after Windows machine restart due to failure to start MongoDB. Attached file shows dialog box screen capture.
Tried upgrading to software version 4.4.4, same issue.
Reviewing other forum threads, found repair of MongoDB might be solution. Did this but no change.
Confirmed there are no *.lock files under Omada software database directory.
Disk has over 200GB free space.
How can I get this tool for start correctly?
File:
2021-08-28.pngDownload
1 Accepted Solution