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

Getting "No resource found" error on publish environment

Avatar

Avatar
Validate 1
Level 1
mattk4043901
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
mattk4043901
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
View profile
mattk4043901
Level 1

04-05-2016

I've just set up a publish environment (port 4503), and I've Activated all of my content (/content/...,  /content/dam/...,  /apps/...,  /etc/Designs/...)  The homepage looks great on publish, but if I try and view a child page I get a "No resource found  Cannot serve request to /content/site-name/en/news.html on this server".  If I hit the same URL replacing ".html" with ".json" or ".infinity.json" I get a listing of all the content, and I can login to the /siteadmin on the publish site and see the pages there, so I know the content is there.  But there seems to be a rendering component that is missing.

The logs aren't much help:

GET /content/site-name/en/news.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
org.apache.sling.api.resource.ResourceNotFoundException: No resource found

 

Thanks for your time.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 50
Level 5
askdctm
Level 5

Likes

47 likes

Total Posts

476 posts

Correct Reply

7 solutions
Top badges earned
Validate 50
Validate 25
Validate 10
Validate 1
Boost 5
View profile

Avatar
Validate 50
Level 5
askdctm
Level 5

Likes

47 likes

Total Posts

476 posts

Correct Reply

7 solutions
Top badges earned
Validate 50
Validate 25
Validate 10
Validate 1
Boost 5
View profile
askdctm
Level 5

05-05-2016

HI Matt,

Just some pointers that might help.

1] Appending ?wcmmode=disabled to page in author instance is the closest resemblance we can have to publish environment. Does issue appear even then.

2] Also, looks like one particular component is causing this to happen. Anyway you can narrow that down.

3] What happens if you create a package of that page and put it on publish instance. Is it the same behavior.

Answers (4)

Answers (4)

Avatar

Avatar
Level 1
PAOER_terki5
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
PAOER_terki5
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
PAOER_terki5
Level 1

16-04-2020

في واحد سرق الحساب حقي وانا ما ادري وش اسوي طيب الي أبغاه منكم ترجعلي ايا والله اني دافع اكثر من ٥ دولار تكفون رجعو حسابي والله اني قاعد ابكي تكفون

 

Avatar

Avatar
Validate 1
Level 5
Tuhin_Ghosh
Level 5

Likes

36 likes

Total Posts

301 posts

Correct Reply

40 solutions
Top badges earned
Validate 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
Level 5
Tuhin_Ghosh
Level 5

Likes

36 likes

Total Posts

301 posts

Correct Reply

40 solutions
Top badges earned
Validate 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
Tuhin_Ghosh
Level 5

05-05-2016

Hi Matt,

Kindly close this ticket and mark this as resolved since your issue is already solved.

Thanks

Tuhin

Avatar

Avatar
Validate 1
Level 1
mattk4043901
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
mattk4043901
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
View profile
mattk4043901
Level 1

05-05-2016

Thanks for the response.  We figured it out - it was because the footer parsys had no content, and the child pages were referencing the footer resource.  We weren't doing a proper check to see if there were any child nodes when referencing the footer component.  The author instance was not showing the footer if wcmmode was anything but disabled on the child pages, which is why we only saw the problem on the publish instance.

Your #1 suggestion above did in fact cause the problem on authoring, and we narrowed it down to the footer component.

Thanks for your help,

Matt

Avatar

Avatar
Validate 100
Level 6
GK-AEM
Level 6

Likes

40 likes

Total Posts

482 posts

Correct Reply

32 solutions
Top badges earned
Validate 100
Validate 50
Validate 25
Validate 10
Validate 1
View profile

Avatar
Validate 100
Level 6
GK-AEM
Level 6

Likes

40 likes

Total Posts

482 posts

Correct Reply

32 solutions
Top badges earned
Validate 100
Validate 50
Validate 25
Validate 10
Validate 1
View profile
GK-AEM
Level 6

05-05-2016

Is this happening only for this child page only or all other child pages as well?

What about the behavior in author?

Please check all required code is there in publish environment or not.

Responsible component for this page is no referring properly.