Is your deployment state stuck in QUEUED or PENDING?

Follow

Comments

9 comments

  • Sohail Ahmed

    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
    Comment actions Permalink
  • Adam Ruth

    Sohail,

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

    0
    Comment actions Permalink
  • Sohail Ahmed

    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
    Comment actions Permalink
  • Adam Ruth

    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
    Comment actions Permalink
  • Sohail Ahmed

    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
    Comment actions Permalink
  • Adam Ruth

    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
    Comment actions Permalink
  • Sohail Ahmed

    Service is Up now...

    Thankx Adam

    0
    Comment actions Permalink
  • Bliss, Robert - HPL

    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
    Comment actions Permalink
  • SelfMan

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

    0
    Comment actions Permalink

Article is closed for comments.