Menu
▾
▴
#281 App runs ok via wrapper -c, fails when running as service
Getting a generic "The system cannot find the path specified. (0x3)" error when I attempt to start my application as a service. However, using the service wrapper with a -c for console mode runs fine. Any ideas on what the issue might be?
log file extract
an update - it looks like the service isn't picking up the drive substitution mapping that I run under (D: drive is a substitute for a subdirectory on C:) - which makes sense since that drive mapping is only available in the context of my windows session.
Thank you for the followup.
When the Wrapper is running as a service, it runs in the environment of the SYSTEM user by default. The D drive mapping on your system is most likely in your user context so it would explain the problem you are having.
Many people have issues like this with network drives. The workaround there is to use universal path format: "¥¥host¥share¥dir" rather than referencing the mapped drive.
We have implemented a new feature for our 3.5.0 release which will allow you to set up drive mappings that will be setup before the JVM is launched. We will run some tests to see how this works with local mappings like yours.
Cheers,
Leif
We ran some tests and the new 3.5.0 mapping feature works fine with local drive mappings like the one you are using. We are hoping to have 3.5.0 out in a couple weeks. Drive mapping will be a Standard & Professional Edition feature.
Currently, it is also possible to set up drive mappings using the event command feature of the Professional Edition.
thanks both for your responses - we'll definitely take a look at the 3.5.0 version once it's out!