+ Post New Thread
Results 1 to 6 of 6
MIS Systems Thread, SOLUS3 - It is possible that the deployment service has stopped in Technical; I tested the use of SOLUS3 for upgrades for the Summer release of SIMS .net with 3 schools. All upgraded ...
  1. #1

    Join Date
    Mar 2012
    Posts
    18
    Thank Post
    3
    Thanked 6 Times in 4 Posts
    Rep Power
    6

    SOLUS3 - It is possible that the deployment service has stopped

    I tested the use of SOLUS3 for upgrades for the Summer release of SIMS .net with 3 schools. All upgraded fine. Tested them again for Autumn. Again all fine. Upgraded Discover on these schools. All fine.
    Then I got excited, and set up a deployment plan covering 28 schools for the Autumn release of SIMS. Exciting. And guess what happened? Failed and rollback. That's ok, I can redeploy. So I did, and it took 8 hours last night to upgrade 24 of those machines. I've set a timeout, which it seemed to ignore.
    The main problem I seem to be facing is the lovely SOLUS3 Deployment Service seems to have stopped error. No it hasn't, it's definitely running. And I've rebooted about a hundred times, and I still get the same error. It spends more time with that error up than not.
    What I'd like to know is - has anyone else had this problem when deploying? Is there anything I should be checking to stop this error coming up?
    To say I've had enough is putting it mildly.
    And don't even get me started on the fact that you can't cancel a deployment once it's verifying the deployment plan, or stuck part way through a deployment but isn't doing anything. That one's been clogging up my system all day.....
    So much for the festive spirit!
    If anyone has any suggestions for what I can try to get rid of this intermittent message I'd be very grateful. I have 80 schools to upgrade by Friday and I don't fancy spending my whole Christmas watching the new blue screen of death.......

  2. #2
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 489 Times in 375 Posts
    Rep Power
    0
    I've seen the message that the service has apparently "stopped" a few times, usually when pushing out a full upgrade. Usually it appears when the deployment server is running at full speed. As far as I can tell, it appears to be a faulty report that makes an appearance when the server is under strain or when SOLUS3 has a large deployment to process. As long as you can see the service is still running on the server, there should be no problems....however as it is SOLUS3, I've come to expect nothing BUT problems!!!

    We've experienced roll-backs too. However, these roll-backs have only been actioned against databases that actually upgraded successfully!!! the deployment service gets itself in a state and stays in a permanent state of rollback preventing any other upgrades going out until you have killed off the SOLUS3 deployment service for 10 minutes! It also tells you to look at the deployment logs which you can't actually do as the button is grayed out during the rollback process!!! Once the service has been restarted, you can push out the same upgrade again and it skips the database as it's already up to date and then upgrades the additional components.

    SOLUS3 truly is a god-aweful piece of software and I loathe it with a passion!

  3. Thanks to Rawns from:

    HannahBuist (18th December 2012)

  4. #3

    Join Date
    Mar 2012
    Posts
    18
    Thank Post
    3
    Thanked 6 Times in 4 Posts
    Rep Power
    6
    Well that's interesting if it is a faulty report - I was hoping that the system taking 8 hours to upgrade was due to there being a lot of 'downtime' with it being stopped, but if it wasn't really stopped and it still took 8 hours for 28 schools? Ouch.
    Thanks for the tip about getting rid of the rollbacks though - that will come in handy to sort out some of my 'stuck' deployments and hopefully tidy up my now very messy deployment history screen!
    I should've known better really - after successfully upgrading 3 schools for both SIMS .net and Discover so quickly I thought this was going to be straightforward. No Christmas miracles here!!

  5. #4
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 489 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by HannahBuist View Post
    Well that's interesting if it is a faulty report - I was hoping that the system taking 8 hours to upgrade was due to there being a lot of 'downtime' with it being stopped, but if it wasn't really stopped and it still took 8 hours for 28 schools? Ouch.
    Thanks for the tip about getting rid of the rollbacks though - that will come in handy to sort out some of my 'stuck' deployments and hopefully tidy up my now very messy deployment history screen!
    I should've known better really - after successfully upgrading 3 schools for both SIMS .net and Discover so quickly I thought this was going to be straightforward. No Christmas miracles here!!
    8 hours for 28 schools?!!! Nasty! Do these schools have their own SOLUS3 deployment environments on site, or do you push it out to them from a LA SOLUS3 Deployment UI?

    Also forgot to mention (but you may already be aware) the fact that the SIMS Autumn upgrade will try and apply every available update from Spring 2011 first! Unless your there to hit the "Deploy now" button constantly, that will add an extra 30-60 minutes on top!

  6. #5

    Join Date
    Mar 2012
    Posts
    18
    Thank Post
    3
    Thanked 6 Times in 4 Posts
    Rep Power
    6
    I push it out from an LA Deployment Service. So I expect it to be slow - but I'm not exactly demanding ridiculous work from it which makes it a bit frustrating.
    Yeah I love how you have to backdate so far.
    At least now I'm on this side of it I know what I'm moaning about and can empathise with others - whereas before I started I just got nervous of it. Now I can get cross about it!

  7. #6

    Sylv3r's Avatar
    Join Date
    Jul 2005
    Location
    Co. Durham
    Posts
    3,206
    Thank Post
    372
    Thanked 377 Times in 335 Posts
    Rep Power
    148
    Ours appear to roll out succesfully on our workstations and server upgrade, but I must admit the 'service has stopped' message did keep appearing for me but never did appear to stop.

SHARE:
+ Post New Thread

Similar Threads

  1. [SIMS] Solus 3 3.4.107.1 upgrade fails on the deployment service part
    By ianswalker in forum MIS Systems
    Replies: 5
    Last Post: 2nd March 2012, 11:55 AM
  2. Replies: 23
    Last Post: 16th November 2011, 12:42 AM
  3. The way it is.
    By Dos_Box in forum General Chat
    Replies: 7
    Last Post: 30th September 2005, 02:09 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •