Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Load/'create' a pdf file into the Assets side of the AEM

Avatar

Level 1

Hi All, I'm attempting to load/'create' a pdf file into the Assets side of the AEM. It loads to about 97%, then says "0 of 1 assets uploaded". The only option provided is "Cancel". I have loaded pdfs successfully many times, and into this folder as recently as an hour ago. I even deleted the previous version of the pdf rather than "Replace" it, thinking that might be an issue. I was required to "Force Delete" because of some message that I didn't read thoroughly, now I'm thinking that message was the key as to why this pdf won't upload. Any suggestions?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @BelindaBo1

1- When you force delete an asset, sometimes the underlying file or its associated metadata might still be locked or partially deleted. This can cause issues when you try to upload a new version. Or the "Force Delete" operation may not have fully cleared all references or dependencies of the previous file. This can leave behind orphaned records in the repository, preventing a new file from being uploaded.

You can try to manually check if any remnants of the previous PDF still exist in the repository in crx/de.

Delete them manually and try uploading the PDF again.

2- Sometimes the AEM repository or internal cache might become inconsistent, especially after forced deletions. You have to restart AEM or If you are using a dispatcher in front of AEM, Clear Dispatcher Cache.

3- Check AEM Server Logs for specific errors.

 

View solution in original post

5 Replies

Avatar

Correct answer by
Community Advisor

Hi @BelindaBo1

1- When you force delete an asset, sometimes the underlying file or its associated metadata might still be locked or partially deleted. This can cause issues when you try to upload a new version. Or the "Force Delete" operation may not have fully cleared all references or dependencies of the previous file. This can leave behind orphaned records in the repository, preventing a new file from being uploaded.

You can try to manually check if any remnants of the previous PDF still exist in the repository in crx/de.

Delete them manually and try uploading the PDF again.

2- Sometimes the AEM repository or internal cache might become inconsistent, especially after forced deletions. You have to restart AEM or If you are using a dispatcher in front of AEM, Clear Dispatcher Cache.

3- Check AEM Server Logs for specific errors.

 

Avatar

Level 2

Hi @BelindaBo1 

  • Ensure the PDF file is not corrupted or damaged. Try opening it in a PDF viewer to verify its integrity.
  • Check the file size and ensure it's within the allowed limits in AEM.
  • If the file is large, try compressing it or splitting it into smaller files.
  • Double-check the folder permissions and ensure you have the necessary rights to upload assets.
  • Verify that the folder structure is correct and the folder is not locked or restricted.
  • Since you've already force-deleted the previous version, try uploading the new PDF file again.
  • If you're still facing issues, try deleting the folder and recreating it, then upload the PDF file.

Avatar

Level 1

Hi arunpatidar

 

It was 574kB but I compressed it to 114kB and it uploaded successfully. I don't thnk file size was the issues, though, I suspect it was a caching issue in the AEM. In any event, it is working now, so all is well. Thank you for your interest.

Avatar

Administrator

@BelindaBo1 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni