Adobe Experience Manager 6.5 service pack release notes

Release information

Products Adobe Experience Manager 6.5
Type Service Pack Release
Date March 11, 2021
Download URL Software Distribution

What is included in Adobe Experience Manager

Adobe Experience Manager includes new features, key customer-requested enhancements, and performance, stability, and security improvements, that are released since the availability of 6.5 release in April 2019. The service pack is installed on Adobe Experience Manager 6.5.

The key features and enhancements introduced in Adobe Experience Manager are:

  • When using Connected Assets functionality, you can now view a list of all the Sites pages that use the asset. These references to an asset are available in an asset’s Properties page. This allows administrators, marketers, and librarians a complete view of assets usage, allowing for better tracking, management, and brand consistency.

  • When deleting an asset that is referenced in a web page, Experience Manager displays a warning. You can force delete a referenced asset or check and modify the references that are displayed in the Properties page of the asset. Clicking the references opens the local and remote Sites pages.

  • Sorting the Live Copy pages available for rollout using the Name, Last modified date, and Last rollout date properties.

  • The built-in repository (Apache Jackrabbit Oak) is updated to 1.22.6.

For a complete list of features and enhancements introduced in Experience Manager, see what is new in Adobe Experience Manager 6.5 Service Pack 8.

The following is the list of fixes provided in Experience Manager release.


  • When a page is moved to blueprint, the destination of links is not updated (NPR-35724).
  • Tizen based player fails to authenticate on certain browsers. The issue occurs with browsers that do not support the samesite=none attribute (NPR-35589).
  • An unlocked responsive container does not display allowed components (NPR-35565).
  • When you create a live copy of a newly added page, the language master creates two copies for each domain (NPR-35545).
  • Deadlock in the SCR Component Registry when many threads are blocked due to org.apache.felix.scr.impl.ComponentRegistry timer. As a result, Experience Manager stops responding for an indefinite time (GRANITE-33125,FELIX-6252).
  • When you search a specific asset in the side rail, the result contains some not-searched assets (NPR-35524).
  • When you enable SSL for an Experience Manager instance, the context path is removed (NPR-35477).
  • When you create a list, add some text as the first element, add a table as the second element, and add a list inside the table, the parent list distorts (NPR-35465).
  • When you use different plugins on consecutive list items, an extra
    tag is added to the list items (NPR-35464).
  • When a list is placed between two paragraphs, you cannot add a table to the list (NPR-35356).
  • When you start an AEM instance upgrade from AEM 6.3 to AEM 6.5, the upgrade instance takes longer to start (NPR-35323).
  • When you replicate an AEM asset that includes a bracket (). in the name, the replication fails (GRANITE-27004, NPR-35315).
  • When you add headings to a Rich Text Editor, the paragraph button is disabled (NPR-35256).
  • When you add an item to an existing list, it deletes the succeeding collapsible or toggle list (NPR-35206).
  • When the Rollout page option is selected, a dialog box with all the available live copies appears, and automatic rollout takes place. The live copies of pages are rolled out to all geographies without user action (NPR-35138).
  • When you use the include children option, the Manage Publication option does not list all pages. Only 22 pages are listed (NPR-35086).
  • When a policy is edited, the text component does not retain the policy changes (NPR-35070).
  • When indenting some items in a numbered list, all items keep the same number although numbering should start from 1 for items with the same indentation (CQ-4313011).
  • When minification is enabled, you are not able to edit any page or component. The issues started after installing AEM 6.5 Service Pack 7 (CQ-4311133).
  • Omni search and asset filters return irrelevant or no results (CQ-4312322, NPR-35793).
  • When multiple pages simultaneously access a client library, the HTML library manager fails to load the client library. It leads to the incorrect rendering of pages (NPR-35538).
  • The context path gets removed automatically when you set up an SSL in Experience Manager (NPR-35294).
  • Package manager does not logout users after clicking the Logout option (NPR-35160).


