AD on 2012 Server [Server A]. (Continua Service User created; Continua Admin Group created).
SQL 2012 on 2012 Server [Server B] (continua database located here with AD Continua Service user as DBO role)
IIS 8 on 2012 Server [Server C - DMZ] (continua service loaded here).
VS 2012 [Developers PC] (agent(s) can probably go here to help ensure there isn't too much software, for security reasons, on IIS DMZ Servers).
Basically I'm just following MS recommended practice for various server configuration and I've got a stack of firewalls between all these services (yay). I try and install the latest edition of Continua and find the installation dialog boxes/options include a stack more information about the security model and options available (thanks!). I think you guys might already be aware that non Administrator roles and an integrated Continua Server has some further work before a lower security model can be used with the software.
I uninstalled the previous Continua Installation.
I installed v1.0.0.1382.
I made a typo mistake for one of the passwords.
post installation I fixed the service password issue.
Ensured all services were started and running.
Ensure there were no warning in the event log against continua.
Went to the web site and got the familiar error.
If you are an administrator, please connect to the Windows server JDSRV*** and
Ensure that the Continua Server service is running
Check the Event Log for any application errors for Continua
Not sure what I can do now, because I don't have further information on what is causing the service to fail.
This would suggest that the web front end (asp.net mvc) cannot connect to the server service using WCF. Try stopping the service, and then run it from the command prompt with -console
Continua.Server.Service.exe -console
See what errors that throws up on the console. I suspect there may be some cases where the service is erroring and not stopping when it should. My first guess would the service is not connecting to the database.
We’ll be spinning up some server 2012 vm’s this week to do testing with non admin accounts etc.
If you have a firewall enabled on the sql server machine, make sure you open a port (1433 from memory) so that the webserver/continua server can connect to it. On the webserver, you will also need to open ports to allow agents to connect to it, and on the agents you will need to open a port so the continua server can connect to them.
I spun up a server 2012 vm, created a non admin user to run the service under, and installed Continua, and I see the same thing. I enabled the udp logger and discovered the issue is the service is unable to determine the local path of the share. This is very strange, since we try 3 different methods, wmi api, wmic command line tool and the net share command. What is even more strange, is if I log in as that user I can at least use the wmic method. we’ll investigate this… I rember we had a beta tester a while back who had similar issues.
as a work around, open Continua.Server.exe.config in notepad (run as administrator first) and add this line under appsettings
Vincent. The error you have with Shares, sounds like a Service Pack installing in the background style issue to me. While the Windows 8 codebase is much better, I just wonder how far down the SP auto update you got.
Of course, running when I run PS > cmd > Continua.Server.Service.exe -console (I’m implicitly running as Administrator on the server DOH!), then the web site works just great. When I try and run against the non admin service role, it all goes pear shaped.
I think it might be a good idea to have the Continua share path in the *.config file(s), so admin people can go to one place to see all the settings on those things. At least you can put further instructions into the file for security information, like folder permissions etc. I like the idea that any and all configuration is in my *.config files, so I can train any Admin guys to read those documents in notepad.
This might help get around “admin” guys wanting to change a “software devs” configuration of continua, when and if they start moving servers or VM’s around.
Posted By Vincent Parrett on 03 Feb 2013 01:23 AM BTW, the installer doesn't try to change the security on the ContinuaShare folder, you need to make sure your user has write permission on it.
I wonder if this is a good UI experience for Continua. I think post installation should include as little steps as possible for the end users, who may not "Read The Instructions". Oh, lets not forget we are lazy software developers.
I think it might be a good idea to have the Continua share path in the *.config file(s), so admin people can go to one place to see all the settings on those things. At least you can put further instructions into the file for security information, like folder permissions etc. I like the idea that any and all configuration is in my *.config files, so I can train any Admin guys to read those documents in notepad.
This might help get around "admin" guys wanting to change a "software devs" configuration of continua, when and if they start moving servers or VM's around.
It's easy for an adminsitrator to find the local path of a shared folder, it's just not easy to do programatically when in a service running as a non admin user. Hopefully this won't be an issue with the next build, as I seem to have (famous last words) solved this one.
I wonder if this is a good UI experience for Continua. I think post installation should include as little steps as possible for the end users, who may not "Read The Instructions". Oh, lets not forget we are lazy software developers.
I actually added code to the installer to update the permissions earlier today, haven't had chance to test it yet (about to after retrieiving some caffine!).
As usual the Vsoft team are doing all the right things for us Software developers. Thanks Vincent. I think I’ll grab a coffee as well! BTW Superbowl was very exciting.