Rawns Posted December 13, 2012 Posted December 13, 2012 We're having issues with some SOLUS3 sites here. Schools are unable to access SIMS after the upgrade went out as the upgrade has a status of "rollback in progress" and is stuck there doing nothing!!! I've never seen come across this before and am unsure what to try first. Anyone come across this and have any pointers?
Ghostgame Posted December 13, 2012 Posted December 13, 2012 hmm. I have had some schools where it has rolled back but has still updated the database somehow (even though that's where it failed on). Have you been able to redeploy even though the "rollback in progress" status is still on?
Rawns Posted December 13, 2012 Author Posted December 13, 2012 Thanks, it appears to be just this. Looking at the upgrade table in Management Studio, it appears to be on the latest release. Had to kill off the Deployment service and restart it which caused the "queued" updates to start applying. I'm redeploying the Autumn upgrade now but it seems to be taking ages just to apply the Spring 11 DB upgrade!!!
Rawns Posted December 13, 2012 Author Posted December 13, 2012 Great! Looks like it's gone through this time! DB, SQL and FIle server upgraded. Just waiting on the workstations!
bossman Posted December 21, 2012 Posted December 21, 2012 @Rawns: Had the same thing happen to me today, after deploying the Autumn 2012 upgrade via Solus 3 it took 2 and a half hours then decided to rollback, the error was that the tolerance factor hadn't been met and therefore rollback initialised. Went back through the agent log and it has other upgrades in process and then has the message failed, everything seems to have rolled back but I didn't try to re-deploy as it was our last day and everyone had gone home at 1:00pm and I wasn't going to stay any longer. Anyone else had this happen with the same error "database tolerance not met" Wouldn't mind but the Discover database and client update went very smoothly without a hitch. Very strange as it also wanted to upgrade every database from spring last year which I think is a bug and is going to be rectified next February so I am led to believe.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now