Adobe Experience Manager 6.5 Latest Service Pack Release Notes

Last update: 2024-02-23

Release information

Product Adobe Experience Manager 6.5
Type Service Pack release
Date Thursday, February 22, 2024
Download URL Software Distribution

What is included in Experience Manager

Experience Manager includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements that have been released since the initial availability of 6.5 in April 2019. Install this service pack on Experience Manager 6.5.

Key features and enhancements

Some of the key features and enhancements in this release include the following:

  • Dynamic Media now supports lossless HEIC image format for Apple iOS/iPadOS. See fmt in the Dynamic Media Image Serving and Rendering API.

  • Multisite Manager (MSM) now supports Experience Fragment structures including folders and subfolders, for efficient bulk rollout of Experience Fragments to Live Copies.

Fixed issues in Service Pack 20


Admin User Interface

  • The Workflow Title field is marked with * as required, but there is no validation. (SITES-16491)

Content Fragments

  • Nested configuration folders were no longer supported and content fragment model folders were no longer visible after upgrading to AEM 6.5.18 or to AEM 6.5.19. (SITES-18110)
  • Some subfolders are not able to pick from inherited content fragment models. It must support folders without having a jcr:content property, even if the DAM folders created by way of the user interface have such a node. (SITES-17943)

Content Fragments - GraphQL API

  • When executing a GraphQL query to filter results using optional variables, if a specific value is not provided for the optional variable, then the variable is ignored in the filter evaluation. (SITES-17051)

Content Fragments - REST API

  • With the upgrade of the org.json library, there was a change in how decimal numbers were deserialized. Before they were converted “by default” into Doubles and now into BigDecimals. Instead, the metadata property values, stored by way of the REST API, should get converted to Double from BigDecimal. (SITES-16857)

Core Backend

  • When Quick Publish of a Content Fragment is used, it continues loading and does not get published. That is, Quick Publish is not working for Content Fragments after a service pack upgrade from AEM 6.5.7 to AEM 6.5.17. When the user tried managed publish, it worked. However, when they tried Quick Publish, it was not getting published. Specifically, caused the system to thrash. (SITES-17311)
  • Content fragments are not serializable with Jackson exporter: The page load breaks when there is a content fragment referred to in a page (uses Jackson exporter code) and any tag added to a content fragment. (SITES-18096)

Core Components

  • Installing CIF Core Components package on AEM causes :type value of existing components to change. The change means that they no longer render on pages that they have been added to. (SITES-17601)

Campaign integration

  • AEM was using an allowlist–also known as a whitelist–due to a vulnerability report. The allowlist was preventing customers from using needed functionality. (SITES-16822)

Experience Fragments

  • MSM for Experience Fragments now supports bulk-rollout to Experience Fragment content structures including folders and subfolders. (SITES-16004)

MSM - Live Copies

  • An “Is not modifiable” exception is thrown when rolling out component. Specifically, an exception is experienced during response processing. (SITES-18809)
  • Unable to roll out changes to specific Live Copies of Experience Fragments. (SITES-17930)
  • When a user adds an annotation to a component on a blueprint page, and then rolls it out, the annotation count on Live Copy is displayed incorrectly. (SITES-17099)
  • The MSM Rollout button from parent page to child page is broken in the touch graphical user interface; when selected the following error is displayed: Uncaught TypeError: _g.shared is undefined. (SITES-16991)

Page Editor

  • Forms Theme Editor preview is broken. When Preview is selected, only a loading icon is visible. (SITES-17164)


  • Unable to validate rule-based fields in metadata editor helper and displays an error message “Missing required fields”. (ASSETS-31396)
  • After a PDF is moved to another location, the View Page option disappears. (ASSETS-30538)
  • Unable to select an image with read permissions. (ASSETS-32199)
  • Unable to change card size in view settings. (ASSETS-31667)
  • Upload fails while uploading .oft file type. (ASSETS-30109)
  • When you try to add a custom metadata field as an additional column to the report, the checkboxes are not selected. (ASSETS-31671)
  • Asset move operation does not work appropriately in Experience Manager Service Pack 16. (ASSETS-30598)

Dynamic Media

  • When an asset is uploaded to AEM, the Update_asset workflow is triggered. However, the workflow never finishes. The workflow only completes up to the product upload step. The next step is the Scene7 batch upload, but that process is not getting pulled into AEM. (ASSETS-30443)
  • Need a better way to handle non-Dynamic Media videos gracefully in the Dynamic Media component. This issue was giving an exception instantiating dynamicmedia_sly.js. (ASSETS-31301)
  • Preview works for all assets, adaptive video sets, and videos. However, it throws a 403 error for .m3u8 files (which, incidentally, still work by way of public links). (ASSETS-31882)
  • The scene7SmartCropProcessingStatus status corrected. Smart Crop video metadata used to show failure even when it was successful. (ASSETS-31255)


