Current version:
Nexus Repository OSS 3.72.0-04
Windows Server 2016
Using bundled JRE, no custom options.
Using folder structure E:\Nexus<binary folder> and E:\Nexus\sonatype-work\nexus3\ data folder.
I tried to upgrade from 3.72.0 following the new guides for windows. But had to do a rollback, due to the error message:
[2025-03-07 20:45:52] [info] ( prunsrv.c:1426) [ 6324] Starting service…
[2025-03-07 20:45:52] [debug] ( javajni.c:221 ) [ 6324] No explicit RuntimeLib specified. Checking registry. Found ‘(null)’
[2025-03-07 20:45:52] [debug] ( javajni.c:235 ) [ 6324] Invalid RuntimeLib ‘(null)’, Checking registry for JRE home. None found.
[2025-03-07 20:45:52] [debug] ( javajni.c:263 ) [ 6324] Invalid RuntimeLib ‘(null)’, Checking registry for JDK home. None found.
[2025-03-07 20:45:52] [error] ( javajni.c:268 ) [ 6324] No JVM configured or found in registry. Unable to start service.
[2025-03-07 20:45:52] [error] ( javajni.c:268 ) [ 6324] The system could not find the environment option that was entered.
[2025-03-07 20:45:52] [error] ( javajni.c:416 ) [ 6324] Failed to load JVM DLL ‘(null)’, home ‘(null)’.
[2025-03-07 20:45:52] [error] ( javajni.c:416 ) [ 6324] The system could not find the environment option that was entered.
[2025-03-07 20:45:52] [error] ( prunsrv.c:1465) [ 6324] Failed creating Java ‘(null)’.
[2025-03-07 20:45:52] [error] ( prunsrv.c:1465) [ 6324] The system could not find the environment option that was entered.
[2025-03-07 20:45:52] [error] ( prunsrv.c:1862) [ 6324] ServiceStart returned 1.
[2025-03-07 20:45:52] [error] ( prunsrv.c:1862) [ 6324] The system could not find the environment option that was entered.
I removed the old service with the legacy method and went through the install-nexus-service.bat, without changing anything before running that. Tried running it both in cmd and powershell just to make sure there weren’t any gotchas there.
I cannot find any mentions of this in the additional 3.78.1 fixes, so I am unsure if I should try 3.78.1, or if I have missed a required step for this version. I have a feeling I have done a newbie mistake, since previous upgrades including the one migrating to H2 database, have always been without any issues.