Adobe Experience Manager 6.5 Latest Service Pack Release Notes

Last update: 2023-12-08
  • Created for:
  • Leader

Release information

Product Adobe Experience Manager 6.5
Type Service Pack release
Date Thursday, December 07, 2023
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:

  • Enabled Sites Page Editor/Image Component user to reference assets from the remote Assets Cloud Service. (SITES-13448, SITES-13433)
  • AEM now supports server-side sorting for quicker project navigation in List view. Project nodes are sorted based on the user-selected column before appearing in the interface.


  • New Adaptive Form Core Components: Vertical tabs, Terms & Conditions, and Checkbox are added to enhance the scalability of forms.

    • Checkbox component: Adaptive Forms based on Core Components can now include a checkbox component. It allows users to make binary choices, selecting or deselecting a particular option. It typically appears as a small box that can be clicked or tapped to toggle between two states: checked and unchecked. The checkbox is a common form element used to present a yes/no or true/false choice.

    • Terms and Conditions component: Adaptive Forms based on Core Components can now include a Terms and Conditions component. It allows forms authors to introduce a specific section within the form where users are presented with the terms, conditions, or legal agreements associated with the use of a service, product, or platform. This component is designed to inform users about the rules, regulations, and obligations they are agreeing to by submitting the form.

      Vertical tabs, Terms & Conditions and Checkbox components

    • Vertical tabs component: Adaptive Forms based on Core Components can now organize form content into a vertical list of tabs, providing a structured and navigable layout. The use of vertical tabs in a form can enhance the overall user experience by simplifying navigation and improving the organization of form content, especially in situations where a form contains multiple sections or complex information.

  • 64-bit version of AEM Forms Designer: The 64-bit version of AEM Forms Designer brings enhanced performance, scalability, and memory management to empower your form creation experience. With the 64-bit architecture, you can tackle even larger and more complex projects with ease, ensuring seamless design workflows and optimized efficiency. Elevate your form design capabilities and embrace the future of AEM Forms Designer with this cutting-edge release.

  • Connect an Adaptive Forms with Microsoft® SharePoint List: AEM Forms provides an OOTB integration to submit forms data directly to SharePoint List, letting you use SharePoint’s Lists capabilities. You can configure Microsoft SharePoint List as a datasource for a Form Data Model and use the Submit using Form Data Model submit action to connect an Adaptive Form with SharePoint List.

  • Support to configure Document of Record properties for Adaptive Form Fragments: You can now easily customize your Adaptive Form fragments and its fields in Adaptive Form editor.

  • 64-bit XMLFM: The 64-bit iteration of XMLFM introduces heightened performance, scalability, and refined memory management. It is the first 64-bit native service deployed on the server-side. By harnessing its inherent capability to access significantly larger memory resources compared to its 32-bit counterpart, XMLFM 64-bit empowers seamless handling of larger rendering workloads. This milestone not only represents a leap in performance but also introduces key enhancements to the native service framework within the AEM Forms server. This update equips AEM Forms server to seamlessly support any 64-bit native service.

Deprecated feature

  • ActiveMQ in AEM is deprecated. ActiveMQ was used for communication between two AEM Publish instances. Adobe recommends that customers now use a load-balancer.

Fixed issues in Service Pack 19



  • On an AEM Sites page, when you zoom in 200% on the page, the links Language Copy and CSV Report in the References rail disappear. (SITES-11011)

Admin User Interface

  • AEM Screens Channel Preview functionality does not work or display on the Dashboard. (SITES-15730)
  • During a page move operation, if the user interface cannot display the references but states that these are automatically republished, they are not republished. (SITES-16435)
  • In AEM 6.5 with Service Pack 16 or 17, when in the List view of sites with the “Workflow” column enabled, you cannot sort the list based on the items in that column. No sorting occurs. (SITES-15385)
  • For a redirect page template, the redirect field has been made mandatory. However, the validation for the required field is not getting applied nor working in these two scenarios: when a page is created without a mandatory redirect value; cannot create a redirect page. The validation does not work when navigating using keyboard shortcuts and when the field is marked as invalid, it does not proceed. (SITES-15903)
  • Some Incoming Links were not getting included in the displayed count in the References panel. For example, the panel was showing Incoming Links (6) but there were actually nine incoming links. (SITES-14816)

