Jump to content

Recommended Posts

Posted (edited)

We have a few schools where SOLUS3 is failing to update itself and it rolls back. If I run the MSI's manually on these servers, I can upgrade the database, service and UI without issues, then redeploy the SOLUS3.5 update via SOLUS3 to get the agents up to date.

 

The servers with issues at first glance appear to have UAC enabled. Anyone had issues with SOLUS3 updating itself with UAC left on? Also, what permissions does SOLUS3 need to update itself? presumably it's done as the SYSTEM account so that needs full write permissions to specific SOLUS3 related areas?

 

The failures also seem to be the Database upgrade stage.

Edited by Rawns
Posted
Did you run the s3 hotfix for discovery delviery? I remember seeing something about this in the release notes about solus 3.5?

 

All our sites had this update as soon as it was released back in may(?). Also if you try to upgrade SOLUS3 to 3.5 without applying this hotfix first, it bricks your SOLUS3 database and you have to restore a backup.

Posted
I see, I remember I had problems with installing Solus 3.5 I had an error message on the left hand side before I was to deploy the upgrade something complaining about version number not matching. I called Capita and they made a small change to the database then I was able to deploy the upgrade. It is worth asking Capita to remote in?
Posted
Fair enough, do you look after SIMS for a number of schools then?

 

Yes, I'm part of the LA support unit. 270+ sites.

Posted (edited)
Who needs SOLUS3? Just ran the updated MSI's via CentraStage against a server with self-upgrade issues and it's upgraded them with no problems. Just need to get the updated agent out there. Edited by Rawns

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...