org.osgi.framework.ServiceException: Service factory returned null | Community
Skip to main content
N
NarayanaCh
Level 3
December 27, 2022
Solved

org.osgi.framework.ServiceException: Service factory returned null

  • December 27, 2022
  • 1 reply
  • 3615 views

Hello,

 

We are seeing below error in the logs after upgrading to SP14, anyone else is facing similar issues with Service Pack upgrade? Unable to reproduce in my local instance its only happening on actual servers.

27.12.2022 09:29:27.961 *ERROR* [FelixDispatchQueue] org.apache.sling.adapter FrameworkEvent ERROR (org.osgi.framework.ServiceException: Service factory returned null. (Component: com.day.cq.dam.core.impl.DamAdapterFactory (1491)))
org.osgi.framework.ServiceException: Service factory returned null. (Component: com.day.cq.dam.core.impl.DamAdapterFactory (1491))

Also noticed seeing an empty side panel where we used to see assets 

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 NarayanaCh

I have noticed below error in the error.log

27.12.2022 15:51:36.152 *WARN* [127.0.0.1 [1672181496136] POST /libs/wcm/core/content/reference.json HTTP/1.0] 
org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 
'commerce-reader-service' is not a known JCR system user id and therefore not allowed in the 
Sling Service User Mapper.

 Based on that I have created system user "commerce-reader-service" then it started working

1 reply

N
NarayanaChAuthorAccepted solution
Level 3
December 27, 2022

I have noticed below error in the error.log

27.12.2022 15:51:36.152 *WARN* [127.0.0.1 [1672181496136] POST /libs/wcm/core/content/reference.json HTTP/1.0] 
org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 
'commerce-reader-service' is not a known JCR system user id and therefore not allowed in the 
Sling Service User Mapper.

 Based on that I have created system user "commerce-reader-service" then it started working

    Terms & ConditionsAccessibility statement

    Loading footer...