ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Failed to download package: Cannot set bit range, invalid DynamicBitset range

book

Article ID: 173040

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

After upgrading  to ITMS 8.5, a lot of packages in a package server were in pending state and those packages were downloading very slowly (or did not download at all. Staying in Pending state). 

The package server had all packages in Ready state before the upgrade.

After updating the agent configuration and refreshing all packages, the count of ready packages increases but very slowly until stopping downloading at all (in spite of all packages were previously downloaded and ready).

If a package is selected in the package server tab in "Pending" state and  "Force Download" was used, it will run the package check and set to Ready right away.

It was found that packages stopped downloading on the package server as soon as error "Cannot set bit range, DynamicBitset is not created" appeared in the agent log.

Entry 1:
Error loading log (0x80070002)
-----------------------------------------------------------------------------------------------------
Date: 11/15/2018 4:32:38 PM, Tick Count: 1634485445 (18.22:01:25.4450000), Size: 284 B
Process: AeXNSAgent.exe (12148), Thread ID: 25788, Module: AeXPackageDelivery.dll
Priority: 2, Source: AeXPackage::get_Log

Entry 2:
PostPkgSvrPackageEvent failed: Unknown error
-----------------------------------------------------------------------------------------------------
Date: 11/15/2018 4:32:38 PM, Tick Count: 1634485461 (18.22:01:25.4610000), Size: 291 B
Process: AeXNSAgent.exe (12148), Thread ID: 25788, Module: AeXNSCPackageServer.dll
Priority: 8, Source: AeXNSPkgSvr

Entry 3:
GetUpdateList called for package: '{21AEE375-FA71-45ED-8CB3-E2D1550FAAC0}' (skip hashing)
-----------------------------------------------------------------------------------------------------
Date: 11/15/2018 4:32:38 PM, Tick Count: 1634485461 (18.22:01:25.4610000), Size: 332 B
Process: AeXNSAgent.exe (12148), Thread ID: 25788, Module: AeXPackageDelivery.dll
Priority: 8, Source: Snapshot

Entry 4:
Cannot set bit range, invalid DynamicBitset range (0xE06D7363)
-----------------------------------------------------------------------------------------------------
Date: 11/15/2018 4:32:38 PM, Tick Count: 1634485477 (18.22:01:25.4770000), Size: 336 B
Process: AeXNSAgent.exe (12148), Thread ID: 25788, Module: AeXPackageDelivery.dll
Priority: 2, Source: AeXPackageDelivery::raw_DownloadPackage

Entry 5:
CAeXNSCPkgSvr::UpdatePackage failed. Cannot set bit range, invalid DynamicBitset range.
-----------------------------------------------------------------------------------------------------
Date: 11/15/2018 4:32:38 PM, Tick Count: 1634485492 (18.22:01:25.4920000), Size: 343 B
Process: AeXNSAgent.exe (12148), Thread ID: 25788, Module: AeXNSCPackageServer.dll
Priority: 1, Source: Package Server Agent

Cause

The issue is related to legacy snapshot.xml stored for certain packages on a Package Server without ability for it to be redownloaded.

Environment

Problem occurred after upgrading from ITMS 8.0 HF6 to 8.5.

Resolution

This issue has been reported to the Symantec Development team. A fix is scheduled to be released with ITMS 8.5 RU1.

A pointfix is available for customers with ITMS 8.5 under TECH251651 "ITMS 8.5 POST-GA Cumulative Fixes"

Meanwhile, there is a workaround that can be used if the issue is only with one or few packages:                

  • Delete snapshot.xml from Package Delivery folder on the affected package server for the package associated to the this error. Review agent logs to find the affected package.
  • Restart Agent Service
  • If there are more similar packages detected ( packages which causes bit range exception) , identify package using trace log and repeat above steps.

    Note: sometimes you will need to clear our all the packagestatus.xmls for all packages on the affected package server if you are not sure which one was causing the issue:
    • Clear (delete) all the PS status xml files located at “C:\Program Files\Altiris\Altiris Agent\Package Server Agent\PackageStatus”  on package server,
    • Restart the Symantec Management Agent service.