It's SIMPLE by default.
It's SIMPLE by default.
Could be, they don't use RedStor or such do they? I know they need it to be full.
No they don't.
I've just installed a brand new SOLUS3 3.4.103 instance on another school server and immediately checked the database in Management Studio. It's in full recovery mode too so the database must be installed and put into full by default.
the compatibility level is also set to SQL2005 (90). Not sure if this should be SQL2008 (100)?
Is your app available for configuring SOLUS 3? Just about to the upgrade to Autumn for the census and not used SOLUS 3 successfully yet!
@Rawns - been told it uses the default. If it's SQL standard, they'll get a maintainance task.
@skunk - should be somewhere on the web, will dig out a link. All it does it give you a text file with the settings you need to put in SOLUS3 when your setting it up for the first time. Nothing really special, just stuff like my proxy is this, my SQL binn is that...
Rolling out agents now, a few at a time, successfully. looks like Autumn Update will have to be Bing Bang test as you cannot deploy except to everyPC.
And My Log is FULL MODE installed by SIMS last summer. Though they did set SIMS DBS to Full too and I have since changed that.
wish me luck!!
Haha yer, that domain thing got a few people, firewall is a pain. Good luck anyway. Don't forget to backup your SOLUS3 database now as well :)
We've spent the last few days in the process of uninstalling SOLUS3 agents in order to get the Autumn release pushed out. Apparently there is a problem with the latest SOLUS3 release in that some machines do not automatically update if they are offline and then get turned on at a later date. If the SOLUS2 update method still worked then this wouldn't be too bad but, if the SOLUS3 agent is installed on a pc, it stops the SOLUS2 method of updating.
Removing the SOLUS3 agent is the best way get things back up and running again quickly - if only the agent didn't have to be manually uninstalled from each workstation in order to do this. (There is a remove agent button in SOLUS3 but apparently this was broken with the last update as well - yay for testing.)
Ok, since Capita support are being their usual helpful selves and cannot return my call, any ideas what to do when the SOLUS 3 upgrade sticks on 'in progress' after upgrading 60% of the SIMS Workstations? Cancel deployment is greyed out, have tried restarting the services and rebooting the server. It hasn't updated the deployment log file since last night.
Just try to redeploy the update, or push it out again, to the workstations that haven't received it yet.
Upgraded SOLUS3 to latest version 3.4.103 yesterday..................now it won't talk to its database. FFS!
SOLUS2 it is again this time....................
I've also had the issue of the deployment getting stuck 'in progress' and also recently had it apparently fail on a few machines because it's timed out, however when i check the workstation it has upgraded them fine.
Glad its not just me having issue's.