- This topic has 10 replies, 2 voices, and was last updated 3 years, 3 months ago by .
-
Posts
-
Hello,
Many thanks for your great tool but…
All my application deployments no longer works. All tasks remain in “Deployment: XXX queued…”.
All other functions work.
If I deploy a bat file with the copy file function, it works.The deployment worked great before.
What could be the cause ?
Thanks
It’s hard for me to guess at what could be going on. I would suggest you start by rebooting the BatchPatch computer. Then try performing the deployment on just a single row and see what happens.
It’s very unlikely that a setting would be the cause of this issue. However, you can certainly test it and see what happens. The easiest way would be to just launch BP under a different user account since all of the BP settings are saved on a per-user basis. Launching it under a new user account would be equivalent to wiping your own account’s settings, but without having to deal with actually doing that. However, if you want to wipe your account’s settings, you can do that too by closing all instances of BP (also uninstall the service instance first if you have that installed – check ‘Tools > Settings > Run As Service’), and then delete registry key HKCU\Software\BatchPatch and C:\users\yourUsername\AppData\Local\Cocobolo_Software,_LLC If you have saved commands/deployments/queues/etc that you don’t want to lose, then you should export them first (Tools > Export), and you should consider backing up the two locations noted above before deleting them.
We have never heard of a situation where a deployment is queued even when there are no other deployments active. Frankly, I can’t even imagine how that could happen. It simply doesn’t make sense. Normally the only thing that can/would cause deployments to queue is if the max number of concurrent threads or max number of copy jobs are already reached (these settings are under ‘Tools > Settings > General > Concurrent Thread Max’ and ‘Tools > Settings > General > Concurrent File-Copy Operations Max’). However, you describe that it’s happening even after a reboot and after executing the deployment for just a single row, so your issue wouldn’t be caused by reaching the maximum threads or copy jobs.
The only other thing that I can think of that you should try before you do any of the stuff noted above is to try a brand new grid (don’t use a saved grid, in case somehow the grid file itself got corrupted), and to create a brand new deployment (don’t use a saved deployment, in case somehow that’s where the issue is).
You said all tasks remain in “Deployment: XXX queued…”
Is this definitely the exact message you see? If yes, then I don’t think it would be an issue with the target machines. It’s almost definitely *just* on the BP machine.
If the above-message is not the exact message that you see, then what is the exact message?
Also, you said everything else works. Can you confirm what happens when you use “Check for available updates” ?
‘Actions > Windows Updates > Check for available updates’ not ‘Help > Check for updates’
I’m not sure what could be causing that aside from everything I mentioned previously. Did you try the suggestions that were posted further up above? And to create brand new everything from scratch, including brand new deployment configuration, brand new grid, etc, along with everything else suggested in the posting I made a few days ago.
- You must be logged in to reply to this topic.