Hi Bart - and any others viewing this post. What appears to be happening is that the aware service - which needs JBOSS an Tomcal to be fully initialised and working- tries to start too soon on slowish servers before JBOSS and/or Tomcat have reached a steady state. A log in the event viewer reveals the following.
"The Aware IM service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service". (this is with the first failure set to "restart the service" in the "Recovery" tag of the Service Properties window - startup set to automatic
One minute later the following entry appears
The Aware IM service entered the running state.
I'm afraid I can't quantify what constitutes a "slow" server. All I can tell you is I don't have a problem on my main working server which has 2 x quad core semperon processors and 2Gb Ram whilst my testing server has a single core 2.6Ghz Pentium processor with 4Gb Ram (from circa 2004)
Trust me ... setting "On first failure - restart the service" will do the trick (leave the "restart after" set to 1 minute"
Let me know how you get on Bart