Thanks a lot Dinesh.

Hi Dinesh,Were you able to find a solution/work-around for this issue?

Hi Dharanya,Did you try the fix suggested by Kautuksahni? Did it work? I am also facing the same issue. Please do let me know.Thanks,Kasyap.

For all those who are facing this issue, we managed to resolve it by providing a dummy product component in the live copy pages. Added it to the templates as well so that the new pages will contain it by default.It is just an empty component. Basically the MSM framework checks for the resource 'prod...

You saved my day, thanks buddy

We have a requirement to dynamically populate a list in an inner component based on the content of the parent component. So, I have a component say abc, with a property value authored as (key:p1, value-v1). In the dialog of the child component of abc component, I am including a data source to fetch ...

We are getting the exact same issue. We are using AEM 6.1 without SP.The rollout happens successfully for the first time and them from second time onwards, we get this exception.

Which AEM version are you using, I am facing this issue in AEM 6.1. Do you have any idea if there is a day care hotfix for the same or has it been fixed in AEM 6.2? Do let me know.