Fixes in Experience Manager Forms are delivered through a separate add-on package one week after the scheduled Experience Manager Service Pack release date. In this case, the AEM Forms add-on package release is scheduled for Thursday, February 29, 2024. A list of Forms fixes and enhancements is added to this section post the release.



  • User sync diagnostics fail after successfully configuring user sync. (NPR-41693)


  • Remove all code and dependencies of Adobe Search&Promote from AEM 6.5. (NPR-40856)


  • Aria-label “close” is not localized in Assets > Files, select a folder, then on the toolbar, select Properties > Permissions tab > member name. (NPR-41705)
  • There is a truncated tooltip for the Key Store Password field on the SSL Setup page for locales ENG, FRA, KOR, DEU, and PTB. (NPR-41367)


  • Issue with integrating Campaign with AEM caused by the /api servlet not returning the correct scheme in the href json. The reason was because AEM was not receiving the X-Forward-Proto header which forced the request to respond with an HTTP scheme instead of HTTPS. As such, the ability to toggle scheme selection based on an OSGI configuration should be added. (GRANITE-48454)


  • The bundle 1.4.2 throws an exception from AEM 6.5, Service Pack 17 and later. The Sling resource merger 1.4.4 should be included in Service Pack 20. (NPR-41630)


  • Following deployment of AEM 6.5 Service Pack 18, there was an issue with the Filters tab in the Translation Rules Editor. When a Context is selected, clicking Edit > Save, a double-quote as HTML character appears the next time you open the same Context. Essentially, translation rules were not getting saved correctly. (NPR-41624)
  • Issues related to Content Fragment translations, where the translated strings are being sent back from the translation provider to AEM, but they are stuck at the /content/projects level and not updating the Content Fragments. (NPR-41516)
  • An error message is displayed when creating a language copy. It occurs on a page that has a content fragment referenced in a page property, using content fragment models. (NPR-41441)
  • Links in Experience Fragments are not adjusted to the correct language during Language Copy. Instead, the Experience Fragment points to the primary locale. (NPR-41343)

User interface

  • Console error is experienced after an upgrade to AEM 6.5, Service Pack 18. The error is in the coralUI3.js file and it occurs when you select any drop-down in AEM. Specifically, it happens with an onOverlayToggle event. The error Uncaught TypeError: Cannot read properties of null (reading 'innerText') is displayed. (NPR-41467)
  • In AEM, Tools > General > Tagging > Create > Create Tag, entering non-latin characters in the Title field causes the Name field to be filled with just the hyphen character ( - ). (NPR-41623)
  • Copyright year is incorrect in the About Adobe Experience Manager dialog box. (NPR-41526)
  • There are untranslated Profile Properties strings when editing user settings. Occurs in all locales. (NPR-41365)

Install Experience Manager

  • Experience Manager requires Experience Manager 6.5. See upgrade documentation for detailed instructions.
  • The service pack download is available on Adobe Software Distribution.
  • On a deployment with MongoDB and multiple instances, install Experience Manager on one of the Author instances using the Package Manager.

Adobe does not recommend that you remove or uninstall the Experience Manager package. As such, before you install the pack, you should create a backup of the crx-repository in case you must roll it back.

Install the service pack on Experience Manager 6.5

  1. Restart the instance before installation if the instance is in update mode (when the instance was updated from an earlier version). Adobe recommends a restart if the current uptime for an instance is high.

  2. Before installing, take a snapshot or a fresh backup of your Experience Manager instance.

  3. Download the service pack from Software Distribution.

  4. Open Package Manager, then select Upload Package to upload the package. To know more, see Package Manager.

  5. Select the package, then select Install.

  6. To update the S3 connector, stop the instance after installation of the Service Pack, replace the existing connector with a new binary file provided in the install folder, and restart the instance. See Amazon S3 Data Store.


Dialog on Package Manager UI sometimes exits during the installation of the service pack. Adobe recommends that you wait for error logs to stabilize before accessing the deployment. Wait for the specific logs related to the uninstall of the updater bundle before being assured that the installation is successful. Typically, this issue occurs in the Safari browser but can intermittently occur on any browser.

Automatic installation

There are two different methods that you can use to automatically install Experience Manager

  • Place the package into ../crx-quickstart/install folder when the server is available online. The package is automatically installed.
  • Use the HTTP API from Package Manager. Use cmd=install&recursive=true so that the nested packages are installed.

Experience Manager does not support Bootstrap installation.

Validate the installation

To know the platforms that are certified to work with this release, see the technical requirements.

  1. The product information page (/system/console/productinfo) displays the updated version string Adobe Experience Manager ( under Installed Products.

  2. All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console: /system/console/bundles).

  3. The OSGi bundle org.apache.jackrabbit.oak-core is version 1.22.18 or later (Use Web Console: /system/console/bundles).

Install Service Pack for Experience Manager Forms

For instructions to install the service pack on Experience Manager Forms, see Experience Manager Forms Service Pack installation instructions.


