Publisher: Page load error; Cannot get DefaultSlingScript

Avatar

Avatar

Bahar

Avatar

Bahar

Bahar

12-04-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Ravi_Pampana

MVP

Avatar

Ravi_Pampana

MVP

Ravi_Pampana
MVP

12-04-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.

Answers (3)

Answers (3)

Avatar

Avatar

Bahar

Avatar

Bahar

Bahar

15-04-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.

Avatar

Avatar

Prince_Shivhare

Avatar

Prince_Shivhare

Prince_Shivhare

12-04-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?

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

12-04-2019

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