Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Error messages displayed when uploaded images in AEM Assets

Avatar

Avatar
Validate 1
Level 2
josiahh94050133
Level 2

Likes

0 likes

Total Posts

16 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
josiahh94050133
Level 2

Likes

0 likes

Total Posts

16 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile
josiahh94050133
Level 2

28-05-2019

I'm coming across a strange issue with AEM Assets in 6.4.

Whether I use the Create --> Files option in the ui or drag and drop an image from the local machine into Assets I am seeing the following error:

error.png

However this is for only 1 asset, if I click Ok, I'm then given:

error2.png

If I select Upload, it presents another dialog with a progress bar that does nothing. If I instead select Cancel it closes the dialog.

Despite the above, the asset is uploaded and processed in the DAM. I see after I refresh the current page and it's renditions when I examine the file in crx/de.

Like the above errors, sometimes I see this when uploading an Asset. However the asset in question is brand new and not a duplicate:

duplicate.png

I've tested the above scenarios in a vanilla 6.4 instance (no fix packs or service packs installed), in a 6.4 instance with SP3 and in one with SP4.

All are behaving in the same way with the above errors.

Please advise.

Replies

Avatar

Avatar
Validate 1
Level 2
josiahh94050133
Level 2

Likes

0 likes

Total Posts

16 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
josiahh94050133
Level 2

Likes

0 likes

Total Posts

16 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Affirm 1
View profile
josiahh94050133
Level 2

15-08-2019

Since this issue began we have started the upgrade process to 6.5.1.

After many weeks of verifying, we have yet to come across the issue with that version.

So this is resolved with an upgrade to the latest AEM release.