Classic UI

  • After installing hotfix in SITES-15827, dialog box titles that had whitespace between words were getting replaced with " ". Line breaks were also being removed. (SITES-16089)
  • Encoded dialog box titles are now resulting in a double encoding of the title. (SITES-15841)
  • Update of AEM servers from service pack 6.5.16 to 6.5.17 resulted in a double encoding of Classic UI dialog box titles. (SITES-15634)

Content Fragments

  • An Internal Server Error message appears in the Content Fragment Editor. (SITES-13550)
  • The update of the org.json library by way of NPR-41291 caused data error conversions in the DefaultDataTypeConverter of the cfm-impl bundle. Data type conversion must be more flexible. (SITES-16473)
  • Getting the error pop-up message, “This content fragment version cannot be compared to the current version because of incompatible content.” Content fragments should be comparable but it is not. (SITES-16317)
  • Changed the asset selector JS URL from
    to (SITES-16068)
  • Adapt new Polaris metadata API response schema for CFM-Polaris integration. (SITES-15166)
  • All content fragments should be listed where the selected content fragment is referenced. Instead, asset references in the content fragment reference panel show 0(zero) references. (SITES-15036)

Core Backend

  • Improve StyleImpl. (SITES-15164)
  • Improve the release/650 branch of the WCM pipeline to be able to run integration tests for its modules. (SITES-12938)

Campaign integration

  • On the signature component (/apps/fpl/components/campaign/signature), the link Externalizer was not working. The domain was not getting appended to the image source, if the HTML comment above the image tag was removed. This issue was found only with the signature component in the production environment, not the staging environment. (SITES-16120)

Foundation Components (Legacy)

  • Adobe Experience Manager (AEM) Sites Search component breaks the user interface. (SITES-15087)

GraphQL Query Editor

  • GraphQL Editor user interface does not let you scroll through all the persisted queries when there is a high number of queries (for example, more than 25). (SITES-16008)
  • The GraphQL Editor is not saving the publishing status of persisted queries. The unpublish button appears in the GraphQL Editor, but the icon that indicates that the persisted query is published does not appear. Refreshing the page shows that the persisted query is not even published. (SITES-15858)


  • Changes in the repository are not save due to Oak0001 conflicts when multiple pages are being edited or content is being authored. It is normal to perform a retry in such an event but this does not occur. (SITES-14840)

MSM - Live Copies

  • MSM Rollout Button does not work in the touch graphical user interface. (SITES-16991)
  • Link Reference does not get updated inside Experience Fragment when creating a live copy or rolling out an Experience Fragment. (SITES-15460)

Page Editor

  • In Forms > Themes, if you opened a theme in the theme editor and made a few changes and saved, then clicked Preview, a loading icon is visible but the actual preview does not load. (SITES-17164)
  • Selection of multiple document filetypes on asset type filter is not working on the page console. No results are found even if the results of one particular filetype are available. As a result, authors are unable to filter multiple documents. They must use multiple document types and they are having to filter it one at a time. (SITES-14047)
  • After upgrading an instance from AEM 6.5.17 and AEM 6.5.18, from inside the Page Editor, if you selected Publish Page, you are redirected to a URL that does not exist. The user should be redirected to the Publish wizard. (SITES-15856)
  • Redundant copy from AEM’s Clipboard during a paste from the operating system’s Clipboard. (SITES-15704)
  • In Assets, selecting Documents, then under Filtertype, selecting Microsoft® Word or Microsoft® Excel shows no results even though files of both types exist. (SITES-14837)


  • When you create or save a public folder, three groups are created in an admin dashboard. (ASSETS-26700)
  • Unable to differentiate publishing assets to Experience Manager or Brand Portal. (NPR-41320)
  • In the search panel, when you select checkboxes and deselect any one of them, all the checkboxes are unchecked. (ASSETS-26377)