Adobe Experience Manager Assets fixes the following issues and provides the following enhancements.

  • Upon restoring a previous version of an asset, the event DamEvent.Type RESTORED is not triggered in the OSGi console (NPR-35789).
  • IndexWriter.merge causes OutOfMemoryError error as smart tagging functionality creates large /oak:index/lucene and /oak:index/ntBaseLucene indexes (NPR-35651).
  • An error message is displayed when trying to save an Asset Contribution type folder with multibyte characters in the name (NPR-35605).
  • When cascading metadata subtype fields are used, an incorrect ‘Please fill out this field’ error occurs (NPR-35643).
  • When an existing asset is dragged on the Assets user interface and a new version is created, the changes in the metadata are not persistent (NPR-34940).
  • When creating rules in metadata schema editor for a cascading menu, the Dependant On option repeats the same name (NPR-35596).
  • Similarity search does not work after editing Assets Admin Search Rail (NPR-35588).
  • From within a folder, if you open asset search in the left rail by clicking Filter, the filter in Status > Checkout > Checked out does not work (NPR-35530).
  • If you attempt to delete all Smart Tags of an asset and save the changes, the tags are not removed. However, the user interface indicates that the changes are saved (NPR-35519).
  • Users are not able to rearrange or sort assets in list view in an orderable folder (NPR-35516).
  • If you edit the default metadata schema, the tags field in asset’s Properties page changes into a text field. The change allows unaware users to add on-demand tags and the tags are stored as a string in the repository (NPR-35478).
  • When downloading an asset, if you provide a name that does not have a valid email address, the download option is unavailable. However, if another option in the download dialog is selected, the button is enabled, but an email is not sent (NPR-35365).
  • Users are unable to check-in assets after editing those in Adobe InDesign and receive error about lack of permissions (NPR-35341).
  • Handlebars JavaScript library is upgraded to v4.7.6 (NPR-35333).
  • Metadata editor interface stops working as expected when you start from bulk metadata edit and de-select items until a single item remains selected (NPR-35144).
  • Global navigation does not open the correct console when clicked from within assets.html page (CQ-4312311).
  • Assets does not display RGB rendition for an asset that has RGB rendition (CQ-4310190).
  • The Relate option in menu is not displayed properly in the Properties page (CQ-4310188).
  • If filetype filter for documents is used to search assets and create a Smart Collection, the filter is not applied when the collection is accessed. Instead, all types of assets are displayed in the search (NPR-35759).
  • You cannot drag and add assets in a Lightbox from the Assets user interface (NPR-35901).
  • When a new version of an existing asset is created after resolving the naming conflict, the metadata of original asset is overwritten (CQ-4313594).
  • When you filter asset search using a search filter or predicate, open an asset to view or edit it, and go back to the search results page, the filter does not work. All the searched assets are listed unfiltered (NPR-35913).

Dynamic Media

  • The URL option for RESS image preset is enabled on the asset details page. Now, both URL and RESS options are available on the asset details page when RESS image preset is selected in the dynamic renditions section. (CQ-4311241)
  • Interactive media component - interactive video does not work if the user has Experience Manager with selective publish configuration (CQ-4311054).
  • If you move assets across folders, the synchronization between Experience Manager and Dynamic Media–Scene7 via API is very slow (CQ-4310001).
  • When using Omnisearch, the size of the logs increases significantly (CQ-4309153).
  • When selective sync is enabled and an asset is copied (not moved) into a sync folder, it does not sync as expected (CQ-4307122).
  • For uploaded assets that get auto-published to DM, the status does not display Published on AEM. Also, the Dynamic Media Publish status column does not show the correct published status (CQ-4306415).
  • If an asset is published on Experience Manager and is set to publish to Dynamic Media on activation, the scene7FileStatus metadata value does not update as expected (CQ-4308269).
  • When editing the video profile, Experience Manager does not display the height and bitrate values set for the video preset. The fields appear blank (CQ-4311828).


  • Unable to create a custom tag for all products in Commerce (CQ-4310682).

  • Product asset reference update causes replication threads to be in the wait state until the ProductAssetListener thread completes its commits to the JCR (NPR-35269).


  • When you use a Coral Tab View component with no tabs and then trigger a Foundation validator, the following error occurs (NPR-35636):

     Uncaught TypeError: Cannot set property 'invalid' of undefined
      at enable (foundation.js:10703)
      at foundation.js:10710
  • SCD forward replication fails for Delete events for nodes that include a comma in the name (NPR-35191).

  • After you upgrade to AEM 6.5.7, the builds start failing. The reason is, an old version or no jackson-core is embedded in the uber-jar (GRANITE-33006).

