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

Getting error org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html

Avatar

Level 2

19.08.2015 18:31:19.678 *ERROR* [0:0:0:0:0:0:0:1 [1440009079675] GET /etc/replication/agents.publish.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=cq:Page, superType=null, path=/content/asset-share-portal/en_us/errors

Any of the page is not opening and giving the error DefaultGetServlet 'No renderer for extension html'. Nothing was opening. We checked all content and pages were there..

1 Accepted Solution

Avatar

Correct answer by
Level 2

We finally tried looking into various service settings and found:

It happen due to settings in Apache Sling Resource Resolver Factory settings under Felix configMgr is tampered. We faced this issue and found that the setting for Resource Search Path is missing all entry. Verify the default entry should have following:

/aps

/libs

/apps/foundation/components/primary

/libs/foundation/components/primary

View solution in original post

4 Replies

Avatar

Correct answer by
Level 2

We finally tried looking into various service settings and found:

It happen due to settings in Apache Sling Resource Resolver Factory settings under Felix configMgr is tampered. We faced this issue and found that the setting for Resource Search Path is missing all entry. Verify the default entry should have following:

/aps

/libs

/apps/foundation/components/primary

/libs/foundation/components/primary

Avatar

Former Community Member

We have similar problem:

02.05.2016 16:22:29.536 *ERROR* [172.18.138.10 [1462198941448] GET /content/bla/bla/de.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=nt:unstructured, superType=null, path=/content/bla/bla/de/jcr:content/footer/morelinks/link_0_copy

We checked Apache Sling Resource Resolver Factory and found exactly the 4 entries mentioned above in the Resource Search Path.

More recommendations, how to solve this problem?

Avatar

Level 1
@Deleted Account Did you check if your link_0_copy node has sling:resourceType property set?

Avatar

Level 1

I didn't find the solution for this issue but I'm not sure why Rohan's answer was marked as correct when it doesn't resolve the issue.

I went to

http://localhost:4502/system/console/configMgr

and confirmed that the above is already in the Apache Sling Resource Resolver Factory.

999054_pastedImage_1.png

Has anyone came across a solution to this issue?