The Adaptive Forms feature, available in AEM 6.5 QuickStart, is designed for exploration and evaluation purposes only. For production use, it is essential to obtain a valid license for AEM Forms, as Adaptive Forms functionality requires proper licensing.

Install GraphQL Index Package for Experience Manager Content Fragments

Customers using GraphQL must install the Experience Manager Content Fragment with GraphQL Index Package 1.1.1.

Doing so lets you add the required index definition based on the features they actually use.

Failure to install this package may result in slow or failed GraphQL queries.


Only install this package once per instance; it does not need to be reinstalled with every Service Pack.


The UberJar for Experience Manager is available in the Maven Central repository.

To use UberJar in a Maven project, see how to use UberJar and include the following dependency in your project POM:


UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository ( The main UberJar file is renamed to uber-jar-<version>.jar. So, there is no classifier, with apis as the value, for the dependency tag.

Deprecated and removed features

See Deprecated and removed features.

Known issues

  • Related to Oak
    From Service Pack 13 and above, the following error log has begun to appear which affects the persistence cache:

    org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.0.202/5]
    at org.h2.mvstore.DataUtils.newMVStoreException(
        at org.h2.mvstore.MVStore.getUnsupportedWriteFormatException(
        at org.h2.mvstore.MVStore.readStoreHeader(
        at org.h2.mvstore.MVStore.<init>(
        at org.h2.mvstore.MVStore$
        at org.h2.mvstore.db.Store.<init>(


    org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.1.214/5].

    To resolve this exception, do the following:

    1. Delete the following two folders from crx-quickstart/repository/

      • cache
      • diff-cache
    2. Install the Service Pack, or restart Experience Manager as a Cloud Service.
      New folders of cache and diff-cache are automatically created and you no longer experience an exception related to mvstore in the error.log.

  • Update your GraphQL queries that may have used a custom API name for your content model to use the default name of the content model instead.

  • A GraphQL query may use the damAssetLucene index instead of the fragments index. This action might result in GraphQL queries that fail, or take a long time to run.

    To correct the problem, damAssetLucene has to be configured to include the following two properties under /indexRules/dam:Asset/properties:

    • contentFragment
      • jcr:primaryType="nt:unstructured"
      • name="jcr:content/contentFragment"
      • propertyIndex="{Boolean}true"
      • type="Boolean"
    • model
      • jcr:primaryType="nt:unstructured"
      • name="jcr:content/data/cq:model"
      • ordered="{Boolean}true"
      • propertyIndex="{Boolean}true"
      • type="String"

    After the index definition is changed, a reindexing is required (reindex = true).

    After these steps, the GraphQL queries should perform faster.

  • When trying to move, delete, or publish either Content Fragments, Sites, or Pages, there is an issue when Content Fragment references are fetched, as the background query fails. That is, the functionality does not work.
    To ensure correct operation, you must add the following properties to the index definition node /oak:index/damAssetLucene (no reindexing is required):

    "tags": [
    "refresh": true
  • If you upgrade your Experience Manager instance from 6.5.0 - 6.5.4 to the latest service pack on Java™ 11, you see RRD4JReporter exceptions in the error.log file. To stop the exceptions, restart your instance of Experience Manager.

  • Users can rename a folder in a hierarchy in Assets and publish a nested folder to Brand Portal. However, the title of the folder is not updated in Brand Portal until the root folder is republished.

  • The following errors and warning messages may be displayed during installation of Experience Manager 6.5.x.x:

    • "When the Adobe Target integration is configured in Experience Manager using the Target Standard API (IMS authentication), then exporting Experience Fragments to Target results in wrong offer types getting created. Instead of type “Experience Fragment”/source “Adobe Experience Manager,” Target creates several offers with type “HTML”/source “Adobe Target Classic.”
    • com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
    • Adaptive Form server-side validation fails when aggregate functions such as SUM, MAX, and MIN are used (CQ-4274424).
    • com.adobe.granite.maintenance.impl.TaskScheduler - No maintenance windows found at granite/operations/maintenance.
    • The hotspot in a Dynamic Media interactive image is not visible when previewing the asset through the Shoppable Banner viewer.
    • bundle (395)[] : Timeout waiting for register change to complete unregistered.
  • Starting with AEM 6.5.15, the Rhino JavaScript Engine provided by the org.apache.servicemix.bundles.rhino bundle has a new hoisting behavior. Scripts that use the strict mode (use strict;) have to correctly declare their variables, otherwise they do not get run, instead throwing a runtime error.

Known issues for AEM Forms

Known issues in Experience Manager Forms are delivered through a separate add-on package one week after the scheduled Experience Manager Service Pack release date. In this case, the AEM Forms add-on package release is scheduled for Thursday, February 29, 2024. A list of known issues for forms is added to this section post the release.

OSGi bundles and content packages included

The following text documents list the OSGi bundles and Content Packages included in this Experience Manager 6.5 Service Pack release:

Restricted websites

These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.

On this page