[sims] Solus 3 on Server 2012

[synaesthesia]

Ok, this is driving me a little mad. How can anyone expect last minute changes to work, especially in large schools?

For instance, why let SIMS work on Server 2012 but not Solus3? What's the operational difference? (Guessing next to none).

Not too bad for a primary but when you need to look at getting rid of a 2003 server, noone's going to be looking at installing 2008R2 as a stopgap just so S3 works. Don't fancy waiting until the last minute in Summer for the Summer update (if it comes out in time!) to swap to a new SIMS 2012 server!

 

Strange and annoying.

[Ghostgame]

I don't think they have said that it does not work. just that it is not supported yet.

Everything is supported on Windows Server 2012 OS now that the Spring update is out.

 

Its just that for SQL 2012 Discover, SOLUS3, etc is not suppported till Summer.

 

So you could have a new SIMS Server 2012 but with SQL 2008R2 installed. When the summer update comes out, upgrade to SQL 2012.

 

Resource number for technical roadmap: 17910

Edited May 31, 2013 by Ghostgame

[Rawns]

I thought SOLUS3 was supported on Windows Server 2012, but not Microsoft SQL Server 2012? Or are you on about SQL 2012?

[Ghostgame]

I hate Microsoft.

Imagine this conversation down a phone - me and the customer both ended up confused.

 

Have a Windows 2012 Server OS but have SQL 2008R2 installed.

[Rawns]

Go NUUUUUUUUUUUUUUUUTTTTTSSSSSSSS!!!!!!!!!!!!!!!!!!!!

 

Install Windows Server 2012, attach SIMS and FMS to a SQL2012 instance and then attach SOLUS3 and Discover to a SQL2008R2 instance!!!!

 

Confused much?

Edited May 31, 2013 by Rawns

[Rawns]

For the record, we have two schools running Windows Server 2012 and SOLUS3. No issues experienced at all.

[Ghostgame]

Install Windows Server 2012, attach SIMS and FMS to a SQL2012 instance and then attach SOLUS3 and Discover to a SQL2008R2 instance!!!!

 

Confused much?

 

Haha, would have made things much easier for me to explain.

 

Don't like the idea of two instances.

Feels like there is more chance for things to go wrong

Would still do it if it was requested.

[Rawns]

Would still do it if it was requested.

 

Well, don't do it! The Discover transfer does not work between a SIMS database on SQL2012 and a Discover database on SQL2008.

 

Just wait until the Spring release and migrate them all to SQL2012, then get rid of the old 2008 instance.

[Ghostgame]

Thats the plan

[synaesthesia]

For the record, we have two schools running Windows Server 2012 and SOLUS3. No issues experienced at all.

 

How? Couldn't get it to install full stop. "This operating system is not supported" with some random numbers, even trying to install in compatibility mode. Capita just shrugged shoulders and told me it's not supported.

[Rawns]

How? Couldn't get it to install full stop. "This operating system is not supported" with some random numbers, even trying to install in compatibility mode. Capita just shrugged shoulders and told me it's not supported.

 

Was that a new Solus 3 install? The two schools we have running it on Server 2012 had Solus 3 installed on old 2008 servers and we migrated it across to their new 2012 server. The database was just detached and attached on the new 2012 server, but the Solus 3 service and UI were installed using the normal installers, no erros, no issues. It just worked.

[synaesthesia]

Brand new install with existing SIMS data. (migration from 2003 to 2012. 2003 had solus 3.5) Refused point blank to install.

Never mind, I'll do it in the summer anyway, but need to think about doing it for my main site (damn slight more at risk there though!) Must get cracking on my testbed.

[MrMat]

Brand new install with existing SIMS data. (migration from 2003 to 2012. 2003 had solus 3.5) Refused point blank to install.

Never mind, I'll do it in the summer anyway, but need to think about doing it for my main site (damn slight more at risk there though!) Must get cracking on my testbed.

 

Sorry to bump an old thread but I just wanted to add that we are having the same trouble as Synaesthesia.

 

New server running 2012. Brand new install of Solus 3. The thing completely refuses to install, we don't even get to chance to configure anything. Run the EXE and pow "This operating system is not supported".

Logged a call with Capita who responded with:

 

'This is expected...We are very optimistic that this will be supported in the 3.6 release'

 

[Rawns]

Sorry to bump an old thread but I just wanted to add that we are having the same trouble as Synaesthesia.

 

New server running 2012. Brand new install of Solus 3. The thing completely refuses to install, we don't even get to chance to configure anything. Run the EXE and pow "This operating system is not supported".

