Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Difference between AdminServer as a service and running it manually on Windows.

Martin HoppeNov 25 2025

Hi

Running: WLS 14.1.2.0 and FORMS and REPORTS 14.1.2.0.0

I created the NodeManager as a Windows Service using the installNodeMgrSvc.cmd delivered by the installation.

Then I proceeded to create a service for the AdminServer, using the guide supplied by Oracle:

"
SETLOCAL
set DOMAIN_NAME=base_domain
set USERDOMAIN_HOME=xxx\user_projects\domains\base_domain
set SERVER_NAME=AdminServer
set WL_HOME=xxx\wlserver
set PRODUCTION_MODE=true
set WLS_USER=xxx
set WLS_PW=xxx
set MEM_ARGS=-Xms512m -Xmx1024m
call "xxx\user_projects\domains\base_domain\bin\setDomainEnv.cmd"
call "xxx\wlserver\server\bin\installSvc.cmd"
ENDLOCAL
"

Blanked for privacy.

I then run wlst.cmd in order to create a ReportsToolsInstance:

connect("xxx","xxx","admin://xx.xx.xx.xx:9002")

createReportsToolsInstance(instanceName='reptools1',machine='AdminServerMachine')

When I do that I end up with this stacktrace:

"
javax.management.RuntimeErrorException: Could not initialize class oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls.
javax.management.RuntimeErrorException: Could not initialize class oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:988)
……
……

Caused By: java.lang.NoClassDefFoundError: Could not initialize class oracle.sysman.oii.oiip.osd.win32.OiipwWin32NativeCalls
at oracle.sysman.oii.oiix.OiixRegistryOps.RegKeyExists(OiixRegistryOps.java:123)
……
……
Caused By: java.lang.ExceptionInInitializerError: Exception java.lang.UnsatisfiedLinkError: no oraInstaller in java.library.path:
at weblogic.utils.StackTraceDisabled.unknownMethod()
"

Then I tried stopping the AdminServer service, starting it manually with the startWebLogic.cmd…. and I could redo the steps with creating the ReportsToolsInstance succesfully.

WLS_FORMS and WLS_REPORTS are starting and at least on the surface are running as they should, when started through the admin console, both when the AdminServer is running as a service and when it isn't.

My guess is that its some context that are missing when running it as a service, and I have seen some minor differences between both CLASSPATH and PATH when comparing them across the 2 modes of running the AdminServer…. but I cannot figure out why there are any differences or if they would cause this issue.

Have anyone encountered anything similar, in the service/not-serviced AdminServer?

Comments
Post Details
Added on Nov 25 2025
7 comments
180 views