Documentation

No assets visible in AEM editor

Last update: Wed Sep 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets, the editor fails to display any assets, including previously published ones. New asset uploads also fail during processing. Although published pages show assets correctly, the editor view remains blank. To resolve the issue, reconfigure valid Dynamic Media credentials in AEM.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets

Issue/Symptoms

  • The AEM Editor fails to display any assets, including pictures and videos.

  • The asset thumbnails and previews don’t load in the editor interface.

  • New uploads of pictures and videos fail during processing and remain invisible.

  • The issue occurs consistently across the production, stage, and development environments.

  • The error stack appears as follows:

    code language-none 
    [ 100.101.100.100 [ 123456789101112]  GET /is/image/powercoprod/image%20979 HTTP/1.1]  org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught Throwable    com.day.cq.dam.scene7.api.model.AuthenticationException: IPS API fault code=10001: Invalid username/password        at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.validateIpsApiFault(Scene7APIClientImpl.java:403) [ com.day.cq.dam.cq-scene7-core:5.13.526]         at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.makeRequest(Scene7APIClientImpl.java:280) [ com.day.cq.dam.cq-scene7-core:5.13.526]         at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.makeRequest(Scene7APIClientImpl.java:249) [ com.day.cq.dam.cq-scene7-core:5.13.526]         at com.day.cq.dam.scene7.impl.Scene7APIClientImpl.getSecureISAuthToken(Scene7APIClientImpl.java:2241) [ com.day.cq.dam.cq-scene7-core:5.13.526]         at com.day.cq.dam.scene7.impl.Scene7ServiceImpl.getAndStoreSecureISAuthToken(Scene7ServiceImpl.java:2418) [ com.day.cq.dam.cq-scene7-core:5.13.526]         at com.adobe.cq.dam.s7imaging.impl.ps.forwarder.ForwardRequestHandlerFactory.getPreviewServerToken(ForwardRequestHandlerFactory.java:194) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.getPreviewServerToken(PlatformServerServlet.java:249) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.handleForward(PlatformServerServlet.java:231) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.handleRequest1(PlatformServerServlet.java:217) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.access$000(PlatformServerServlet.java:90) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet$1.run(PlatformServerServlet.java:204) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.scene7.is.util.callbacks.Proc0.call(Proc0.java:68) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.scene7.is.util.callbacks.Proc0.call(Proc0.java:26) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.scene7.is.util.callbacks.Func0.apply(Func0.java:28) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.scene7.is.util.callbacks.ExecutionUtil.withClassLoader(ExecutionUtil.java:114) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.handleRequest(PlatformServerServlet.java:201) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]         at com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.doGet(PlatformServerServlet.java:191) [ com.adobe.cq.dam.cq-scene7-imaging:1.6.248]

Resolution resolution

AEM fails to connect to Dynamic Media because the credentials are invalid. This prevents asset previews from loading in the page editor and blocks new asset uploads.

To fix the issue:

  1. Check that the Dynamic Media configuration is correct.
  2. Enter valid credentials (email ID and password) for the Dynamic Media account.
  3. If needed, reset the password for the Dynamic Media account and reconfigure it within AEM.
  4. Make sure you’re added as a company administrator to all relevant Dynamic Media accounts—production, stage, and development.
  5. Test asset previews and uploads in AEM to confirm the issue is resolved.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f