Working document to gather common issues and possible solutions. (AEM 5.6.1 and 6.0) Please let me know if you have explanations for any of these issues.
General Advice:
- check all logs (make sure to check them on the correct instancce if there's more than one)
- restart/reload/update bundle
- restart instance
- delete /var/classes and /var/clientlibs
Edit button doesn't show up.
Solutions:
- the only thing that helped for me is re-install the instance.. (bug?)
(Pretty generic error that can have a lot of reasons...)
- "Installation on http://localhost:4502/apps/abc/install failed, cause: Installation failed" --> 'install' folder doesn't exist yet so the jars can't be pushed to the instance. Create folder manually in CRXDE Lite.
Solutions:
- Component does not have a dialog or cq:editConfig (must have at least one of these), or the dialog.xml/_cq_editConfig.xml is malformed
- Component is '.hidden'
- Component is not allowed for current page / parsys / etc.
- The design's "components" list is malformed (missing commas "," between components, has whitespace in it, etc)
- There is no cq:designPath set on the site's root page (e.g. /content/mysite) or the page isn't able to inherit this property from the root page (e.g. because it's nested in a folder)
Solutions:
- clear local storage in browser since it might have old references to it if it was deleted in a different tab
Never really found out why this happened.. Solution for now: Use favicon from DAM instead of /etc or upload to CRXDE directly.
Vault might not have pushed your changes to CRX. Make sure there is no XML errors in any of the files you're building. (Example: & -> &)
org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource SyntheticResource
Resource/Component doesn't exist. Check resource path.
org.apache.sling.servlets.resolver.internal.SlingServletResolver Calling the error handler resulted in an error java.lang.Error: Unresolved compilation problems: Only a type can be imported. com.adobe.acs.commons.errorpagehandler.ErrorPageHandlerService resolves to a package ErrorPageHandlerService cannot be resolved to a type ErrorPageHandlerService cannot be resolved to a type
- Make sure bundle is active
- Make sure bundle actually exports this class/service
- Try deleting
/var/classes/*to force recompilation (or via/system/console/slingjsp)
- Check: Does it show up on Author/Publish?
- Check: Is there Redirects set on the Dispatcher?
- Maven dependency included?
- set header directly on Dispatcher and/or CDN
- use Varnish? (see here)
campaigns.length seems to be 0
- check that campaigns is actually part of your client context configuration
- any personalization components included that shouldn't be there? hit "Target" by accident?
- is the client context (cq/personalization/components/clientcontext) compoentn properly included?
"com.adobe.granite.xss.impl.HtmlToHtmlContentContext AntiSamy warning: The a tag contained an attribute that we could not process. The adhocenable attribute has been filtered out, but the tag is still in place. The value of the attribute was "false"."
- Depending on which attribute it's complaining about, you might want to see where it's coming from.
- If it should be allowed, like target="_blank", simply add it to your AntiSamy config (/libs/cq/xssprotection/config.xml, copied to /apps of course)
Whenever you try to edit a page and enter the /editor.html/path/to/page.html it throws a 404 error.
- For me there was a folder node "editor.html" under "/libs/wcm/core/content" that prevented the actual "editor" node from loading.
- As far as I can see the reason for this is: when you don't have a campaign selected but click "+" it creates this fake node because it doesn't know where to save the new experience. Bug?
....JasperException: The absolute uri: http://abc.com/taglibs cannot be resolved in either web.xml or the jar files deployed with this application
- does taglib bundle exist and is active?
- Check console, see if AEM can read the "....permissions.json?path=...". If it's a 404, call that page and see what it returns. For me, a "jcr:content" node was missing.
- This was a weird one, I'm not sure what exactly went on but whenever I put in a real email address [email protected], it would return a "302 Found" instead of the normal "200 OK" when ajax posting to my servlet. It was fixed when I took out ":formid" and ":formstart"
- make sure you added authentication headers if needed
- Either check "Allow Empty" in "Apache Sling Referrer Filter" OSGi config or set a proper referrer header in Postman
Targeted component: simulation doesn't work but selecting the campaign and experience in the client context works
- This happened for me when I was just trying to test some segments on the Geometrixx site. Turns out they have to be under their respective site (ie. '/etc/segmentation/geometrixx-outdoors'), I had them under another folder. They showed up when I created the experiences but then the connection wasn't made properly.
- Adobe's Maven repository seems to have issues some times, try a different source :)
- check that the artifact actually exists by navigating to it in your browser
Some approaches:
- "mvn eclipse:eclipse"
- On the project, do "Maven" > "Reimport"
- "File" > "Invalidate Caches / Restart"
- does dependency exist in OSGi container? If not, try embedding it.
- try moving up/down the dependecies that have conflicts
j_security_check returns 403 / User login does not work / Error in logs: org.apache.sling.auth.core.impl.SlingAuthenticator handleSecurity: AuthenticationHandler did not block request; access denied
- In our case a 301 redirect messed with the headers so the auth headers didn't make it through.
For me one of the items in my dialog was simply missing "jcr:primaryType="nt:unstructured" but stepping through each field to make sure it can be parsed properly definitely helps.
Cookie does not show up even when it looks correct in the response headers. Possible solutions:
- Add Cookie to "Adobe Granite Opt-Out Service" OSGi config
- Don't set "Domain" in Cookie
- setSecure(true) set on http traffic
For me the problem was that I had a comment at the beginning of this config file: /etc/workflow/models/translation/translation_rules.xml
Apparently AEM can't handle it and fails without error. Make sure to put any comments inside the <nodelist>.
- Check if event is even happening:
/system/console/events - Is EventHandler registered?
- EventHandler might be "blacklisted", check:
org.apache.felix.eventadmin.impl.EventAdminconfig
There's a permission for contributors on root (/) that denies read access to rep:glob=apps/*/config/* which means that out-of-the-box, authors in this group won't have access to the config node under your cq:inplaceEditing node (_cq_editConfig.xml) for your components. According to Adobe, this is a security feature.
Problem when publishing: Failed to retrieve references for the selected page. / NullPointerException in ContentPolicyReferenceProvider
Seen in AEM 6.2 SP1. For me, it was a cq:policy property that was pointing to a policy that didn't exist (anymore?): wcm/foundation/components/responsivegrid/policy_1487706890435
As seen via top command, the io wait wa is constantly above 30%.
In our case, it was related to MSM rollouts that got messed up somehow so they bogged down the system. We noticed this by looking at the events via /system/console/events
Only solutions I've found were faking a change and deploying it so that AEM realizes there's a change OR restarting the Apache Sling Internationalization Support (org.apache.sling.i18n) bundle.
Error:
[ERROR] Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.5.1:install (install-content-package) on project aem-view: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Solution: Add -Dvault.relaxedSSLCheck=true to mvn command.
SAML request to /saml_login returned 403 Forbidden when the user was already logged in. Only happened when config was installed via config.author folder and not when the config is manually saved in the configMgr.
- Make sure all config values have the right type:
{Boolean},{Long},[] - For me one issue was that
service.rankingshouldn't be included in the config at all because then it got ranked lower in the list of authentication handlers (see/system/console/slingauth). Needs to be above the Token Authentication Handler to work. Check/system/console/eventsforLOGINevents and see what authenticator is used.
Problem in my case was that the root /content/* resource wasn't replicated so when it traversed up the three it caused a NullPointerException.