[sims] SOLUS3: Another depolyment is currently in progress. Current status: idle

[tech-man]

Hello,

 

I have a computer which is stuck installing SIMS.net - I was installing it using SOLUS earlier and I suspect someone turned it off.

 

The message in SOLUS3 is: Another depolyment is currently in progress. Current status: idle

 

I have tried uninstalling the agent, selecting the re-deploy option & rebooting the PC - none of these help.

 

Does anyone have any ideas?

 

Thanks

[matt40k]

You should of just left it, it would have timed out. I think if you click the check agent status that would have also done it. I think restarting the S3 service on the server would solve it. It's got a job stuck in the queue I guess.

[tech-man]

No joy i'm afriad.... I'll log a call with my helpdesk

[Rawns]

Sounds like you added a device to the SIMS Workstation channel? SOLUS3 automatically installs/upgrades SIMS once it's added. I'm guessing you set off a manual deployment at the same time as the auto deploy was going.

 

I've suffered this once or twice before. In most cases, stopping all SOLUS3 services on the server for 30+ mins seems to do the job, however in most cases, the deployment job will always show as "in progress" even though it has stopped/timed out. Other times, it made no difference so a reboot of the server was actioned. This also fixed it.

[tech-man]

This got logged with Capita and this was their suggestion which worked.

If this message is being displayed for one agent on your network and is not the agent local to the server, then all you need to do is go on to the machine by question and go to the following directory:

C:\ProgramData\Capita\SOLUS3 or C:\Documents&Settings\All Users\Application data\Capita\SOLUS3

When in this directory, rename the deployments folder to deployments.old

Now redeploy to this workstation and this should go through ok

[robjduk]

I had this a couple of times. I had to get the people who do our support to remote in and remove the entry from the SQL. From now on I only install 5 manually at a time.

[Rawns]

Cheers @tech-man, just experienced this at a site of ours and renaming the deployment folder did the job.

[Kaz77]

I've also had this problem. Phoned Capita, helpdesk person said they'd never seen the problem before so they were passing it to technical. Still awaiting a reply. @tech-man's fix worked for me, had to start the laptop in safe mode to rename the folder.

 

Thanks @tech-man

Edited January 14, 2014 by Kaz77

[robjduk]

I can fix that now and happens to us from time to time. I include the fix if your up for doing it.

 

Open your SQL and sign in

Open your SIMS SQL

-Databases

-solus3_deployment_server

open a new query and enter the following...

 

update solus3.agent

set agent_status = 16

where agent_status = 8

 

Obviously best to wait for Capita to play as its SQL and could be something else but thought it may speed up the fix process for someone.

Enjoy

[matt40k]

If it is Install Active that it's locked on - this tool will do the same thing as @robjduk mentioned without going into SQL Managment Studio - http://www.edugeek.net/forums/mis-systems/124621-solus3-reset-install-active-agents-utility-matt40k.html

[Kaz77]

Thanks for the information.

 

I have solved the problem with @tech-man's fix, renaming the deployments folder, as it was only on one laptop.

 

I'm still waiting for Capita, rather than cancelling the call, just to see how long they are going to take to reply.

Edited January 14, 2014 by Kaz77

[Kaz77]

Just noticed @matt40ks comment. I did try the reset utility but that showed a smiley face so that didn't seem to be the issue Edited January 14, 2014 by Kaz77

[matt40k]

Just to check @Kaz77, you just downloaded it? I only ask as I only added in the support for Install queued in the latest version (it also has the version number at the bottom). I'm not surprised, as you've said, @tech-man advise worked so it sounds like you two had a slightly different error.

 

PS: Weird the helpdesk didn't know what it was, surely that would be a Capita KB article - maybe the helpdesk person didn't have the KB search zen today

[Kaz77]

Yes, I downloaded it yesterday. I have subsequently used your app for another laptop where the Solus3 agent install got stuck at Active. Thanks

[Rawns]

You should go into freelance SOLUS3 support @matt40k! You'd make a KILLING, and you can bet there would be guaranteed work for you for the next couple of years!

[matt40k]

Haha, I'm sure you're right, but there is only 1 way that is ever going to happen!

[kennysarmy]

This got logged with Capita and this was their suggestion which worked.

If this message is being displayed for one agent on your network and is not the agent local to the server, then all you need to do is go on to the machine by question and go to the following directory:

C:\ProgramData\Capita\SOLUS3 or C:\Documents&Settings\All Users\Application data\Capita\SOLUS3

When in this directory, rename the deployments folder to deployments.old

Now redeploy to this workstation and this should go through ok

 

and that fix still works

[Rawns]

and that fix still works

 

Shame Capita have not fixed the cause of this in the past 5 years!!!

[kennysarmy]

Shame Capita have not fixed the cause of this in the past 5 years!!!

 

Give them time...

[TwistedHelixis]

Out of interest did you try restarting the Solus deployment service running on the server, whenever I have the issue you mention, I just restart the service and click re deploy.

[kennysarmy]

Out of interest did you try restarting the Solus deployment service running on the server, whenever I have the issue you mention, I just restart the service and click re deploy.

 

No, I did n't - I'll give that a try when the issue returns at the next major update.