In my case the install had somehow dropped in 32-bit Java, which caused the service not to start. Support was able to extract the 64-bit Java and reinitialize with RunOnce to get it to work, in case anyone else has a similar issue!
↧