PDQ Deployment stuck on Connecting status
Hi PDQ community,
We are using PDQ very frequently and none of my colleagues ever had this problem.
PDQ gets stuck on Connecting while deploying and then I have to manually abort the deployment, which is a very time consuming work around with over thousands of clients. It's not on every computer but only every 50-100 computers.
I tried to resolve this problem with disabling the Service Manager TCP connection, but it didn't help.
Thank you for your support.
-
This problem can pop up every now and then. It is fairly rare and "the perfect storm" of certain events need to happen to cause it especially in later versions of PDQ Deploy.
The easiest thing to do is to clear out those computers that are stuck in a Connecting state. Go to File > Preferences > Database. Open your SQLite Console. Type in the following command (dont forget the semicolon):
delete from DeploymentComputers where Stage = 'Connecting';
Then go to the Background Service panel (in Preferences) and stop the Background Service. After doing this go ahead and close and reopen the PDQ Deploy console. The Background Service will then start automatically (when the console is started). This should take care of the problem.
-
Thanks for the great support you guys are offering, some other big companies could learn a lot from you guys!
There is still an issue coming up though with the status stuck on connecting again after a while.
I think if there was an option that if a status like Connecting lasts longer then 30 minutes it should let the deployment fail it would be great to get around this problem. Is there already a way to configure this? Or would this be a feature request? -
PDQ Version: 4.2.0.0 Release 2 Enterprise Mode
Offline settings: http://imgur.com/NFU2lZ3
I think I see the problem now...it's the 72h setting.
Please sign in to leave a comment.
Comments
12 comments