[sims] Solus breaks with latest Workstation Patch

[FragglePete]

Implemented the latest Workstation Patch last night - and then today we found we couldn't deploy SIMS via SOLUS3 anymore!

 

I've raised a call and they've acknowledged that there is an issue that a lot of other schools are having the same issue.

 

You'll get the following error when clicking the Check for Updates button on the SOLUS3 notifier.

 

"Selected package has no expected target versions assigned to it, cannot deploy"

 

SOLUS itself deploys with no issues, just won't do SIMS Workstation.

 

 

Pete

[DrBeaker]

Implemented the latest Workstation Patch last night - and then today we found we couldn't deploy SIMS via SOLUS3 anymore!

 

I've raised a call and they've acknowledged that there is an issue that a lot of other schools are having the same issue.

 

You'll get the following error when clicking the Check for Updates button on the SOLUS3 notifier.

 

"Selected package has no expected target versions assigned to it, cannot deploy"

 

SOLUS itself deploys with no issues, just won't do SIMS Workstation.

 

 

Pete

 

F A N T A S T I C.

 

Nice one there Capita. Thanks for the heads-up though

[SpaceInvader83]

Implemented the latest Workstation Patch last night - and then today we found we couldn't deploy SIMS via SOLUS3 anymore!

 

I've raised a call and they've acknowledged that there is an issue that a lot of other schools are having the same issue.

 

You'll get the following error when clicking the Check for Updates button on the SOLUS3 notifier.

 

"Selected package has no expected target versions assigned to it, cannot deploy"

 

SOLUS itself deploys with no issues, just won't do SIMS Workstation.

 

 

Pete

This patch rolled out last night for us so probably have this to contend with Monday, on the bright side we are hopefully sacking Sims off this academic , can't say I'll miss anything about it!

[Tefters]

Ow how I love Capita... Was due to look at this today as I clocked the issue on Thursday last week but hadn't found the time to properly investigate the root cause, I should of guessed it wasn't anything from my side really...

 

Edited September 28, 2020 by Tefters

[MrWu]

Thanks for the heads up, well, just have to do the workaround and copy the whole SIMS folder from working machine onto the one with the issue to let it run for now

[paulkerton]

And this is yet another reason to move to a cloud MIS!

[tech-man]

Does anyone have any fixes for this?

[ALittleFish]

This might explain one of the issues I was having recently with a school.

 

My work around was to re-deploy the SIMS Summer Full release to the new/re-built workstations once they had been added into Solus3.

[Arthur]

Relevant KB article:

 

https://support.capitasoftware.com/csm?id=kb_article_view&sysparm_article=KB0041334

[Arthur]

KB0041483 - Unable to log into SIMS after Consolidated Workstation Patch 1 was applied between 27th and the morning of 30th September

 

What is the issue?

If a school has applied the census Consolidated Workstation Patch 1 between Monday 28th September and the morning of Wednesday 30th September, after the patch has been applied to the workstation, upon trying to log into SIMS they experience an application crash.

 

Who is impacted?

Only those schools who downloaded and applied the patch via SOLUS3 in the timeframe mentioned above are impacted.

 

What is the cause of this issue?

The version of the patch that was applied updated the required files to fix the defined census problem, but also regressed three specific files in the SIMS .net folder back to Spring 2020. Users attempting to log into SIMS will experience an application crash due to a mis-match in files, hence the un-successful launch of SIMS.

 

What is the resolution to this?

By using the SOLUS3 agent on the impacted workstations, the user can force a re-install of an updated version of this patch, which will also re-install the Summer 2020 versions of those files regressed back to Spring 2020.

 

Continues...

[fiza]

Anyone having problems with Cover since the Census patch was applied?

[Jaan]

I'm getting the below error when trying to install sims via solus now. The agent and discover install fine.

 

Not sure if its the update that has caused this, or if its something else i need to do. Never had this before.

 

 

[Dirthat]

I'm getting the below error when trying to install sims via solus now. The agent and discover install fine.

 

Not sure if its the update that has caused this, or if its something else i need to do. Never had this before.

 

 

[ATTACH=CONFIG]59286[/ATTACH]

Have you tried deleting the PC from Solus3 and then redeploying? I had a similar error before with the "agent target id" bit and that seemed to solve it.

[Jaan]

Have you tried deleting the PC from Solus3 and then redeploying? I had a similar error before with the "agent target id" bit and that seemed to solve it.

 

yes i have. I've also noted this affects all my machines..... be each has a different agent id number. Must be centrally from the server.

[Benjaminbl12]

Hi all,

 

I installed the latest Census patch from the 1/10/2020 which was a database patch. I was told on their article that this should resolve this issue but I'm getting the same message pop up with the version on the clients solus as 0.0.0.0

 

