Level 1

Unable to re-enable component inheritance for MSM Live Copy

Forum|Forum|1 year ago
June 6, 2024
3 Antworten
1373 Ansichten

Hello.

We have some issues related to MSM Live Copy inheritance in AEM Cloud.

The functionality of re-enabling MSM component inheritance doesn't work for all our components which have cq:responsive node across all our environments in cloud manager.

At the same time it works locally with the same aem-sdk version and the same version of our source code.

When we are trying to re-enable inheritance for some component with cq:responsive node, we are getting 500 Internal Server Error for the POST request to re-enable inheritance in browser console. Also we have checked the error logs of our instance, there we were found such error message: POST /content/.../content_component.msm.conf HTTP/1.1] com.day.cq.wcm.msm.impl.servlets.LiveRelationshipServlet Error while updating relationship java.lang.IllegalStateException: The relation given is not cancelled, can not reenable.

The error message says that the relation is not cancelled, but as we can see from the page editor and from JCR - the inheritance is cancelled.

At the same time if we will try to delete cq:responsive node from the component structure - the inheritance re-enablement will work.

Note: In our codebase we don't have any custom code which relates to the MSM Live Copies functionality.

Does anyone have some ideas what can be the root cause of this issue and how could it be fixed?

Thank you,

Anton.

Dieses Thema wurde für Antworten geschlossen.

HrishikeshKagne

Community Advisor

Hi @anton_kha ,

The error message "The relation given is not cancelled, can not reenable" indicates that the Live Copy relationship for the component is not in a state where it can be re-enabled. This can happen if there are conflicting changes between the source and target Live Copy instances, or if there are issues with the Live Copy configuration.

Here are a few possible reasons for the issue and some steps to troubleshoot:

1. Conflicting Changes: If there are conflicting changes between the source and target Live Copy instances, it can prevent the re-enabling of component inheritance. Check if there are any pending changes in the source or target Live Copy instances that may be conflicting with the inheritance re-enabling. Resolve any conflicts and try re-enabling inheritance again.

2. Live Copy Configuration: If there are issues with the Live Copy configuration, it can prevent the inheritance re-enabling. Check if the Live Copy configuration is set up correctly and if there are any errors or warnings in the Live Copy console. Resolve any issues and try re-enabling inheritance again.

3. CQ:Responsive Node: The presence of the cq:responsive node in the component structure can cause issues with the inheritance re-enabling. Try removing the cq:responsive node from the component structure and then re-enabling inheritance. If this works, you may need to modify the component structure to support inheritance with the cq:responsive node.

4. AEM Version: Check if there are any differences in the AEM version between your local environment and the AEM Cloud environment. If there are differences, it may be related to a bug or issue in the AEM version used in the Cloud environment. Check if there are any hotfixes or patches available to address the issue.

If none of these steps resolve the issue, it is recommended to reach out to Adobe Support or your AEM implementation partner for further investigation and assistance.

Hrishikesh Kagane

kautuk_sahni

Community Manager

@anton_kha Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni

K

KumariSu

Level 2

Hi @anton_kha did you find any solution to this issue, I'm also getting the same issue. Any suggestion or help would be appreciated.