User Interface

  • When you switch from Card view to List view for documents in a folder in the Assets console, sorting does not work appropriately (NPR-35842).

  • When you hyperlink text in a text component, the search feature does not display appropriate results (NPR-35849).

  • When a value is not provided to a hidden field that is marked required, it blocks you from saving a component (NPR-35219).


  • When you use different values for IMS Tenant ID and Target Client code, Experience Manager fails to integrate with Adobe Target (NPR-35342).

Translation projects

  • Issues when exporting or importing a translation job in Experience Manager (NPR-35259).


  • When you create a campaign page using an out-of-the-box template in Touch UI and open the Email tab on the page properties dialog, the personalization variable for the subject and body fields remains disabled (CQ-4312388).


  • On adding a page structure to a community group, the Group title in the breadcrumb is changed to the title of the first Page (NPR-35803).

  • Unlike moderators, a standard community member is not able to access and edit any draft post (NPR-35339).

  • Broken access control and denial of service with DSRPReindexServlet which brings the communities site down until the indexing is complete (NPR-35591).

  • Removing All Users from the Administrators field does not actually remove them from the back-end (NPR-35592, NPR-35611).

  • The Compose Message component does not return any result when the entered text is a partial-match (NPR-35666).

  • You may notice some performance impact and slowness, when attempting to add tags to a new blog by selecting Add Tags. To improve performance, install hotfix.

Brand Portal

  • Adding a member to an Asset Contribution type folder shows Add User or Group caption in the user interface, although only Brand Portal active users are supported and not groups (NPR-35332).



Experience Manager Forms releases the add-on packages one week after the scheduled Experience Manager Service Pack release date.

Adaptive Forms

  • When you insert a table with a repeatable row to a repeatable panel that has multiple instances in an adaptive form, the table always gets added to the first instance of the panel (NPR-35635).

  • When the tab focus reaches the CAPTCHA component again after successfully verifying it once in an adaptive form, Experience Manager Forms displays the Provide Captcha phrase to proceed error message (NPR-35539).

Interactive Communication

  • When you submit a translated form, the submission messages display in English and do not translate to the appropriate language (NPR-35808).

  • When you include a hide condition in the attached XDP or document fragments, the Interactive Communication fails to load (NPR-35745).

Correspondence Management

  • When you are editing a letter, the modules with conditions take a longer time to load (NPR-35325).

  • When you select an asset from the left navigation pane that is not included in a letter and then select the next asset, the blue highlight is not removed from the previously selected asset (NPR-35851).

  • When you edit text fields in a letter, Experience Manager Forms displays the Text Edit Failed error message (CQ-4313770).


  • When you try to open an adaptive form on an Experience Manager Forms mobile application for iOS, the application stops to respond (CQ-4314825).

  • The To-do tab in the HTML workspace displays HTML characters (NPR-35298).


  • When you generate an XML document using the Output Service, the OutputServiceException error occurs for some of the XML files (CQ-4311341, CQ-4313893).

  • When you apply superscript property to the first character of the bullet, the bullet size gets smaller (CQ-4306476).

  • The PDF forms generated using the Output Service do not include borders (CQ-4312564).


  • When you open an XDP file in Experience Manager Forms Designer, a designer.log file gets generated in the same folder as the XDP file (CQ-4309427, CQ-4310865).

HTML5 Forms

  • When you select a checkbox in an adaptive form in Safari web browser for iOS 14.1 or 14.2, additional fields do not display (NPR-35652).

Forms Management

  • No confirmation message to indicate the successful bulk upload of XDP files to CRX repository (NPR-35546).

Document Security

  • Multiple issues reported for the Edit Policy option on AdminUI (NPR-35747).

For information on security updates, see Experience Manager security bulletins page.


Setup requirements and more information

  • 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 removing or uninstalling the Adobe Experience Manager package.

Install the service pack

To install the service pack on an Adobe Experience Manager 6.5 instance, follow these steps:

  1. Restart the instance before installation if the instance is in update mode (and this is the case when the instance was updated from an earlier version). Adobe also 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 and click Upload Package to upload the package. To know more, see Package Manager.

  5. Select the package and click 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 installations is successful. Typically, this happens on Safari but can intermittently happen on any browser.

