Expand my Community achievements bar.

SOLVED

AEM Launch is faling in preview mode

Avatar

Level 2

Hi, 

 

I am getting the below error while doing a preview of the AEM launch. Can anyone help?

 

org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: Operands are not of the same type: the equality operator can only be applied to String, Number and Boolean types.

Cannot serve request to /content/launches/2021/02/04/2021_s_hp_marwk2spring/content/launches/2021/01/29/2021_s_hp_marwk1/content/launches/2021/01/19/2021_s_hp_febmarwk4personaday/content/launches/2021/01/07/2021_s_hp_febwk2presidentsday/content/launches/2020/12/02/2020_s_hp_decwk3mongiftingcode/content/launches/2020/11/20/2020_s_hp_decwk3gifting/content/launches/2020/11/03/2020_s_hp_novwk3blackfridaypreviewactual/content/launches/2020/10/09/2020_s_hp_nov_veteransday0/content/launches/2020/10/01/20201004_s_hp_octwk12searsdaysdynamic/content/launches/2020/09/14/20201004_s_hp_octwk12searsdays/content/launches/2020/07/04/20200705_s_hp_junewk5/content/shc/sears/us/en.html on this server

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6.5
1 Accepted Solution

Avatar

Correct answer by
Level 2

I think it was my one of component that was failing it and that was causing it. Removing the component resolved the issue. Now I know at least the culprit component.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

I think it was my one of component that was failing it and that was causing it. Removing the component resolved the issue. Now I know at least the culprit component.