com.day.cq.wcm.msm.impl.RolloutConfigManagerFactoryImpl RolloutConfig /libs/msm/wcm/rolloutconfigs/activate is invalid: Failed to resolve Factory with id rep:policy, maybe Service is uninstalled | Community
Skip to main content
V
vaibhavjain302
August 26, 2022
Solved

com.day.cq.wcm.msm.impl.RolloutConfigManagerFactoryImpl RolloutConfig /libs/msm/wcm/rolloutconfigs/activate is invalid: Failed to resolve Factory with id rep:policy, maybe Service is uninstalled

  • August 26, 2022
  • 3 replies
  • 1799 views

I am getting the below error many times in logs

com.day.cq.wcm.msm.impl.RolloutConfigManagerFactoryImpl RolloutConfig /libs/msm/wcm/rolloutconfigs/activate is invalid: Failed to resolve Factory with id rep:policy, maybe Service is uninstalled

Does any one know the reason, using AEM 6.5

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 joerghoh

Please file an issue with Adobe support, it looks like that this logic tries to handle all child nodes as rollout configs, even child nodes with a special meaning. 

3 replies

Manu_Mathew_
Community Advisor
Manu_Mathew_Community Advisor
Community Advisor
August 27, 2022

@vaibhavjain302 seems this is addressed here ref. 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/error-while-creating-a-custom-rollout-option/m-p/442355

 

    V
    vaibhavjain302Author
    August 29, 2022

    Hi @manu_mathew_ 

    Thanks for the update, 

    In the reference link, error is showing up in logs for a node for which we have a liveAction or liveActionName.
    But in my case the error is coming as we need some permissions for the node and a rep:policy node is generated, i dont have any liveAction for rep:policy node as such and AEM is treating this rep:policy node as well like an OSGI service

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      August 29, 2022

      Please file an issue with Adobe support, it looks like that this logic tries to handle all child nodes as rollout configs, even child nodes with a special meaning. 

        V
        VENUGOPALCH1
        May 21, 2024

        Hi,

         

        i am having same issue. here rollout config is always null and rolloutconfigManager is always not satisfied in component reference.

        Any solution to this? and i have aem sdk - 

        2023.12.14697.20231215T125030

         

         

        rolloutConfig = rolloutConfigManager.getRolloutConfig(rolloutConfigPath);

        Terms & ConditionsAccessibility statement

        Loading footer...