Hi All, Rocketman and Pete
I finally have this problem sorted! It turns out to be a port problem all along!! Port 9000 to be exact. There was no obvious indication as to this being the problem so thanks Pete for your help, I wouldn’t have realised the problem without setting up services and the other steps as above.
I had created rules, prior to installation, to unblock all ports required for awareim using inbound/outbound rules in Firewall in Windows Server Manager.
It wasn’t until starting aware as a service and trying to log into the operation mode and configuration mode that I realised I also had to create a "Connection Security Rule" in Windows Server Manager specifically for port 9000. - The instant I done this everything worked as it should. I don’t need to run as services any more and it all starts perfectly in the conventional way. Having said that, I quite like the idea of aware starting as a service and I think I’m going to stick with it now.
So now I am running on my new server with MySQL and I am a very happy man. Unfortunately my old vps setup was with Derby so I am just about to start on that mission - import and export of my operational data.
Are you using MySQL? had a problem a while ago where jboss/tomcat/aware tried to start before MySQL was ready.
I re-installed aware with both MySQL and Derby but my problems were the same in either instance.
.... PS, using 1&1 VPS - so will be very interested to know how you got on as I was thinking of upgrading
I, until now, have been using a 1&1 VPS since reading your recommendation (
