This isn't something I've seen before, but here's what I'd try:
- Check Event Viewer to see if there are any System or Application errors that happen during startup.
- Check that all service dependencies are set to Automatic. Most likely the only one is AR System Portmapper (if any at all).
- Change the AR Server service startup to Manual, apply, then back to Automatic. If it isn't working, never hurts to toggle it.
- Try changing the AR Server service startup to Automatic (Delayed Start) as a workaround.
- Call the Windows Admins for help!
In this case,
Check with the event viewer and check in armonitor.log, ar exception. Log
and ardebug.log for more details.
From Windows registry check if the path are proper and if there is any
registry corruption with ar server parameters.
As you mention it starts manually it means the problem is not with the ar
server but with OS.
During startup the server starts from arserver.config under ARSytem folder.
Check with the paths of jars and java.
Most importantly if you run it on command prompt you will get more details
as to y the server is not starting.
Hope above steps will help you to pin point and find out the problem.