PDQ Deployment stuck on Connecting status

Comments

12 comments

  • Shane Corellian

    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.

    1
    Comment actions Permalink
  • Umut Demiriz

    Hey Shane,

    Thanks for your quick reply. It worked! :-) But only after I restarted the deployment machine.

    Cheers,
    Umut

    0
    Comment actions Permalink
  • Shane Corellian

    Thanks for getting back to us. I modified my statement to have you stop the Background Service. Doing this should prevent you from having to restart the console computer.

    0
    Comment actions Permalink
  • Umut Demiriz

    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?

    0
    Comment actions Permalink
  • Shane Corellian

    What version of PDQ Deploy are you using? What are your Offline Settings (Preferences > Deployments). Are the computers (that are stuck in the Connecting state) powered on? Are you using Wake-on-LAN?

    0
    Comment actions Permalink
  • Umut Demiriz

    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.

     

     

    0
    Comment actions Permalink
  • Umut Demiriz

    I took the offline setting out and there are still some computers where the "Connecting" is stuck. The computers which are stuck are online (Tested through pinging)

    0
    Comment actions Permalink
  • Shane Corellian

    Thanks, Umut. We are going to try and duplicate the issue in our lab.

    0
    Comment actions Permalink
  • Shane Corellian

    Umut, some issues were recently fixed that may very well solve this problem. They will be available in PDQ Deploy 5. It is in a public beta right now.

    0
    Comment actions Permalink
  • David Cunningham

    I am experiencing this issue also.  The clients are directaccess connected workstations.  I can ping all of them.  Currently only 1 workstation (shown below) out of 6 has reconnected after a reboot.

     

    0
    Comment actions Permalink
  • Colby Bouma

    Do they get the same IP address when they come back up?

    0
    Comment actions Permalink
  • David Cunningham

    Yes - also since they are connecting via DirectAccess they are IPv6 (although I don't believe that is the issue).  I am able to abort and simply perform the 3 step in another package (but that defeats the purpose of automating it).

     

    0
    Comment actions Permalink

Please sign in to leave a comment.