|Products||Adobe Experience Manager 6.5|
|Type||Service Pack Release|
|Date||November 26, 2020|
|Download URL||Software Distribution|
Adobe Experience Manager 22.214.171.124 is an important update that 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 126.96.36.199 includes:
Performing the page moves and MSM rollouts as asynchronous operations to reduce their impact on runtime performance.
Users can sort digital assets in Card and Column views.
Assets and Dynamic Media provide multiple accessibility enhancements. The enhancements are related to keyboard navigation, use of screen readers, and enabling users to use similar assistive technology (AT). See Assets enhancements and Dynamic Media enhancements.
Form data model HTTP client configuration to optimize performance.
Availability of Reset Option for each component in the Layout mode
Experience Manager 6.5 Service Pack 7 Forms improves the performance for:
Validating the field values on the server when you submit an adaptive form.
Converting a PDF form to an adaptive form using the Automated Forms Conversion service.
Support for Microsoft SQL Server 2019 in Experience Manager Forms.
The built-in repository (Apache Jackrabbit Oak) is updated to version 1.22.5.
For a complete list of features and enhancements introduced in Experience Manager 188.8.131.52, see What’s new in Adobe Experience Manager 6.5 Service Pack 7.
The following is the list of fixes provided in Experience Manager 184.108.40.206 release.
When you open the Timewrap option for a page, keep the Timeline side rail option open, and navigate to Sites console, the
Failed to Load error occurs (NPR-34951).
The Timewrap option does not display images for the selected date and time range (NPR-34951).
When a filter calls
getHeader() from a page containing a Content Fragment, the
java.lang.AbstractMethodError error occurs (NPR-34942).
When the path of a page contains multiple content substrings, previews fail to render, and the version compare function also fails (NPR-34740).
When you set a numeric value for the
String type label property of a component, you can delete the component and undo the delete operation. However, after undoing the delete, the label property changes from
The following exception occurs on adding an Experience Fragment based on a template with a locked layout to a page (NPR-34632):
When you move a folder, it results in traversal issues and the following error occurs (NPR-34554):
org.apache.sling.api.SlingException: Cannot get DefaultSlingScript. org.apache.jackrabbit.oak.query.RuntimeNodeTraversalException: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped
When new assets are created, published, and moved to a new location, the
Request to complete move operation workflow gets created and results in an Aborted state. Uploading a new asset and executing a
move operation results in creating the
Request to complete move operation workflow in pending state (NPR-34543).
When you export an Experience Fragment from Experience Manager 6.5.2 environment to Target Standard, the API call fails because the workspace property is not available for Target Standard (NPR-34557).
Users cannot publish pages through the manage publication option because the Publish option disappears (NPR-34542).
When you add some styles to the text, a
<div> tag is added to the text, and the style cannot be applied to the text anymore (NPR-34531).
When you select an item in a pop-up menu and update the required files, it does not allow saving dialog values as the other menu has an empty required field (NPR-34529).
When you create a page from a custom template and move it within the blueprint hierarchy, components deleted earlier from the page starts showing up on the page within the live copy hierarchy (NPR-34527).
Once an article style is applied to a content, it cannot be removed (NPR-34486).
All live copies and copies of an Experience Fragment point to the same Adobe Target offer ID (NPR-34469).
Bulleted list items are displayed in addition to the numbered list (NPR-34455).
The compare to source option fails to show the difference between the source page and the edited version of a page (NPR-34285).
When you delete a page, the versioning details are not configurable (NPR-34159).
When a user selects the Open Selection dialog option, the keyboard focus moves to the hidden control present on the page (CQ-4307779, CQ-4293601).
When you move a published folder on the Author, the folder paths are not updated accordingly on the Publish instance (CQ-4305144).
When a user select the
Enter key on the Select All option, the keyboard focus does not move to the Create Control option (CQ-4293599).
When you select the
Esc key, the focus is not restored to the parent control (CQ-4293593, CQ-4293590).
Improved WCAG compliance for Sites UI and Core components (CQ-4293448).
Zoom and Scale functions are disabled for the Sites Editor page (CQ-4282353).
After you use the Rotate Right option, the screen reader stops narrating the current rotation or flip state (CQ-4282128).
Done and Cancel Configure dialog buttons have more than one tab-stops (CQ-4274601).
Moving of pages with a similar name on the same level is not allowed (NPR-35041).
After selecting the Clear (x) option, the keyboard focus does not move to the Filter field (CQ-4293581).
When you upgrade to Experience Manager 220.127.116.11, behavior of the inherited paragraph system changes and it does not work properly (NPR-35117).
Keyboard users are not able to shift the tab focus in an appropriate order after selecting the Action section on an AEM Sites page (CQ-4307786).
After selecting an option in the link target menu list of the RTE toolbar when editing a content fragment, the content fragment author dialog starts to flicker (CQ-4305532).
Keyboard users are not able to select the options in the Add Component drop-down list using the Down arrow key (CQ-4295097).
The tab focus does not shift in an appropriate order when selecting a date from the Calendar menu in the Assets tab of a Sites page (CQ-4293600).
The tab focus does not shift to the next or previous options for keyboard users after deleting the Link or Text options available when editing a Sites page (CQ-4293597).
Keyboard users are not able to shift tab focus back to More options in the Actions section after viewing the available options and pressing the
Esc key (CQ-4293592).
When you activate the Rotate option for an image in the Edit mode, the tab focus, instead of remaining on Rotate, shifts to the Redo option for the keyboard users (CQ-4293587).
In the Open Selection dialog available on the Link and Actions tab, the tab focus shifts to hidden elements in the page after the Cancel option (CQ-4293579).
When keyboard users edit an image, navigate to the Finish option, and press the Enter key, the screen readers do not announce the completion (CQ-4282351).
The Move up and Move down options available on the Link and Actions dialog are not available to the screen reader and keyboard users (CQ-4281120).
Keyboard users are not able to restore the tab focus after navigating to the Close (X) option on the Properties page (CQ-4293581, NPR-34653).
Adobe Experience Manager 18.104.22.168 Assets fixes the following issues and provides the following enhancements.
The following enhancements are done for accessibility in Experience Manager Assets in this release. For more information, see accessibility features in Assets.
Esckey can collapse the Show All option without losing the focus (CQ-4293598).
The following user experience enhancement is done in Assets:
After the upgrade to 6.5, if a JSON file is generated using the Assets HTTP API, there are issues with the encoding used in the file (NPR-35129).
Users of a group that is not provided the permission to create Collections (Create Collection option is unavailable) are still able to create collections by directly accessing the URL
When sorted by name, the searched assets are sorted in case-sensitive manner. This creates two separate sorted lists based on casing that appearing in ordered manner in the search results (NPR-35068).
When a Content Fragment is opened in the editor, warning messages (
Invalid value specified for a metadata property) are logged in the error logs (NPR-35012).
Users without administrator privilege can edit expired assets using [Experience Manager] desktop app. (NPR-34993).
When the same 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 editing Collections, a user can delete the title of the Collection and successfully save the changes (NPR-34889).
When uploading a duplicate image, a delete option is presented. Selecting delete lets the images upload. DAM Update Asset workflow is also triggered (NPR-34744).
When using Adobe Asset Link with Adobe InDesign, the search results do not contain folders and collections but only contain assets (NPR-34699, CQ-4303666).
Hovering pointer on card view, makes the screen scroll as a result of (automatic) focus on the quick actions available in the card (NPR-34514).
When editing the properties of multiple assets in bulk, selecting the Save option closes the bulk editor view and redirects to the main Assets page. This behavior is same as the behavior of Save & Close option and is not expected (NPR-34546).
The smart collection does not present the correct user interface setting after saving. The query is saved properly but the interface always displays the last added Option predicate (NPR-34539).
When adding assets to Experience Manager, the metadata without a namespace does not get imported (NPR-34530).
When dragging an asset on a folder to move it, the user interface also displays the option to Drop in Lightbox and Drop in Collection. Even if the move operation is canceled, the user interface continues to display the latter two options (NPR-34526).
%> is displayed on the collections page (NPR-34499).
In column view, Assets displays duplicate folder and asset names when scrolling upward and downward before all assets get displayed (NPR-34464).
If you create a private folder immediately after creating a public folder, then the public folder uses the private folder settings (NPR-34415).
In the card view, the cards are not listed in alphabetical order and cards cannot be sorted alphabetically (NPR-34234).
When reopening cascading rules, the choices are not maintained on the user interface (CQ-4301452).
The following enhancements are done for accessibility in Dynamic Media (CQ-4290306). For details, see accessibility features in Dynamic Media.
Tabkey, the focus moves to the appropriate user interface elements in the workflow to create an interactive video (CQ-4290621, CQ-4290620, CQ-4290619).
Remote Imagesets are not editable in Experience Manager if the company name and folder name are the same (NPR-31340).
The z-index order is incorrect when you try to preview the output after adding a hotspot to a Dynamic Media image or after editing a Dynamic Media video or an Experience Fragment with an image (CQ-4307267).
Dynamic Media sync fails when mixed media sets are reprocessed (CQ-4307184).
If an asset is moved to a folder on which auto-synchronization to Dynamic Media is configured, the asset does not synchronize (CQ-4307122).
Dynamic Media video is not playing on iOS devices with the native HTML5 video controls (CQ-4306977, CQ-4306727).
Cannot download images on which SmartCrop is applied (CQ-4304558).
Cannot selectively publish folders to Dynamic Media (CQ-4304526).
Unpublishing a video file from Experience Manager do not unpublish the Adaptive Video Set from a configured Scene7 deployment (CQ-4304405).
Adding a panoramic image asset in a panoramic media component and refreshing the page results in
Uncaught ReferenceError: $ is not defined error (CQ-4302810).
In the Viewer Presets Editor, when editing PanoramicImage/PanoramicImage_VR preset, in the
PanoramicView component, the
PANORAMICVIEW_AUTOROTATE modifier label is not available (CQ-4302443).
Video captions are not displayed if the video is not the first in a MixedMediaSet (CQ-4298161).
HTML5 eCatalog Viewer on iPhones mobile devices cannot turn the pages or flip the pages (CQ-4296611).
When scrolling swatches on a mobile device, the swatches scroll to the right and out of the visible area for a few seconds before scrolling back into view (CQ-4296439).
When a Viewer Preset Master Record is created, the CSS and artwork do not get published and only the viewer preset gets published (CQ-4262205).
When attempting to link an Experience Fragment for a given hotspot in the Interactive Video/Images component, it does not show the selected Experience Fragment path. Instead, it returns an empty value from the path field (NPR-35146, CQ-4298136).
Cannot preview an Experience Fragment in IVV Editor (CQ-4308560).
When adding a hotspot to an image and selecting an Experience Fragment, it is not possible to select the subfolders and the variants of the Experience Fragment (CQ-4307455).
The non-image assets do not show as published after uploading (CQ-4306415).
DAM CQ MIME Typeservice applies incorrect MIME types to 3D assets leading to incorrect rendering (NPR-34731).
NullPointerExceptionis returned when starting daily or weekly maintenance tasks from user interface (NPR-34953).
AudienceOmniSearchHandlerfunction uses a deprecated index (NPR-34870).
findByTitlefunction of the
TagManagerAPI does not work if the tag name contains a special character (NPR-34357).
ariaLabelledbyproperties to the
") are not displayed properly on the user interface (CQ-4305439).
The Link to field in component properties displays autocomplete suggestions that do not match the specified string (NPR-34865).
AEM displays the following error message when you schedule a daily maintenance window distributed between 2 days (NPR-35280):
ERROR The start time must precede (be less than) the end time
Experience Manager Forms releases the add-on packages one week after the scheduled Experience Manager Service Pack release date.
Experience Manager Service Pack does not include fixes for Forms. They are delivered using a separate Forms add-on package. In addition, a cumulative installer is released that includes fixes for Experience Manager Forms on JEE. For more information, see Install AEM Forms add-on and Install AEM Forms on JEE.
Unable to edit an adaptive form using Classic UI after applying Experience Manager Service Pack 6 (NPR-35126).
When you convert a PDF to an adaptive form, you cannot set a value for a nested panel using a form data model on the tabbed layout. In addition, there are issues when setting a value for Radio Button Groups dynamically with a static array using the code editor (NPR-35062).
When you enter Japanese characters in a text field component in an adaptive form, you can specify more characters than the maximum limit of 35 characters (NPR-35039).
The adaptive form displays unwanted parameters, such as
status, on the Thank you page displayed after submitting the form (NPR-34989).
The File Selection dialog for the Attachment component displays the unsupported file types as well for selection resulting in error during adaptive form submission (NPR-34970).
When you insert an adaptive form in an Experience Manager Sites page that includes text before the form, the cursor focus directly moves to the form instead of the text before the form (NPR-34947).
Preview with Data option to prefill an adaptive form using an Experience Manager 6.2 data XML file does not work appropriately (NPR-35087).
When you update the data dictionary for an adaptive form, the form does not get translated as the adaptive form returns cached values (NPR-34845).
Fragments take longer time to load in an adaptive form because of cache invalidation (NPR-34567).
Tab navigation does not work appropriately for screen readers in an adaptive form (NPR-34544).
Unable to save values for XML tags with numeric data, which includes float type, as a draft (NPR-35050).
When you migrate the assets from ES3, the assets include two non-editable default conditions (NPR-34972).
When you edit a data dictionary in a letter, the Lent Content section displays spinning rectangles instead of useful information (NPR-34853).
When you save a new document security policy, Experience Manager Forms displays the
Relative validity period is required error message (NPR-34679).
Document Security is not able to protect PDF 2.0 document (CQ-4305851).
For information on security updates, see Experience Manager security bulletins page.
Setup requirements and more information
Adobe does not recommend removing or uninstalling the Adobe Experience Manager 22.214.171.124 package.
Perform the following steps to install the Service Pack on an existing Adobe Experience Manager 6.5 instance:
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.
Before installing, take a snapshot or a fresh backup of your [Experience Manager] instance.
Download the service pack from Software Distribution.
Open Package Manager and click Upload Package to upload the package. To know more, see Package Manager.
Select the package and click Install.
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.
There are two ways to automatically install Adobe Experience Manager 126.96.36.199 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 188.8.131.52 does not support Bootstrap installation.
The product information page (
/system/console/productinfo) displays the updated version string
Adobe Experience Manager (184.108.40.206) under Installed Products.
All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console:
The OSGi bundle
org.apache.jackrabbit.oak-core is version 1.22.3 or later (Use Web Console:
To know the platforms certified to work with this release, see the technical requirements.
Experience Manager Forms releases the add-on packages one week after the scheduled Experience Manager Service Pack release date.
Skip if you are not using AEM Forms. Fixes in Adobe Experience Manager Forms are delivered through a separate add-on package.
AEM 220.127.116.11 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 18.104.22.168, install the latest version of the package post installation of Forms Add-On Package.
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.
The UberJar for Experience Manager 22.214.171.124 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:
<dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.5.7</version> <scope>provided</scope> </dependency>
UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository (
repo.adobe.com). The main UberJar file is renamed to
uber-jar-<version>.jar. So, there is no
apis as the value, for the
Below is a list of features and capabilities that are marked as deprecated with Experience Manager 126.96.36.199. 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.
|Integrations||The AEM Cloud Services Opt-In screen is deprecated. With the AEM and Target integration updated in AEM 6.5 to support the Target Standard API, which uses authentication via Adobe IMS and I/O, and the growing role of Adobe Launch for instrumenting AEM 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 AEM cloud services.|
|Connectors||The Adobe JCR Connector for Microsoft SharePoint 2010 and Microsoft SharePoint 2013 is deprecated for AEM 6.5.||N/A|
Ignore the following errors in the
error.log file during the installation of Experience Manager 188.8.131.52:
com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy] : Cannot register component (org.osgi.service.component.ComponentException: The component name 'com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy' has already been registered by Bundle 331 (com.day.cq.dam.cq-dam-core) as Component of Class com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy(1314)] : Could not load implementation object class com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy (java.lang.ClassNotFoundException: com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy not found by com.day.cq.dam.cq-dam-core ) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy(1316)] : Could not load implementation object class com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy (java.lang.ClassNotFoundException: com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy not found by com.day.cq.dam.cq-dam-core ) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy(1315)] : Could not load implementation object class com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy (java.lang.ClassNotFoundException: com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy not found by com.day.cq.dam.cq-dam-core ) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)BundleComponentActivator : Unexpected failure enabling component holder com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy (java.lang.IllegalStateException: Could not load implementation object class com.day.cq.dam.core.impl.collection.CollectionCreationListenerDummy) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)BundleComponentActivator : Unexpected failure enabling component holder com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy (java.lang.IllegalStateException: Could not load implementation object class com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy] : Cannot register component (org.osgi.service.component.ComponentException: The component name 'com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy' has already been registered by Bundle 331 (com.day.cq.dam.cq-dam-core) as Component of Class com.day.cq.dam.core.impl.team.MediaPortaltRoleProviderDummy) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)[com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy] : Cannot register component (org.osgi.service.component.ComponentException: The component name 'com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy' has already been registered by Bundle 331 (com.day.cq.dam.cq-dam-core) as Component of Class com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy) com.day.cq.dam.cq-dam-core bundle com.day.cq.dam.cq-dam-core:5.12.276 (331)BundleComponentActivator : Unexpected failure enabling component holder com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy (java.lang.IllegalStateException: Could not load implementation object class com.day.cq.dam.core.impl.team.MediaPortalShareHandlerDummy)
If you are upgrading your Experience Manager instance from 6.5 to 184.108.40.206 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-components packages using the Package Manager.
The following errors and warning messages may display during installation of AEM 6.5.x.x:
com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
com.adobe.granite.maintenance.impl.TaskScheduler- No maintenance windows found at granite/operations/maintenance.
The following text documents list the OSGi bundles and Content Packages included in AEM 220.127.116.11:
These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.