With the Events Dispatcher Service disabled, newly uploaded packages will be stuck at "Pending Install"

Version 1

    Verified Product Versions

    AppSense Management Center 8.7AppSense Management Center 8.6AppSense Management Center 10.0AppSense Management Center 10.1

    Introduction

     

    If the "AppSense Events Dispatcher" service is stopped on your Management Server(s), any new packages you upload will be stuck with an Installation Status of "Pending Install", as seen below:

     

     

    Also, if you check the "download" folder on the endpoint where the installation is pending, you may see a "Blank GUID" folder as seen below:

     

    C:\Program Files\AppSense\Management Center\Communications Agent\download\{00000000-0000-0000-0000-000000000000}

     

    Finally, if you review Deployment Agent logs captured on the endpoint (using the Ivanti Support Toolkit), you will see lines similar to the following:

     

    L3 T3668 377220750 [AMCPackageInfo::IsValidInstruction] Failed due to action having invalid properties. ProductCode [{00000000-0000-0000-0000-000000000000}] InstallerPath []
    

     

    Detail

     

    In addition to uploading auditing data to the Management database, the Events Dispatcher Service is also responsible for maintaining a cache of packages on the server in the following location:

     

    C:\Program Files\AppSense\Management Center\Server\Web Site\Deployment\Packages

     

    There are two main points to note in relation to the packages cache:

     

    1. When a package is initially uploaded to the Management Server, it first gets stored on the database, and is then synced back to the package cache by the Events Dispatcher Service.
    2. When packages are assigned to a deployment group, the endpoints use BITS to download the packages from this location, saving unnecessary traffic to the database.

     

    The problem arises when the Events Dispatcher Service is stopped - the package(s) will not be available in the cache and therefore the download cannot take place.

     

    This is expected behaviour, the Events Dispatcher Service is crucial to the functionality of the Management Server, and should always be in a "running" state during normal operation.