Jump to content

Recommended Posts

Posted

Hi,

 

Anyone come across this one before?

 

Deploy an agent in SOLUS (3.7), client pops up saying "installing in 2 minutes...", then 10 seconds after the 2 minutes is up (or you hit deploy now), the client says "No updates pending" and the SOLUS agent screen has the above status message.

 

Peter

Posted (edited)

I'd probably give Capita a ring about it, however if you want to try something:

 

Firstly I'd try redeploying the update and see if that works. If not, go to Manage Updates and try downloading the update again and then redeploy after that.

 

We had something similar once (Not on 3.7, I think it was either 3.5 or 3.6), however our error message was the downloaded file size didn't match the expected size for some reason.

Edited by Cache
  • 1 year later...
Posted
Hi,

 

Anyone come across this one before?

 

Deploy an agent in SOLUS (3.7), client pops up saying "installing in 2 minutes...", then 10 seconds after the 2 minutes is up (or you hit deploy now), the client says "No updates pending" and the SOLUS agent screen has the above status message.

 

Peter

 

Sorry to start up a really old thread, but I am having the same problem at one of our schools. "Decompiling of the package SIMS Spring 2016 Full Release (7.168.50) (SIMS Workstation) failed" I am waiting for Capita to get back to me, but don't know how long they will be, in the meantime, can anyone help?

Posted
I seem to recall it was something daft like disk space on the server or the clients?

 

Peter

 

Hi Peter,

 

Thanks for the reply, there seems to be enough disk space, firewalls appear to be off... still waiting on Capita!

Posted

Try uninstalling the S3 Agent (on the client computer from control panel), then remove it from the Servers SOLUS 3 GUI.

Reboot the client machine and restart both the Servers S3 Services.

Now re-install the agent to the client and try again.

 

Like Peter said there needs to be plenty of disk space on both devices.

Posted

Hi

So Capita replied, the server had rebooted whilst downloading the upgrade files via Solus, so the pkg became corrupt.

 

Once the corrupt package was identified and deleted on the server and on the local workstations, I redone loaded the update and it worked.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...