ZIP upload fails with “maxUploadSizeInBytes must be > 0” and Smart Crop download errors

Uploading ZIP files and downloading Smart Crops or custom overviews can fail in Adobe Experience Manager Assets as a Cloud Service. ZIP uploads fail with a maxUploadSizeInBytes must be > 0 validation error, while Smart Crop and custom overview downloads return an unexpected service error, often for assets that were copied from one location to another. To fix these issues, reprocess the affected assets in Dynamic Media and confirm that the maxUploadSizeInBytes configuration is set to a positive value.

Description description

Environment:

  • Adobe Experience Manager as a Cloud Service (all versions)
  • AEM Assets with Dynamic Media

Issue/Symptoms:

  • Uploading ZIP files fails with the following validation error:

    zip’ has failed : maxUploadSizeInBytes must be > 0.

  • Downloading custom overviews or Smart Crops for certain images displays the following message:

    Unexpected Error: Looks like we are having some issues with our service.

  • The issue is reproducible when accessing specific assets and using the Smart Crop or custom overview features.

  • Affected assets may have been copied from one location to another within AEM.

Root cause:

Copying assets in AEM without reprocessing them in Dynamic Media can cause metadata conflicts that produce Smart Crop download errors. AEM is path-based, whereas Dynamic Media (Scene7) is database-based, so a copied asset and its original can reference the same Dynamic Media asset metadata. Separately, a misconfigured or unset maxUploadSizeInBytes parameter prevents ZIP uploads.

Resolution resolution

Note: If assets were copied from one location to another in AEM, note that AEM is path-based but Dynamic Media (Scene7) is database-based, so both the original and the copy can reference the same Dynamic Media asset metadata.

To fix the issue:

  1. Go to the new asset location in AEM and select the affected assets.
  2. Run the Dynamic Media Reupload workflow on the selected assets to reprocess them in Dynamic Media and regenerate Smart Crops.
  3. Do not use the regular reprocess workflow, because it may not resolve the metadata conflict.
  4. Check the maxUploadSizeInBytes value in the relevant AEM Assets configuration.
  5. Ensure that maxUploadSizeInBytes is set to a positive integer greater than 0. If the value is 0 or not set, update the configuration and restart the relevant services if required.
  6. Attempt to upload ZIP files and download Smart Crops again. If the issues persist, review the AEM error logs for related validation or workflow errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles