Help Center

Follow

Is your deployment state stuck in QUEUED or PENDING?

There are a couple of reasons why this might be happening.  One of the more common reasons is that your Background Service is not running.   Check the status bar at the bottom of your PDQ Deploy screen for any notifications.   If this is the case, then you will see “! Service is not running”.

 svcNotRunning.png

 In order to process all deployments and schedules, PDQ Deploy uses a Windows service named PDQDeploy.  The quickest and easiest fix is to check your preferences settings.  Under File > Preferences > Background Service, check the status.  If it says “Service is not running” simply click the button below that says “Start Deploy Service”. 

 preferences.png 

If only SOME of your deployments are stuck in

“Queued” or “Pending”, you might be maxing out

 your “Concurrent Targets per Deployment”.  Under File > Preferences > Performance you can see

what your console is set to.  The default settings are 8 Concurrent Targets per Deployment, and 32 Total Concurrent Targets, in Pro mode you can customize these numbers to fit your needs.  The server will push deployments according to these limits, which could explain why some of your deployments are running fine while others seem to be stuck.

 Performance.png

 

Hope this helps, and happy PDQing!

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

9 Comments

  • 0

    As I click "Start Deploy Service"  I got the following answer..

    "The PDQ deploy service failed to start without an error code"

    complete result in Screenshot...

  • 0

    Sohail,

    Can you look in your application event log for any errors related to the PDQ Deploy service?  

  • 0

    Diagnostic Details :

     

    CLR Version : 4.0.30319.1

    Comments :

    E-Mail : ahmad.sohail@ufonegsm.net

    Error : The PDQDeploy service failed to start without an error code, check the event log for possible reasons

    Error Type : AdminArsenal.AppFramework.BackgroundServiceException

    License Mode : Free

    Memory : 4 GB (2 GB free)

    Product : PDQ Deploy

    Subject : PDQ Deploy Diagnose Report

    Version : 2.0.1.0

    Windows : Microsoft Windows 7 Enterprise (6.1.7600.0)

    The PDQDeploy service failed to start without an error code, check the event log for possible reasons

    Service Name: PDQDeploy

    AdminArsenal.AppFramework.BackgroundServiceException

    ------- INNER ERROR -------

    The PDQDeploy service failed to start without an error code, check the event log for possible reasons

    Service Name: PDQDeploy

    AdminArsenal.Foundation.ServiceFailedToStartException

    at AdminArsenal.Foundation.ServiceManager.Start(String name, TimeSpan timeout)

    at AdminArsenal.AppFramework.BackgroundService.DoStart()

  • 0

    Sohail,

    Look in your Application event log using eventvwr.exe.  There should be some messages from PDQ Inventory in there with some more information.

  • 0

    from event log:

    |
     
    |  
    |  
    | Access to the path 'C:\ProgramData\Admin Arsenal\PDQ Deploy\Database.db.329bea43-0fc6-4a9d-9730-36709b0b0443' is denied. System.UnauthorizedAccessException at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.StreamWriter.CreateFile(String path, Boolean append) at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize) at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding) at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding) at System.IO.File.WriteAllText(String path, String contents) at AdminArsenal.PDQDeploy.Server.VerifyWriteAccessToDatabaseDirectory() at AdminArsenal.PDQDeploy.Server.MainMethod()
    |

  • 0

    Thank you.  It appears that the background service user account doesn't have rights to access the database file or directory.  The best solution is to make sure that the user for the background service is a member of the local Administrators group.  

  • 0

    Service is Up now...

    Thankx Adam

  • 0

    I have 1 computer that is stuck in Queded status.

    I can go and run another deployment, to other machines, while this is still in the queded mode.

    I have restarted this machine, and nothing else is being deployed to this machine.

  • 0

    @robert, be sure to check you DNS if its pointing to the right machine and that there is only one entry.

Article is closed for comments.
Powered by Zendesk