I have had James v3B5 running for several years on a WinServer16 box.
In the last couple of weeks, the service has failed to start. I can
open a command prompt and run James with the 'run' bat file from there
without any problem. I've tried rebooting. I uninstalled the service
and reinstalled it. No luck. I haven't made any changes to the system
other than the mandatory Windows updates. But at this point, I can't
get the service to start. The last two times I tried it, I got error
messages that meant nothing. The most recent one said it didn't have
enough memory. I've got 16GB, and it's running about 45%. Perhaps
somebody can decipher the log below. Not much recent info on google
about the 'unable to allocate a console for the service' message. The
wrapper header output is: Java Service Wrapper Community Edition 64-bit
3.5.24.
Anybody got any suggestions? Thx. Log:
C:\james-3.0.0-b5\log>type wrapper.log
STATUS | wrapper | 2019/08/01 13:06:26 | --> Wrapper Started as Service
ERROR | wrapper | 2019/08/01 13:06:26 | ERROR: Unable to allocate a
console for the service: The specified resource name cannot be found in
the image file. (0x716)
STATUS | wrapper | 2019/08/01 13:06:26 | <-- Wrapper Stopped
STATUS | wrapperm | 2019/08/02 19:06:58 | Apache James :: Server :: App
service removed.
STATUS | wrapperm | 2019/08/02 19:07:12 | Apache James :: Server :: App
service installed.
STATUS | wrapper | 2019/08/02 19:07:26 | --> Wrapper Started as Service
ERROR | wrapper | 2019/08/02 19:07:26 | ERROR: Unable to allocate a
console for the service: Not enough storage is available to process this
command. (0x8)
STATUS | wrapper | 2019/08/02 19:07:26 | <-- Wrapper Stopped