Automatic installation

There are two ways to automatically install Adobe Experience Manager on a working instance:

A. Place the package into ../crx-quickstart/install folder when the server is available online. The package is automatically installed.

B. Use the HTTP API from Package Manager. Use cmd=install&recursive=true so that the nested packages are installed.


Adobe Experience Manager does not support Bootstrap installation.

Validate installation

  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.3 or later (Use Web Console: /system/console/bundles).

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

Install Adobe Experience Manager Forms add-on package


Skip if you are not using Experience Manager Forms. Fixes in Experience Manager Forms are delivered through a separate add-on package a week after the scheduled Experience Manager Service Pack release.

  1. Ensure that you have installed the Adobe Experience Manager Service Pack.
  2. Download the corresponding Forms add-on package listed at AEM Forms releases for your operating system.
  3. Install the Forms add-on package as described in Installing AEM Forms add-on packages.

AEM includes a new version of AEM Forms Compatibility Package. If you are using an older version of AEM Forms Compatibility Package and updating to AEM, install the latest version of the package post installation of Forms Add-On Package.

Install Adobe Experience Manager Forms on JEE


Skip if you are not using AEM Forms on JEE. Fixes in Adobe Experience Manager Forms on JEE are delivered through a separate installer.

For information about installing the cumulative installer for Experience Manager Forms on JEE and post-deployment configuration, see the release notes.


After installing the cumulative installer for Experience Manager Forms on JEE, install the latest Forms add-on package, delete the Forms add-on package from the crx-repository\install folder, and restart the server.


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 features

Below is a list of features and capabilities that are marked as deprecated with Experience Manager Features are marked deprecated initially and later removed in a future release. An alternate option is usually provided.

Review if you use a feature or a capability in a deployment. Also, plan to change the implementation to use an alternate option.

Area Feature Replacement
Integrations The AEM Cloud Services Opt-In screen is deprecated. With the Experience Manager and Adobe Target integration updated in Experience Manager 6.5 to support the Adobe Target Standard API, which uses authentication via Adobe IMS and I/O, and the growing role of Adobe Launch for instrumenting Experience Manager pages for analytics and personalization, the Opt-In wizard has become functionally irrelevant. Configure system connections, Adobe IMS authentication, and Adobe I/O integrations via the respective Experience Manager cloud services.
Connectors The Adobe JCR Connector for Microsoft SharePoint 2010 and Microsoft SharePoint 2013 is deprecated for Experience Manager 6.5. N/A

Known issues

  • If you are upgrading your Experience Manager instance from 6.5 to version, you can view RRD4JReporter exceptions in the error.log file. Restart the instance to resolve the issue.

  • If you install Experience Manager 6.5 Service Pack 5 or a previous service pack on Experience Manager 6.5, the runtime copy of your assets custom workflow model (created in /var/workflow/models/dam) is deleted.
    To retrieve your runtime copy, Adobe recommends to synchronize the design-time copy of the custom workflow model with its runtime copy using the HTTP API:

  • Contact Adobe Customer Care if you encounter issues when editing and creating cascading rules in Folder Metadata Schema Forms Editor and Metadata Schema Forms Editor using Define Rule dialog. The rules that are already created and saved are working as expected.

  • If a folder in the hierarchy is renamed in Experience Manager Assets and the nested folder containing an asset is published to Brand Portal, the title of the folder is not updated in Brand Portal until the root folder is published again.

  • When a user selects to configure a field for the first time in an adaptive form, the option to save a configuration does not display in Properties Browser. Selecting to configure some other field of the adaptive form in the same editor resolves the issue.

  • If Connected assets configuration wizard returns a 404 error message after installation, manually reinstall the cq-remotedam-client-ui-content and cq-remotedam-client-ui-components packages using the Package Manager.

  • The following errors and warning messages may display 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.
    • Hotspot in a Dynamic Media interactive image is not visible when previewing the asset through Shoppable Banner viewer.
    • bundle (395)[] : Timeout waiting for reg change to complete unregistered.

OSGi bundles and content packages included

The following text documents list the OSGi bundles and Content Packages included in Experience Manager

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

Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now