[sims] Solus broke since july server updates

[browolf]

Solus3 stopped working since july server update which is unfortunate since we just got the summer 21 update which is not downloading or deploying.

 

All the clients haven't been seen since and the solus deployment application system log has no entries since the time the server reboot for the updates.

 

All the agents have the error "could not connect to net.tcp://sql:52965"

 

The firewall is still off on the server.

 

It feels like there should be a service to start or something but there's not a "solus deployment server" service.

 

Any ideas?

[ajp233]

SOLUS3.12.59.5 will be released by close of business on Friday 21st May 2021. Details about the change can be found below.

 

What is the current situation?

Following on from the change to the new SOLUS3 Package Server URL a few weeks ago, we would like to inform you of another required change that forms part of the separation from Capita. There is a URL change we need to implement, this time it is part of a minor update to the SOLUS3 application. To ensure that schools continue to receive updates to their SIMS systems via SOLUS3 we advise that the following activities take place in the following order:

 

Approve the following URL for access via your internet filtering systems:

Service (the old URL was Service)

Once your firewalls have been updated, you are then advised to update SOLUS3 to version 3.12.59.5 which should be available by close of business 21st May 2021. Please keep an eye on updates to this article for a specific release date.

 

When will I need to make the change by?

The new URL is live and available now, this means that as soon as the update to SOLUS3 is released, as long as users have added the new URL to their white list, SOLUS3 will continue to work as normal. The old URL will remain in service until the end of August 2021. Customers therefore have a four month window to ensure that internet filtering systems are updated with the new URL and the update to SOLUS3 can be applied. The update to SOLUS3 will update the SOLUS3 service including each SOLUS3 Agent defined in the deployment environment.

 

What is the impact for users of SOLUS3?

The downloading of patches and updates via SOLUS3 may fail if the new URLs are not approved for access via internet filtering systems and the update to SOLUS3 not implemented. We are therefore recommending that customers add the new URLs Service to their whitelist before updating SOLUS3.

 

You can find further information regarding SOLUS3 URLs within the following knowledge article KB0023674.

[Boredguy]

The Deployment service uninstalling after updating to 312.50 is a known bug, and your SIMS support should have made you aware of it when they told you 3.12.59 was out (as that updates the Update URL to be EES and not Capita)

 

Basically extract the Solus 3 Deployment update from the Admin panel and re-run the Server Solus3DeploymentServiceInstaller and it should resolve the issue.

Our Support company had a EXE version of the file available to download from their site, along with the instructions.

[browolf]

Apparently it's "proper broke" and it's been referred to capita to fix.

[Boredguy]

Solus is never proper broken, if all the agents were purple, but you can access the Admin console on the server, it's just the deployment service that went hiding.

 

Worst case it's just running the setup file again to repair it.