Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

dam folder

Avatar

Former Community Member

Hi,

We see that whenever we upload some assets to AEM DAM using DAM Admin it is creating a redundant empty folder(Upper Case) under the same path .To elaborate more on the issue.It is happening for all types of assets like pdf,image,doc etc.

1-Suppose I am uploading a asset named lxk_mfg_ghs-printing-and-publishing_solutionsheet.pdf to the DAM under /content/dam/testfolder/documents/brochures/y2015.

2-After uploading the asset it creates a Folder named LXK_MFG_GHS-PRINTING-AND-PUBLISHING_SOLUTIONSHEET.PDF under /content/dam/testfolder/documents/brochures/y2015.

3-It is not happening for all assets but for few of the assets.So at this point we are not sure what is causing this to create a folder.

Please let us know if an one else has encountered this.Any help on this would be highly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Level 10

I tried replicating the same. 

Created a pdf file with the name 'Lexmark_Perceptive_Mobile_Capture_SDK-Solution-Sheet.pdf' . uploaded the file using /damadmin

It created the asset node properly without any issue.

Can you please give the steps you are following ?

Is this happening for any files that you upload or only for few ?

View solution in original post

9 Replies

Avatar

Former Community Member

Hi The asset lexmark_perceptive_mobile_capture_sdk-solution-sheet.pdf was uploaded to DAM and it created a foler named Lexmark_Perceptive_Mobile_Capture_SDK-Solution-Sheet.pdf under the same location where asset was uploaded.Below is the log snipper form error.log

15.04.2015 17:21:00.884 *ERROR* [172.31.250.215 [1429132860840] POST /content/dam/lexmark/documents/brochures/y2015/Lexmark_Perceptive_Mobile_Capture_SDK-Solution-Sheet.pdf/jcr:content/metadata.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException java.net.MalformedURLException: base file:/tmp/fonts.82df1454-065e-4510-8e79-30be6b14a475/ is not a valid directory
    at org.apache.fop.apps.FOURIResolver.checkBaseURL(FOURIResolver.java:98)
    at org.apache.fop.apps.FopFactory$1.setFontBaseURL(FopFactory.java:160)
    at org.apache.fop.apps.FopFactory.setFontBaseURL(FopFactory.java:376)
    at com.day.cq.rewriter.xml.fop.FOPNGSerializer.init(FOPNGSerializer.java:83)
    at org.apache.sling.rewriter.impl.PipelineImpl.init(PipelineImpl.java:126)
    at org.apache.sling.rewriter.impl.ProcessorManagerImpl.getProcessor(ProcessorManagerImpl.java:445)
    at org.apache.sling.rewriter.impl.RewriterResponse.getProcessor(RewriterResponse.java:172)
    at org.apache.sling.rewriter.impl.RewriterResponse.getWriter(RewriterResponse.java:110)
    at org.apache.sling.servlets.post.HtmlResponse.doSend(HtmlResponse.java:114)
    at org.apache.sling.servlets.post.AbstractPostResponse.send(AbstractPostResponse.java:376)
    at org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:219)
    at org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
    at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
    at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
    at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:508)
    at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
    at com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:146)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
    at com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:356)
    at com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:168)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
    at com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:96)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
    at org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:254)
    at org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
   

Avatar

Level 10

Hi,

can you give the snapshot of the logs ?

Also, it looks like a bug. please do raise a support ticket aswell

Avatar

Level 10

I think, this error you are seeing because its creating a folder instead of the dam asset node

Avatar

Former Community Member

Our concern is why is it creating a redundant folder.Any clue will be highly appreciated.

Avatar

Community Advisor

Hi,

Can you also check the status of the workflow that gets fired when you upload the asset?, also make sure you don't have any unnecessary workflow launchers configured 

Also I have one question, does it create a valid asset node? or it simply creates the redundant folder with asset name?

- Runal

Avatar

Correct answer by
Level 10

I tried replicating the same. 

Created a pdf file with the name 'Lexmark_Perceptive_Mobile_Capture_SDK-Solution-Sheet.pdf' . uploaded the file using /damadmin

It created the asset node properly without any issue.

Can you please give the steps you are following ?

Is this happening for any files that you upload or only for few ?

Avatar

Former Community Member

I go to DAM Admin and upon selecting the folder where my asset to be placed -New File->browse the asset from my local to upload.

This is the step i follow to upload.

Avatar

Former Community Member

This is happening for few assets not for all.

Avatar

Former Community Member

Workflows are fine and yes it creates a redundant empty folder .