Publisher: Page load error; Cannot get DefaultSlingScript | Community
Skip to main content
B
Bahar
Level 3
April 12, 2019
Solved

Publisher: Page load error; Cannot get DefaultSlingScript

  • April 12, 2019
  • 4 replies
  • 5192 views

Hello All,

I have a new component in AEM 6.4 which works fine in author/publisher in local.

Also it is fine in author/publisher in dev env. and when I go to QA env. It works and show correctly in author and wcmmode=disabled

But in publisher of QA, I will get this error and Page is not rendering...

org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.SlingException: Cannot get DefaultSlingScript: org.apache.sling.api.scripting.ScriptEvaluationException: java.lang.NullPointerException

Any idea what can be wrong in different environment? Not any more info in log....

(there is this warn before this error: com.day.cq.wcm.webservicesupport.impl.ConfigurationManagerImpl Cloud service /etc/cloudservices/sdltms-translation/SdlTms1 not found)

Thanks for your time

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ravi_Pampana

Hi,

Check if you are referring to any system user and system user is having required permissions in QA publish instance. Also, if you are using any login administrator code to get the session which might be causing the issue.

Try to check the error logs to find the exact line of code which is causing the exception which gives idea about the exception.

4 replies

smacdonald2008
smacdonald2008
Level 10
April 13, 2019

There is something different in that other environment. It could be purhaps not all OSGi bundles are active for example.

Prince_Shivhare
Community Advisor
Prince_ShivhareCommunity Advisor
Community Advisor
April 13, 2019

please check your bundle is active or not.

if no error is coming and still installed state, try to check dependencies in the bundle, are they active?

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity AdvisorAccepted solution
Community Advisor
April 13, 2019

Hi,

Check if you are referring to any system user and system user is having required permissions in QA publish instance. Also, if you are using any login administrator code to get the session which might be causing the issue.

Try to check the error logs to find the exact line of code which is causing the exception which gives idea about the exception.

B
BaharAuthor
Level 3
April 15, 2019

I couldn't figure it out anything more, no more log or specific lines of code. Bundles looked like ok!

Finally we have restart the qa publish environment and it works fine without issue.

Thanks everyone.

Terms & ConditionsAccessibility statement

Loading footer...