Expand my Community achievements bar.

Not able to edit asset

Avatar

Level 1

In AEM cloud when we edit any image like crop and rotate and then save it, the image is not getting updated. After analyzing I could see there is one node "dam:failedRenditions" getting created inside "jcr:content" of the image. How can we fix this ?

@arunpatidar can you please help on this.

5 Replies

Avatar

Community Advisor

Hi @KumariSu , Based on the error, it looks like AEM is having trouble generating the renditions due to factors like corrupted images, unsupported image formats, or large image sizes that exceed configured limits. Please check below.

1- DAM Update Asset workflow is triggered when you are saving it.

2- Check the logs in case of failure.

 

You should also refer https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-16874

 

 

Avatar

Level 1

@Pradeep_Kumar_Srivastav I'm on AEM cloud where we don't have the "DAM update asset workflow". I'm getting this issue for all images irrespective of file size and type.

 

In the logs, I'm getting this error :

com.day.cq.dam.core.impl.servlet.ImageModificationServlet error while getting the metadata for asset

Avatar

Community Advisor

Hi @KumariSu , I would suggest to raise a support ticket a Adobe for further investigation. There was a similiar issue in 6.5 and SP2 fixed that. refer https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/error-on-cropping-existing...

Avatar

Level 2

check the DAM Update Asset workflow and ensure it's configured correctly. Also, inspect the error logs for details on why "dam
" is created, and resolve any underlying issues such as permission or processing errors in the workflow.

Avatar

Level 8

@KUMAR any error on the logs and explore below?

- Asset file size and type [supported or not]

- asset microservice /- processing profile config :  Tools > Assets > Processing Profiles. Click Create.

- try to upload using he POST request is POST https://[aem_server]:[port]/content/dam/assets/folder.initiateUpload.json. via postman check error