Dynamic Media

  • After an asset is uploaded to AEM, the update_asset workflow is triggered. The workflow never finishes. Looking at the workflow instances, the workflow finishes up to the product upload step. The next step is Scene7 batch upload. User can see that the asset is in Scene7 from the Dynamic Media Classic app. (ASSETS-30443)
  • A custom Servlet (API endpoint) is returning an incorrect Dynamic Media (Scene7) file name. It occurs when an asset is deleted and replaced with an asset of the same name. The custom servlet is returning the old Dynamic Media (Scene7) file name, while a “jcr” API call returns the correct file name. (ASSETS-29476)
  • Even after Sync is turned off at the Folder level, the Logs show the trigger of “Scene7 ReplicateOnModifyListener”. The ReplicateOnModifyListener/Worker should skip processing on non-Dynamic Media folder assets and content fragments. (ASSETS-26705)
  • People with low vision are impacted if the Focus is not visible in drop-down elements (Content Only, View, More Options) in high contrast black and white modes. (ASSETS-25759)
  • People with low vision are impacted if luminosity contrast ratio for text on a page is less than 4.5:1. (ASSETS-25756)
  • Screen readers are not narrating the displayed pop-up message after submitting the data. (ASSETS-25755)
  • Screen readers are not recognizing landmarks in the page (Dynamic Media; creating a video encoding profile), when navigated using landmark/region shortcut key D/R. (ASSETS-25752)
  • Screen readers are not recognizing multiple landmarks in the page (Dynamic Media; creating interactive video), when navigated using landmark/region shortcut key D/R. (ASSETS-25750)
  • Screen readers (NVDA/JAWS/Narrator) are not recognizing the Landmarks in Edit Asset page while navigating using the shortcut keys D/R. (ASSETS-25744)
  • User gets an empty/false async job message but the connected asset is published successfully. (ASSETS-29342)


Adaptive Forms

  • When a user adds a toolbar to Adaptive Form, the Form Container Label shows erratic behavior because it does not change to the preferred language the Author selected for Forms. (FORMS-11371)
  • In AEM Forms Workspace, the dropdown field selects the first option by default on the UI. (FORMS-11346)
  • The language configuration in AEM does not show to have any effect if you use locales with five characters and the decimal separator is not correctly rendered in the letter. (FORMS-11344)
  • When a user generates the XML output using the workbench process, it fails for a few of the files. (FORMS-11314)
  • When a user generates preview for Document of record (DOR) in languages other than English, it does not work. (FORMS-11106)
  • When a user converts some image files with PDFG on an OSGI instance based on Linux with JDK11, it does not convert. (FORMS-11105)
  • When user installs AEM Forms add-on, it breaks the content tree panel in AEM Sites. (FORMS-10912)
  • When a user copies dates using NVDA screen reader from Date picker component, it does not read correctly. (FORMS-10805)
  • In Forms rule editor, the user is unable to set the value of the Radio button/Checkbox when the data value type is Boolean. (FORMS-10713)
  • When a user adds added items in an Adaptive Form, it is added in reverse order to a drop-down List. (FORMS-10456)
  • When a dropdown is cleared using the rule editor, the first provided value still appears even though the value has been cleared. (FORMS-9963)
  • Users are not able to access Form Title using screen readers such as NVDA. (FORMS-8815)
  • Users are not able to access Sub Title in a Form using screen readers such as NVDA. (FORMS-8814)
  • In the page source of html form, the access key attribute is empty and is not working. (FORMS-5753)
  • In the About Workspace dialog, the text “Adobe Experience Manager – Forms” is presented as text. (FORMS-5748)

Forms Designer

  • When a user tries to read non-interactive PDF forms through screen readers, some list items are not read or skipped. (LC-3921645)
  • When a user tabs through the editable fields, it does not traverse to all the PDF form fields consistently. (LC-3921631)
  • Ordering of the tags are randomly changed in PDF even tagging in Forms Designer is correct. (LC-3921313)
  • A list does not display correctly in the tags in Adobe Acrobat Reader or Adobe Acrobat DC. (LC-3921306)
  • Heading levels which are assigned correctly in Forms Designer are randomly changed to a <P> tag in Adobe Acrobat. (LC-3921305)
  • In a table the ID of any object cannot be modified once it is assigned. (LC-3921134)
  • If merged cells are in the table, no GUI is available for setting the span (row and column) and scope in a complex table in AEM Forms Designer. (LC-3919532)


  • Creating a language copy at the language root level does not adjust paths in the page. In the case where the language copy was created, not for the language root but for the pages under it, the path changed correctly. (NPR-41364)
  • The “Relative Date Presentation” tooltip can only be closed by pressing Escape (ESC) on the keyboard. The tooltip should close when the user selects any part of the user interface. (NPR-41394)
  • Unlocalized string Something went wrong while adding the private key. when adding the wrong Private Key File in Edit User > Keystore. (NPR-41366)
  • Icons are needed for Microsoft® SharePoint and Microsoft® One Drive in the AEM 6.5 environment. (NPR-41354)
  • Unlocalized “UserId/Password mismatch.” string in Security > User > Create dialog box. (NPR-41245)
  • Popover code and Event handlers are loaded twice, breaking user-created Coral3-based user interfaces. (NPR-41171)
  • Deselection does not work correctly after using “Select All” in the AEM Sites console. (NPR-41304)


  • SMS links in an AEM email campaign are not correctly written; they contain an HTML anchor element. (NPR-41211)
  • Wording used on account configuration screen should not use new credential type. (NPR-41210)
  • Moving Analytics report import scheduler from ManagedPollConfig to sling jobs. When two different analytics frameworks were attached with different report suites to two different sites, ManagedPollConfig polls only one of them. (NPR-41209)
  • When the value is reset to default, the previously selected timeframe button stays enabled. In the content insight dashboard of AEM, by default the time frame is set at the week and shows content insights as weekly data. Now, if the user selects other time frame options, such as hour, day, month, and year, the data changes according to the selected value. However, if the values are reset, by default, the visible time frame is week but still the previously selected time frame option is selected. (NPR-41246)


  • Backport utility to rate limit writes to AEM in case async indexing is delayed. (NPR-40985)


  • QueryBuilder queries with square brackets are wrongly translated to xpath . (NPR-41298)

Translation projects

  • While creating the language copy of page “A”, it should automatically create the language copies of the referenced Pages, Experience Fragments, Content Fragments, and Assets. Also, the newly created language copy of Page “A” at the new path should have its references updated to the respective newly created language copies of the Pages, Experience Fragments, Content Fragments, and Assets. (NPR-41076)


  • Unable to complete a task in the Inbox. Only an “undefined” value is observed in the drop-down menu when trying to complete the task and select an action. This means that users cannot apply the AEM 6.5.18 service pack. (NPR-41402 and NPR-41473)
  • Unable to complete tasks in Inbox. There is no value (only “undefined”) in the drop-down list when trying to complete the task for zip files, Asset reports, move (success or failure), or asset expiration. (NPR-41305)
  • When a user selects Tools > Workflow > instances, then selects the running workflow, then select View Payload, it results in a 500 error page. (NPR-41325)

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.17 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

Supported platforms

  • JDK 11.0.20 is not supported to install AEM Forms on JEE Installer. Only JDK 11.0.19 or earlier versions are supported to install AEM Forms on JEE Installer. (FORMS-10659)


  • On JBoss® 7.1.4 platform, when user installs Experience Manager or later service pack, adobe-livecycle-jboss.ear deployment fails. (CQ-4351522, CQDOC-20159)

  • After installing AEM Service Pack full installer, the EAR deployment fails on JEE using JBoss® Turnkey.
    To resolve the issue, locate the <AEM_Forms_Installation_dir>\jboss\bin\standalone.bat file and update Adobe_Adobe_JAVA_HOME to Adobe_JAVA_HOME for all occurrences before running the configuration manager. (CQDOC-20803)

Install the servlet fragment (AEM Service Pack or earlier)

  • If you are upgrading to AEM Service Pack or higher, and your AEM instance is operating on Tomcat 8.5.88, it is mandatory that you install the servlet fragment before you proceed with the installation of Service Pack or higher.
  • It is mandatory that you install the servlet fragment for all application servers except those running on JBoss® EAP 7.4.0.

To install the servlet fragment:

  1. Download the servlet fragment from Software Distribution.
  2. Start the application server.
  3. Wait for the logs to stabilize and check the bundle state.
  4. Open Web Console Bundles. The default URL is http://[Server]:[Port]/system/console/bundles.
  5. Select Install or Update.
  6. Select the downloaded fragment
  7. Select Install or Update.
  8. Wait for the application server to stabilize.
  9. Stop the application server.

Adaptive Forms

  • When an Adaptive Form is published, all its dependencies, including policies, get republished, even if no modifications have been made to them. (FORMS-10454)
  • 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.
  • When users perform the submit action, the submission fails with an error:
    javax.servlet.ServletException: java.lang.NoSuchMethodError
    To resolve the issue, recompile the Sling scripts such as JSP, Java, and Sightly. (FORMS-8542)

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