Documentation

Bundles stuck in installed state after AEM Service Pack 22 upgrade

Last update: Thu Apr 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

After upgrading Adobe Experience Manager (AEM) to Service Pack (SP) 22, some bundles remain in the installed state and fail to start. To resolve this, install a compatible Screens Feature Pack.

Description description

Environment

Product: Adobe Experience Manager (AEM) On-Premise, v6.5

Issue/Symptoms

  • After upgrading AEM from Service Pack 19 to Service Pack 22, the following bundles fail to start:

    • ContentFragmentManagement - HTTP API

      • Symbolic Name: com.adobe.dam.cq-dam-cfm-haf
      • Version: 1.0.14

    • Adobe Granite RESTful API Assets

      • Symbolic Name:com.adobe.granite.rest.assets
      • Version: 1.0.58.CQ650-B0003

  • Attempts to manually activate these bundles result in errors, and they remain unavailable.

Resolution resolution

To resolve the issue, follow these steps:

  1. Install Screens Feature Pack FP11.5, which is compatible with AEM Service Pack 22. This feature pack addresses compatibility issues introduced by earlier versions of Screens Feature Packs (for example, FP11, FP11.3, FP11.4) when used with SP21 or SP22.
  2. Navigate to the OSGi console and confirm that both com.adobe.dam.cq-dam-cfm-haf and com.adobe.granite.rest.assets are in the active  state.
  3. Test the functionality provided by these bundles to ensure proper operation post-upgrade.

You should now have compatibility between AEM Service Pack 22 and feature packs, restoring the full functionality of impacted bundles. If issues like blank screens or dashboard errors occur after installing Screens FP11.5, investigate logs or error messages for further troubleshooting.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f