Logged a call with Capita who responded with:

 

'This is expected...We are very optimistic that this will be supported in the 3.6 release'

 

@synaesthesia @MrMat

 

Just thought of how it's installing from me but no one else!

 

Are you running it with the exe? I remembered that I install it using the MSI files that have been extracted from the EXE as we install via a script using CentraStage. Maybe something in the EXE checks the O/S and throws a wobbly. You should be able to open the exe in 7-zip and extract the MSI files to install it successfully on Server 2012:

 

SSCERuntime-ENU.msi

SSCERuntime-ENU-x64.msi

SOLUS3DeploymentServerDatabaseInstaller.msi

SOLUS3DeploymentServiceInstaller_x64.msi

SOLUS3DeploymentServiceInstaller_x86.msi

SOLUS3DeploymentServerUIInstaller_x64.msi

SOLUS3DeploymentServerUIInstaller_x86.msi

 

On SupportNet, Phil Neil says 3.6 is expected to be release COB on August 9th.

Edited July 30, 2013 by Rawns

[synaesthesia]

Seems to fail at first hurdle, no MSI in Solus3DeploymentServerDatabase., just a few files and folder (.rsrc, .data .rdata .text and CERTIFICATE). There's MSI's in the rest of the exe's though.

 

 

***

 

Scratch that, found it in one of the cabinet files.

 

 

***

 

Bugger. "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected."

Edited July 30, 2013 by synaesthesia

[MrMat]

Hmmmm at what point did you get that message?

 

I've managed to extract all the MSI files. I havent tried installing yet but they all seem to load up alright on the Server.

 

Have you had any issues specifically with these 2012 servers Rawns?

[synaesthesia]

I suspect mine may be due to SQL2012.

That new message is at the end of the install process for the deployment server database setup.

[Rawns]

Hmmmm at what point did you get that message?

 

I've managed to extract all the MSI files. I havent tried installing yet but they all seem to load up alright on the Server.

 

Have you had any issues specifically with these 2012 servers Rawns?

 

No issues at all with installing and using SOLUS3 on a Windows 2012 server. We are still using SQL 2008 on all of them though as 2012 is not supported yet and I don't think the SOLUS3 database installer will work if you try to install a new SOLUS3 database on a 2012 instance (that's what I found with the Spring Discover database installer when trying to install it to SQL2012 in our test environment).

Edited July 30, 2013 by Rawns

[Rawns]

I suspect mine may be due to SQL2012.

That new message is at the end of the install process for the deployment server database setup.

 

Sounds like it. The same thing happens if you try to install a SIMS Spring Discover database against a 2012 instance.

[synaesthesia]

Our Discover (Summer) is working on SQL 2012 thankfully. Will hold on for 3.6, although frankly it's not the end of the world for us if solus 3 never works

[MrMat]

Ahh excellent. Cheers guys.

 

We're using SQL 2008 as well so hopefully it should work okay. Will try installing later today and see how we get on (not going to do it now, only 'officially' been in this role since Friday so will wait for the boss to return and run it past him before I try installing anything on the shiny new server haha )

[Rawns]

Ahh excellent. Cheers guys.

 

We're using SQL 2008 as well so hopefully it should work okay. Will try installing later today and see how we get on (not going to do it now, only 'officially' been in this role since Friday so will wait for the boss to return and run it past him before I try installing anything on the shiny new server haha )

 

Good stuff, let us know how you get on.

[mtillbrook]

Hmm, just been reading through all these posts.

 

I have tried running the MSI's and I get the error saying its not supported by the operating system.

 

Strangly people are talking about extracting the MSIs from the EXE? The download for Solus3 3.5.20 that i've got from Capita just has the MSI's and no sign of an EXE. Am I missing something?

I am trying this version of Solus 3 with SQL 2008R2 as I wasn't brave enough to try SQL2012 but still running on Server 2012.

 

Any help would be appriciated - in other words, please don't make me ring Capita in the morning?!!

 

Cheers

[synaesthesia]

Just wait. 3.6 is being released, with SQL and Server 2012 support, next Wednesday.

 

Or if you must - use 7zip to extract the download EXEs and the msi's are contained therein. One of them you have to go digging into the .cab files to find the MSI's but they are there.

[MrMat]

Quick heads up for anyone that missed it.

 

Posted today on SupportNet:

 

'Solus 3.6 release date now 16th August

 

Due to the recent issues with the hosted SOLUS3 servers we have made the decision to change the release date of SOLUS3.6 to Friday the 16th of August.'