ACS Commons asset and MCP report failures in AEM environments
Adobe Experience Manager (AEM) ACS Commons report generation fails when asset reports, MCP reports, or Report Builder dashboards return errors, blank downloads, or empty results. This issue occurs due to outdated ACS Commons versions, missing bundles, or misconfigured report definitions affecting report execution. To resolve the issue, upgrade the version, validate the bundles, and fix the configurations.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- Displays the error: java.lang.NoSuchMethodError: org.apache.poi.xssf.usermodel.XSSFColor.
<init>(Ljava/awt/Color;)V during report generation. - Shows TooManyCallsException during report execution or return empty report results.
- Failed to load the ACS Commons Report Builder dashboard at
/apps/acs-commons/content/reports.html. - Fail to download MCP-generated report files or return blank Excel/CSV files.
- Redirect to error pages when accessing report dashboards or execution endpoints.
Root cause
The issue occurs when an outdated ACS Commons version uses incompatible Apache POI APIs or when required Report Builder bundles are missing or inactive. Misconfigured report definitions, incomplete dependencies, or complex queries that exceed system limits also lead to failures such as NoSuchMethodError, empty results, or execution exceptions.
Resolution resolution
Follow these steps to identify the failure type and resolve the ACS Commons report issue:
- Identify the failure type by reviewing AEM logs and locating errors such as NoSuchMethodError, XSSFColor, or TooManyCallsException.
- Categorize the issue by mapping the detected error to scenarios such as version incompatibility, missing bundles, empty results, or execution limits.
- Resolve version-related errors by upgrading ACS Commons to version 6.0.14 or later and deploying the update through the Cloud Manager pipeline.
- Validate bundle deployment by checking the ACS Commons Report Builder bundle in
/system/console/bundlesand ensuring it is active with no dependency issues. - Fix empty report results by verifying that assets exist in the environment and confirming that the selected report paths and configurations are correct.
- Address execution limits by increasing the sling.max.calls threshold where applicable, to handle complex report queries.
- Validate the resolution by re-running the report, confirming successful download, ensuring the dashboard loads correctly, and verifying that report data appears as expected.
When to escalate
- The issue persists after upgrading ACS Commons and validating bundle activation.
- The report generation continues to fail despite correct configuration and data availability.
- The out-of-the-box AEM asset reports fail to generate or download.
- The error indicates a system-level issue beyond ACS Commons configuration.