Asset isn’t published to Dynamic Media Classic from Experience Manager Assets

In Experience Manager Assets, a corrupt image file prevents the asset from publishing to Dynamic Media Classic. The asset doesn’t appear in Dynamic Media Classic, and no public delivery URL is generated. The relevant logs show a mismatch between the actual file length and the length specified in the image header. To fix this, replace the corrupt file with a valid version, upload it to Experience Manager Assets, and verify publishing and public URL availability.

Description description

Environment

Experience Manager Assets with Dynamic Media Classic (Scene7) integration

Issue/Symptoms

When you upload an image to Experience Manager Assets, the asset doesn’t publish to Dynamic Media Classic.

  • An asset uploaded to Experience Manager Assets isn’t published to Dynamic Media Classic.
  • The asset isn’t available through its public delivery URL, which affects workflows that rely on asset distribution.
  • The asset doesn’t appear in Dynamic Media Classic.
  • No public URL is generated for the uploaded asset.
  • The available Dynamic Media Classic logs indicate file corruption, including a mismatch between the actual file length and the length specified in the image header.
  • No specific error appears in the Experience Manager UI.

Cause

The image file is corrupt. Its actual file length doesn’t match the length specified in the image header, so Dynamic Media Classic can’t process or publish the asset.

Resolution resolution

To fix this issue, follow these steps:

  1. Check the image file for corruption before you upload it.
    • Open the file in an image viewer or use a file-integrity tool.
  2. Obtain a valid version of the asset if the file doesn’t open or the image viewer displays an error.
  3. Upload the valid, non-corrupt version of the asset to Experience Manager Assets.
  4. Monitor the publishing workflow to confirm that the asset is published to Dynamic Media Classic.
  5. If the issue persists, review the available Dynamic Media Classic logs for additional file-integrity or publishing errors.
  6. After the asset publishes successfully, verify that it appears in Dynamic Media Classic and is available through its public delivery URL.
recommendation-more-help
experience-cloud-kcs-help-kbarticles