RogerCorrigan Posted June 23, 2014 Posted June 23, 2014 Was SOLUS 3.7 released today as (re)planned? The latest thing about it I can see on the news widget on SupportNet is on the 20th about it having a revised release date. I need a link...
robjduk Posted June 23, 2014 Posted June 23, 2014 I can imagine the release notes now... -UI now 10% more cluttered and 20% less responsive. -Fixed bug where SOLUS would deploy to a computer when using correct username and password. -only compatible with x86 systems. 1
minimoo Posted June 27, 2014 Posted June 27, 2014 Well, We updated it the other day. Logged first support case today, and I'm wondering whether to log a second case about fact Sims discover hasn't deployed to workstation after adding target 3 hours ago. The UI is kinda different - whilst there's some improvements, some parts look to be more confusing so far (Given being used to the old system) Has anyone else upgraded so far?
splattthecat Posted June 27, 2014 Posted June 27, 2014 Discover clients don't auto deploy in the same way SIMS and FMS ones do. You need to go into your last Discover upgrade deployment and re-deploy to that machine. This is unchanged from previous releases. 1
minimoo Posted June 27, 2014 Posted June 27, 2014 realised that after my initial post... in any case, sims just pushed out the bug fix realease to 3.7 that simscfc was expecting
MrMat Posted June 30, 2014 Posted June 30, 2014 For those not already aware, Capita have managed to balls things up yet again: SOLUS3.7 An updated version is now available as SOLUS3.7.149.0 An issue has been discovered in the released version of SOLUS3.7 which can cause the Fileserver element of the imminent SIMS 2014 Summer Update to fail. This was not acceptable and needed to be resolved. This has been fixed and we have re-issued SOLUS3.7.149.0 for all directly supported sites and support teams. Customers who have already applied the original SOLUS3.7 release You will need to upgrade to the SOLUS3 release called ‘Solus 3 – 3.7.149.0’ This will update your Deployment Service to 3.7.149.0 and leave the other already upgraded elements as they are. We will be looking to de-authorise this release from SOLUS3 so if you have the 3.7 release scheduled would encourage you to replace this with the 3.7.149.0 update already available. Note: New agents installed from now on will be at the version 3.7.149.0 but they are fundamentally the same as the existing ones versioned at 3.7.147.0. Fortunately for us it's not much of an inconvenience but it does amaze how such a large company can get this stuff wrong time and time again.
PhilNeal Posted June 30, 2014 Posted June 30, 2014 @MrMatt very annoying and embarrassing; sorry. The effect of the error is very minor but I accept that it does knock confidence.
matt40k Posted June 30, 2014 Posted June 30, 2014 Fortunately for us it's not much of an inconvenience but it does amaze how such a large company can get this stuff wrong time and time again. Am I missing something? element of the imminent SIMS 2014 Summer Update to fail. This was not acceptable and needed to be resolved. Sounds like they've resolved it before it was released then... ie they've found a bug whilst they tested it?!? The idea of agile is you build faster and more frequently, it will have more bugs, but they are smaller and they are resolved faster. Can you image how long it took to re-issue 22,000 CDs? Don't want to even think about when they used floppy discs!! The key issue is the timescale from you reporting an issue to it being resolved on your system, it doesn't matter if they do 1 patch or a 100. If that 1 patch takes 3 months to get applied on your system, you'll take those 100 patches that apply in 30secs any day. It looks like from this release on, see below, application fixes that normally require a re-release or you have to way 3-4 months for the next release can be issued like a database patch, but only via SOLUS3. Suddenly SOLUS3 looks a whole lot nicer. the ability to issue application fixes to SIMS workstations. This will help reduce the need to apply whole platform re-releases in the case of a critical fix in the front end being identified in a release.
MrMat Posted June 30, 2014 Posted June 30, 2014 Am I missing something? Sounds like they've resolved it before it was released then... ie they've found a bug whilst they tested it?!? . Maybe I interpreted it incorrectly but my impression is that it isn't just the SIMS Summer release that has a bug but the recent version of SOLUS3 that was released last week does too, hence why an updated version of S3 needs to be deployed. Don't get me wrong, I'm actually quite a fan of S3. We've been using it for sometime and don't have an issue with it. My comment was solely on the fact that we have to re-release S3.7 only a few days after releasing it for the first time and while it isn't a huge inconvenience (although my re-release has just failed for some reason hmmmmm, best investigate!), it simply doesn't instill confidence. In regards to the SIMS Summer Release, I don't have an issue with the Summer Release being postponed. As you say, it's much better that they've spotted the issue early and are hanging back a short while.
matt40k Posted June 30, 2014 Posted June 30, 2014 I think the bug is with how SOLUS3 handles the SIMS release - I guess they didn't get it until the last moment - it's like when you write reports, you get issues cause the data is yucky and the data is yucky because the form validation is quite right but you don't know that the form validation isn't quite right until you write a report to look at the data... and the process can't start until someone enters the data into the system. Bit of chicken and egg. Guess it's time to start looking at auto deploy
MrMat Posted June 30, 2014 Posted June 30, 2014 (edited) Guess it's time to start looking at auto deploy We can't really use auto deploy For starters I have no idea where auto deploy now sits in 3.7... Seriously where is it? lol I can't find it. Mainly however, we have 1 Deployment Service that controls all of our Primary Schools which totals about 66 servers (not my idea, this is how it was set up when I started and as the guy who set it up is claiming his job back in a few months, I didn't feel it was right to redo it all). We manually select about 10 schools to deploy each night over a week or so when the release arrives. With each school there's nearly always one or two machines that don't upgrade correctly (usually due to a teacher trying to log into SIMS!!) which with only 10 or so schools at a time is manageable, however you times those 1 or 2 machines by all 60 odd schools and you have a royal sh**storm of broken machines the morning after which I would not be able to manage. Edited June 30, 2014 by MrMat
matt40k Posted June 30, 2014 Posted June 30, 2014 (edited) Ah... . Luckily the "one ring to rule them all" idea didn't work for us, god bless firewalls - did think about settings n many schools to a day of the week and get them into the habit of updates happening once a week on that set day. Then I moved teams Edited June 30, 2014 by elsiegee40
Cache Posted July 1, 2014 Posted July 1, 2014 (edited) Just spotted this on supportnet: Upgrade issues using SOLUS3.7 An issue has been identified which is causing SOLUS3 to become unusable following an upgrade to the 3.7 release. This issue has been created in previous versions of SOLUS3 where the SOLUS3 system has been moved to a different SQL Instance (for instance to \SQL2012 from \SQL2008). This issue will cause the upgrade to occur on the old SOLUS3 database, rather than the new one and the system will therefore stop functioning due to incompatibility issues. Please avoid deploying SOLUS3.7 if you have made this move. As stated above, this is not an issue with the 3.7 release, however we are looking at options to re-issue SOLUS3.7 ASAP containing a fix to prevent the issue from occurring. Further information will be published shortly. My Solus3 deployment rolled back tonight for some reason, just wondering if it is now related to this since I disposed of all aspects of my old database. Edited July 1, 2014 by Cache
MrMat Posted July 2, 2014 Posted July 2, 2014 Just spotted this on supportnet: My Solus3 deployment rolled back tonight for some reason, just wondering if it is now related to this since I disposed of all aspects of my old database. Failed due to Tolerance not met for target Solus 3 GUI by any chance?
ianriley1986 Posted July 2, 2014 Posted July 2, 2014 Anyone got a screenshot of the latest version or does it look exactly the same?
MrMat Posted July 2, 2014 Posted July 2, 2014 Ta da! As you can see it looks completely different. Overall it's quite an improvement however there are still oddly placed elements etc. 1
Cache Posted July 2, 2014 Posted July 2, 2014 Failed due to Tolerance not met for target Solus 3 GUI by any chance? Mine failed due to Tolerance not met for Solus 3 Database, so it did the .net 4.5 and the Solus 3 agent and then rolled the whole lot back.
Sheridan Posted July 8, 2014 Posted July 8, 2014 Upgraded to 3.7 - Solus is now broken Can't deploy anything - just get In Progress all the time - nothing gets updated, no error gets logged! Trying to work out now how to roll back to the 3.6 version that has worked nicely for ages!
MrMat Posted July 8, 2014 Posted July 8, 2014 Check your deployment history. Is anything still deploying? i.e. is the SOLUS 3.7 still active or does is it complete? I had the issue initially that i couldnt deploy anything etc and it was because the 3.7 had fallen over at some point and was stuck!
Sheridan Posted July 8, 2014 Posted July 8, 2014 The initial 3.7 (with the 3.7.147 client) finished OK - but updating the client to 3.7.149 is stuck 'In Progress' The deployment log just shows it waiting on machines that have no solus client or are offline. Its just ignoring the online ones and seems to be doing nothing else!
MrMat Posted July 8, 2014 Posted July 8, 2014 Sounds like it's fallen over. Check your Deployment Service (view local services > Solus3 Deployment Service) and make sure it's running. If it's not, turn it on! Unless you've changed it, the timeout is 30 mins so unless you desperately need it to deploy SIMS asap, leave it for 30 mins to see what it does. Failing that if it doesn't sort itself out, go back to services and turn off the Deployment Service, wait a minute or so and then turn it back on. This will trip the upgrade over and make it come back as a failure. This sounds like it's a bad thing but it's better than it being stuck in no-mans land.
Sheridan Posted July 8, 2014 Posted July 8, 2014 I'm going to leave it - I can't restart the server until the end of day anyway. The client 3.7.149 deployment seems to consist of .net 4.5, client 3.7.147 and client 3.7.149 so its a triple install.
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