One or more Endpoints are showing 0% deployment status after upgrade to Managment Server / CCA 8.3

Version 1

    Verified Product Versions

    Management Center 8.3


    After upgrading to Management Server 8.3 and upgrading clients to the 8.3 Client Communications Agent (CCA) via a 3rd party deployment tool, one or more endpoints are not deploying agents/configurations.The computers are polling, but deployment status is 0%.  As a result, no updated Agents or Configurations are deployed to the affected Endpoints.


    After successfully installing/upgrading and polling, specific endpoints are generating an exception when communicating with the Management Server. This is visible in the Management Server Application Event log and/or local CCA Logs.


    Event code: 3005
    Event message: An unhandled exception has occurred.
    Process information:
    Process ID: 8284
    Process name: w3wp.exe
    Exception information:
    Exception type: ArgumentOutOfRangeException
    Exception message: Version's parameters must be greater than or equal to zero.
    Parameter name: build
    CCA Logs show a 500 Error when accessing the manifest.aspx page (accessing the same page via a browser on the endpoint is showing no such errors).


    In order to diagnose if this Article is related to the issue, run the script below against the Management Server SQL database, to check for specific values which are known to cause this exception.

    --The script will not modify the database.

    use [managementserver]
    SELECT M.NetBiosName, MP.*
    FROM [MachinePackages] AS MP
    INNER JOIN [Machines] AS M
    ON M.MachinePK = MP.MachineFK
    WHERE = '-1' and mp.packagekey= '00000000-0000-0000-0000-000000000000'

    If the script returns any rows, this indicates that this issue is present. The netbios names returned in the rows can be cross referenced with the Endpoints listed in the Management Console to ensure that these names match.

    It is possible to repair any endpoints in this state by removing the specific rows from the MachinePackages table. Please contact AppSense Support quoting this Knowledge Article, and we will aide in resolving this issue.