Hello All,

Recently, have noticed package distribution failing on workstations & in all the workstations following error is found in Kdeploy.log

Error: KDeploy is already running. Only one instance may be run at a time.

This error is written in the log every next second. I am using Managed Install to distribute the package. 

Does anyone have any idea what can be the actual cause of this & how this issue can be resolved?

Answer Summary:
KDeploy is already on the workstation, so it cant start new process to deploy managed installs.
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


I recently ran into the same issue during a managed install. What happened in my case was there was a user prompt in the installation caused by a new process running that was not present in my test enviroment. So the managed install kicked off when users weren't logged into their computer and it prompted for them to stop the offending software but of course got no response. The intallation just hung there and log everytime the computer checked in would just say kdeploy is already running.  I tried creating scripts to restart the computer and push it to the label having issues but they wouldn't reboot, I'm guessing because Kdeploy was running and the agent was waiting for that to finish before running the pushed scripts? anyway it was a software installation problem for me. hopefully that can help you track down your problem

I ended up conecting to the machines useing psexec and forcing a reboot that way to "unstick" it

Answered 05/16/2012 by: alsmith
Senior Yellow Belt

Please log in to comment



I have never seen this.  What it sounds like is that the KDeploy process is already running on your machines, so it can't start a new process to deploy other managed installs.  It may be that something you deployed is stuck on the machines still trying to run, so it can't start a new install.  I would contact support directly to take a look.

Answered 05/14/2012 by: philologist
Red Belt

  • You can try restarting the KACE Agent service to see if it clears things, but if it is a deployment getting stuck, you'll eventually just run into it again the next time the deployment causing the problem tries to run.
  • I think restarting the KACE Agent services will resolve the issue but you can also try restarting the machie and then check.
Please log in to comment
Answer this question or Comment on this question for clarity