Documentation Center

Troubleshooting Experience Manager problems

This task presents steps to check if your Experience Manager setup is not working properly.

Procedure

  1. Check your cd_preview.log for the following:
    Request for path 'RELATIVEPATH' was found to match the configured excludedPath: 'EXCLUDEDPATH'.

    where RELATIVEPATH is the path to a webpage that does not work with Experience Manager, and EXCLUDEDPATH is some string.

  2. If you find the above message, check your cd_ambient_conf.xml for the ExcludedPaths section, and comment out any Path elements that match the URL of a webpage you want to make editable.
  3. In your Session-enabled Content Service location on the server, check the following (your log level is assumed to be set to DEBUG):
    1. In cd_storage_conf.xml, verify that SessionWrapper is listed among the wrappers.
    2. In cd_storage_conf.xml, verify that Preview_dao_bundle.xml is listed among the storage bindings.
    3. In cd_ambient_conf.xml, verify that WhiteList is enabled and that the IP address that is making requests is within the configured IP range. To allow any IP, set the range to <Ip>0.0.0.0-255.255.255.255</Ip>
    4. In cd_ambient_conf.xml, verify that in the <GloballyAcceptedClaims> section, there's a Claim with its Uri attribute set to taf:session:preview:preview_session.
    5. In cd_ambient_conf.xml, verify the presence of the two Preview Cartridges: <Cartridge File="cd_webservice_preview_cartridge.xml" Category="SYSTEM"/> and <Cartridge File="cd_webservice_preview_cartridge.xml"/>
    6. In cd_core.log, ensure the presence of the line: DEBUG AbstractAmbientDataServletFilter - Cookie forwarding is enabled: true
    7. In cd_core.log, ensure the presence of the line: DEBUG AbstractAmbientDataServletFilter - Cookie forwardingforcurrent request is allowed: true
    8. In cd_core.log, ensure the presence of the line: DEBUG ClaimCookieDeserializer - Found NUMBER claims cookies. where NUMBER is some number. You should not see the line: DEBUG ClaimCookieDeserializer - The list of ClaimsCookies sent to be deserialized is empty!
  4. In your Preview Service location on the server, check the following:
    1. In cd_storage_conf.xml, verify that SessionWrapper is listed among the wrappers.
    2. In cd_storage_conf.xml, verify that Preview_dao_bundle.xml is listed among the storage bindings.
    3. In cd_ambient_conf.xml, verify the presence of the two Preview Cartridges: <Cartridge File="cd_webservice_preview_cartridge.xml" Category="SYSTEM"/> and <Cartridge File="cd_webservice_preview_cartridge.xml"/>
  5. In the Session Preview database, verify that when you select Update Preview in Experience Manager, there is data in the PREVIEW_SESSIONS or PREVIEW_SESSION_ITEMS table.
  6. If your staging website runs as a Java web application, also check the following:
    1. In cd_client_conf.xml, verify that your cache is disabled.
    2. In cd_client_conf.xml, verify the presence of a PreviewService element with the MachineName, FileLocation and DefaultFileSystem attributes set.
    3. In cd_ambient_conf.xml, verify that the <ForwardedClaims> section is enabled and contains a Claim with its Uri attribute set to taf:session:preview:preview_session.
    4. Verify that there is a web.xml file at the same level as the classes/ directory.
    5. In this web.xml file, ensure that PageContentFilter is enabled and set to com.sdl.web.preview.client.filter.ClientPageContentFilter.
    6. In this web.xml file, ensure that BinaryContentFilter is enabled and set to com.sdl.web.preview.client.filter.ClientBinaryContentFilter.
    7. The logs contain the following line: ForwardedClaims is configured. Will forward following claims: LISTOFCLAIMS, where LISTOFCLAIMS contains taf:session:preview:preview_session.