javax.jcr.PathNotFoundException thrown while rendering PDF using formService | Community
Skip to main content
Level 3
February 4, 2026
Question

javax.jcr.PathNotFoundException thrown while rendering PDF using formService

  • February 4, 2026
  • 1 reply
  • 15 views

Hi,

I am facing an issue while rendering PDF from XDP template, for just 1 form.

The issue is that, at the time of calling formsService.renderPDFForm("crx://" + xdpPath, xmlDataDocument, renderOptions);

I see this error, for all the fragments associated to this form:

Error creating FileDataBuffer from URL crx:///content/dam/formsanddocuments/Fragment/frag_logo.xdpjava.io.IOException: Error of type 'javax.jcr.PathNotFoundException' thrown on attempting operation 'CONNECT' on URL 'crx:/content/dam/formsanddocuments/Fragment/frag_logo.xdp'. Message = [Node with path /content/dam/formsanddocuments/Fragment/frag_logo.xdp does not exist.]	at com.adobe.aemds.datamanager.impl.AbstractUrlConnection.connect(AbstractUrlConnection.java:67) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.UrlUtil.doOpenUrlStream(UrlUtil.java:98) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.UrlUtil.access$000(UrlUtil.java:41) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.UrlUtil$1.call(UrlUtil.java:112) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.UrlUtil$1.call(UrlUtil.java:109) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.granite.resourceresolverhelper.impl.ResourceResolverHelperImpl.callWith(ResourceResolverHelperImpl.java:65) [com.adobe.granite.resourceresolverhelper:1.0.4]	at com.adobe.aemds.datamanager.impl.UrlUtil.openUrlStream(UrlUtil.java:109) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.UrlUtil.createFileDataBufferFromUrl(UrlUtil.java:142) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.aemds.datamanager.impl.DataManagerImpl.createFileDataBufferFromUrl(DataManagerImpl.java:215) [adobe-aemds-core-bmc:3.0.144]	at com.adobe.service.DataManagerPOATie.createFileDataBufferFromUrl(DataManagerPOATie.java:104)	at com.adobe.service.DataManagerPOA._invoke(DataManagerPOA.java:137)	at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:301) [adobe-aemds-core-bmc-orb:3.0.144]	at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:604) [adobe-aemds-core-bmc-orb:3.0.144]	at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:747) [adobe-aemds-core-bmc-orb:3.0.144]Caused by: javax.jcr.PathNotFoundException: Node with path /content/dam/formsanddocuments/Fragment/frag_logo.xdp does not exist.

I have checked the XDP file, and it is referencing fragments, exactly the same way as other working forms.

I checked crxde, and the reference property also shows the correct association to the fragments, but at the time of rendering the PDF; the fragments are searched for in this location: /content/dam/formsanddocuments/Fragment/

The fragments are actually placed /content/dam/formsanddocuments/FOFO/Fragment.

Can anyone please guide me on how the renderPDFForm is getting the associated fragment path from XDP template. Thank you

1 reply

SmrithiGoAuthor
Level 3
February 4, 2026

The issue got fixed, when we resaved the XDP template, on my local machine, without any changes and then reuploading it back on AEM. Wondering if there is any hidden path in XDP, when we save using designer. Has anyone experienced this before.