Since installing Continua, I've only rebooted my server twice. In both instances now, Continua hasn't worked until I've restarted the 'Continua UI Application Service'. There is a Windows application log information message from 'ContinuaCI' that reads the following:
Service started successfully.
However when attempting to access Continua from a browser it just spins its wheels on a blank page (I haven't gone trawling IIS logs yet). Before I've manually restarted the service, this error shows up in the Windows application log for every repository I've got:
Repository @link(2002, bfae3b4c-83c5-4b10-ba45-33547552d837)[Phoenix6] cannot be initialised: Value cannot be null. Parameter name: path1
The source for the errors is identified as 'Continua'.
Is it possible I've missed a configuration step somewhere? We're running Continua 64bit on Windows 2008 R2, with Postgres as installed by the Continua installer. All our repos are Mercurial sourced over https.
I’ve finally tracked this one down… ContinuaCI Service has a dependency on the Windows Management Instrumentation service. The easiest way to do this, is to wait for the next build we release and install it. Then follow these steps:
Stop the ContinuaCI Service. Either from the Services UI or running net stop ContinuaCI on the command line.
Open up a command prompt at the ContinuaCI Server install location, default is: C:\Program Files\VSoft Technologies\ContinuaCI\Server
Run the command Continua.Server.Service.exe -uninstall
Run the command Continua.Server.Service.exe -install -user=<domain\username> -password=<your_password></your_password></domain\username>
Start the ContinuaCI Service. Either from the Services UI or runningnet start ContinuaCI on the command line.