DocumentationExperience Cloud KCS

Asset properties are missing because of a DAM UI JSP compilation failure

Last update: August 18, 2026

This article describes how to address an issue in Adobe Experience Manager where asset properties are missing because a DAM UI JSP fails to compile due to outdated Social or Rating imports. To fix this, review the JSP compilation errors, check for outdated DAM UI content or stale overlays, install the correct package for your AEM 6.5 LTS build, and validate the Asset Metadata screen.

Description description

Environment

Adobe Experience Manager (AEM) 6.5 LTS or later

Symptoms

  • Asset properties do not appear in the Asset Metadata screen in some environments, even though they are visible in others.
  • Error logs show JSP compilation failures referencing missing classes such as com.adobe.cq.social.tally.client.api.Rating.

Cause

This issue occurs when the DAM UI JSP responsible for displaying asset ratings fails to compile due to references to legacy Social/Rating bundles that have been removed in AEM 6.5 LTS. It is often caused by a missing or outdated cq-dam-content package or by stale overlays shadowing updated content.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Review the error logs in the affected environment for JSP compilation errors that reference missing Social or Rating classes.

  2. Confirm that /libs/dam/gui/coral/components/admin/rating/individualrating/individualrating.jsp fails because of legacy import statements.

  3. Check for stale content or overlays in the affected environment.

    • Inspect for an outdated cq-dam-content package.
    • Inspect overlays under /apps/dam/gui/.../rating that shadow the updated LTS content.

  4. In Package Manager, compare the version of cq-dam-content between your working and affected environments. Ensure that the correct version for your installed AEM 6.5 LTS release is installed in all environments. For example, one environment can use a version such as com.adobe.cq.dam:cq-dam-content:zip:2.5.1240.

  5. If the required cq-dam-content package is missing, install it by using Package Manager.

  6. If the issue persists after installation, restart the AEM instance.

  7. Access the Asset Metadata screen for the affected assets and verify that the properties are now visible.

recommendation-more-help
experience-cloud-kcs-help-kbarticles