sling error 404 | Community
Skip to main content
J
jrough
Level 2
October 16, 2015
Solved

sling error 404

  • October 16, 2015
  • 5 replies
  • 2815 views

I am still trying to get my server back.  I imported my packages  and installed them. Now I can't get to my login page.  There is the below sling error 404.   Why is there a sling error? The default .html extension is active.  Could it be a java error?   My setup is pointed to a Felix dev box.  I double checked that configuration.  If Felix was wrong then it wouldn't be serving it right?   I reloaded the packages and installed them again one by one.  In the package manager it says they were last built a month ago so I did not rebuild them.  I noticed the Geometrix site comes up but the Admin page doesn't?  I don't know why?

Thanks,

ng filter: org.apache.sling.bgservlets.impl.BackgroundServletStarterFilter 15 (2014-11-13 16:52:38) LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter 15 (2014-11-13 16:52:38) LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.designimporter.CanvasPageDeleteRequestFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.core.impl.WCMRequestFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.adobe.granite.optout.impl.OptOutFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.theme.impl.ThemeResolverFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.foundation.forms.impl.FormsHandlingServlet 15 (2014-11-13 16:52:38) LOG Calling filter: org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter 15 (2014-11-13 16:52:38) LOG RedirectFilter did not redirect (MobileUtil.isMobileResource() returns false) 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.core.impl.warp.TimeWarpFilter 15 (2014-11-13 16:52:38) LOG Applying Componentfilters 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.core.impl.WCMComponentFilter 15 (2014-11-13 16:52:38) LOG Calling filter: com.day.cq.wcm.core.impl.WCMDebugFilter 15 (2014-11-13 16:52:38) TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0} 15 (2014-11-13 16:52:38) TIMER_END{0,org.apache.sling.servlets.get.DefaultGetServlet#0} 15 (2014-11-13 16:52:38) LOG Applying Error filters 15 (2014-11-13 16:52:38) LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter 15 (2014-11-13 16:52:38) TIMER_START{handleError:status=404} 15 (2014-11-13 16:52:38) TIMER_END{0,handleError:status=404} Using handler /libs/sling/servlet/errorhandler/404.jsp 17 (2014-11-13 16:52:38) LOG Found processor for post processing ProcessorConfiguration: {contentTypes=[text/html],order=-1, active=true, valid=true, processErrorResponse=true, pipeline=(generator=Config(type=htmlparser, config={}), transformers=(Config(type=linkchecker, config={}), Config(type=mobile, config=org.apache.sling.jcr.resource.JcrPropertyMap@347f98a), Config(type=mobiledebug, config=org.apache.sling.jcr.resource.JcrPropertyMap@6a4fd4b4), Config(type=contentsync, config=org.apache.sling.jcr.resource.JcrPropertyMap@1f15abf3), serializer=Config(type=htmlwriter, config={}))} 20 (2014-11-13 16:52:38) TIMER_END{20,Request Processing} Dumping SlingRequestProgressTracker Entries
Best answer by jrough

okay, thanks to all.  My cq5 server was down for almost 20 days :-( but it is back up now.  Our technical staff was having a baby & on vacation.  REally bad.  It just got solved.  It was some international configuration I didn't know about.  I installed everything right.  REally weird because I was getting different results and doing the same thing.  Its fixed now and since I'm a new cq5 user/admin it has been sink or swim, mostly sink.  thanks again.

5 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

Is it author or publish instance.

Use browser private window & verify.

Admin page means which one?

J
jroughAuthor
Level 2
October 16, 2015

Yes it is the same error in Incognito browser window.  The admin screen that comes up with AEM.  However I get the sling error.  I did re-install my packages.  That is all.  CRXde works, pkg manager works.  It is author.

 

0 (2014-11-14 09:21:10) TIMER_START{Request Processing} 0 (2014-11-14 09:21:10) COMMENT timer_end format is {<elapsed msec>,<timer name>} <optional message> 0 (2014-11-14 09:21:10) LOG Method=GET, PathInfo=/content/XXcom/XX/xx/xx/login.html 0 (2014-11-14 09:21:10) TIMER_START{ResourceResolution} 3 (2014-11-14 09:21:10) TIMER_END{3,ResourceResolution} URI=/content/xxcom/xx/xx/xx/login.html resolves to Resource=, type=sling:nonexisting, path=/content/XXXcom/base/xx/xx/login.html, resource=[NonExistingResource, path=/content/XXcom/base/xx/xx/login.html] 3 (2014-11-14 09:21:10) LOG Resource Path Info: SlingRequestPathInfo: path='/content/xxcom/xx/xx/xx/login.html', selectorString='null', extension='html', suffix='null' 3 (2014-11-14 09:21:10) TIMER_START{ServletResolution} 3 (2014-11-14 09:21:10) TIMER_START{resolveServlet(, type=sling:nonexisting, path=/content/xxcom/xxx/xx/xx/login.html, resource=[NonExistingResource, path=/content/xxcom/xxx/xx/xx/login.html])} 20 (2014-11-14 09:21:10) LOG {0}: no servlet found

Thanks

vikramca06
vikramca06
Level 4
October 16, 2015

There might be an issue in starting the bundles. Check the felix console and start the necessary bundles

J
jroughAuthorAccepted solution
Level 2
October 16, 2015

okay, thanks to all.  My cq5 server was down for almost 20 days :-( but it is back up now.  Our technical staff was having a baby & on vacation.  REally bad.  It just got solved.  It was some international configuration I didn't know about.  I installed everything right.  REally weird because I was getting different results and doing the same thing.  Its fixed now and since I'm a new cq5 user/admin it has been sink or swim, mostly sink.  thanks again.

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
January 19, 2025

A 404 error in Sling indicates the resource isn't found. Here’s what to check:

  1. Check URL: Ensure the correct URL and path for the page/resource.
  2. Rebuild & Redeploy Packages: Rebuild and redeploy your packages to ensure content and templates are correctly deployed.
  3. Permissions: Verify permissions for the admin page, as this might be blocking access.
  4. Felix Configuration: Double-check Felix settings to ensure proper service configuration.
  5. Check Logs: Look at Sling logs (sling.log) for additional errors.
  6. Dispatcher Cache: Clear dispatcher cache if using one, to avoid serving outdated content.
  7. Verify JCR Resource: Ensure the resource exists in JCR via CRX Explorer.

Rebuild and verify configuration, then test with a basic page to isolate the issue.

Terms & ConditionsAccessibility statement

Loading footer...