Do I need to remove the target fully from Solus as well?

[Jaan]

Hi all,

 

I installed the latest Census patch from the 1/10/2020 which was a database patch. I was told on their article that this should resolve this issue but I'm getting the same message pop up with the version on the clients solus as 0.0.0.0

 

Do I need to remove the target fully from Solus as well?

 

i've removed the machine from solus here, made no difference

[Benjaminbl12]

Refer to this: https://support.capitasoftware.com/csm?id=kb_article_view&sys_kb_id=79c77d6a1b6bd094676cdb12cd4bcbc5

 

Re-download the patch from the 30th and redeploy to the users that didn't work. Ask your data team/officer first though as they might still be working on a Census and it might cause conflicts if you do a mass deploy! Learnt that ALMOST the hard way… Thank god for SQL backups!

[MrWu]

Bar copying the SIMS program folder to bodge new PC builds to run sims, has capita advised a permanent fix?

 

PCs including ones with SIMs installed, pops up with "Selected package has no expected target versions assigned to it, cannot deploy" when update button is pressed and showing version 0.0.0.0 for all, support company seemed to think it’s a firewall issue ...

 

I could try the redeploy workstation fix later today posted here

[Tefters]

Bar copying the SIMS program folder to bodge new PC builds to run sims, has capita advised a permanent fix?

 

PCs including ones with SIMs installed, pops up with "Selected package has no expected target versions assigned to it, cannot deploy" when update button is pressed and showing version 0.0.0.0 for all, support company seemed to think it’s a firewall issue ...

 

I could try the redeploy workstation fix later today posted here

 

No updates as of yet, workaround is still as you described above.

[Jaan]

I've "cloned" sims from one PC to another..... however it doesn't seem to be very stable, not sure if that's just bad luck

 

I've submitted a number of support requests via our support channels...... it's all very quiet!

[chazzy2501]

This is unbelievably stupid. I have to redeploy SIMS (patch whatever) to over a 100 workstations so I can install SIMS onto 2 new laptops... FFS and next week when I have 6 more depoly again to 102 workstations?

 

Does the old Simsinst still work

[Jaan]

I've been in contact with our support channel here...... i'll keep you all posted if we end up with a fix.

 

We started to have an issue after applying the latest workstation patch.

 

since then we can't deploy sims, Solus agent and discover deploy and work fine. Sims doesn't.

 

This is the error we get when asking solus to check for updates against the workstation:

 

 

tried all the standard stuff,removing sims, removing from solus removing and reinstalling the agent blah blah.

Edited October 8, 2020 by Jaan

[smarties11]

I cannot download consolidated workstation patch 1 - gives me a 'download failed' error and a 404 error when I click it in SOLUS.

 

A colleague in another School kindly sent me it over e-mail, so I could manually extract it just for the census workstation - and McAfee Threat Prevention 10.7.0.1751 detects the pulsar.exe file as a 'potentially unwanted program'. I expect it's a false positive. Could this be related though - is it triggering some AV systems and hence the issues?

[Tefters]

This is unbelievably stupid. I have to redeploy SIMS (patch whatever) to over a 100 workstations so I can install SIMS onto 2 new laptops... FFS and next week when I have 6 more depoly again to 102 workstations?

 

Does the old Simsinst still work

Yes.

 

To clarify, the issue is that the Solus Agent will install on a client pc but not Sims.

 

My simple workaround is:

 

1. Deploy Solus to new machine as normal from Sims server by assigning it Sims. Solus agent will install but Sims will not.

 

2. Copy the Sims install folder from the Solus server extraction share to the client machine.

 

3. Run SimsApplicationSetup.exe from the folder for an old school install experience.

 

4. Delete the Sims install folder copied from the server to the client.

 

5. Kick back and sip your coffee while laughing at how Capita can fcuk things up more and more everday.

 

6. Await patch to fix issue and know you have Solus on the client machine just incase the patch can be deployed somehow but don't hold your breathe.

[TomoL]

Yes.

 

To clarify, the issue is that the Solus Agent will install on a client pc but not Sims.

 

My simple workaround is:

 

1. Deploy Solus to new machine as normal from Sims server by assigning it Sims. Solus agent will install but Sims will not.

 

2. Copy the Sims install folder from the Solus server extraction share to the client machine.

 

3. Run SimsApplicationSetup.exe from the folder for an old school install experience.

 

4. Delete the Sims install folder copied from the server to the client.

 

5. Kick back and sip your coffee while laughing at how Capita can fcuk things up more and more everday.

 

6. Await patch to fix issue and know you have Solus on the client machine just incase the patch can be deployed somehow but don't hold your breathe.

 

 

What version of the Solus agent are you able to push out to your workstations?