Hi @pkumarp1 - You might have already validated by now but Is it the same issue that you get when you try to setup fresh AEM instance?

@sethia_varsha-  If you can validate the existence of the content.xml across msm folder, the custom blueprint folder (that you have created above) and across the jcr:content folder within the apps folder in your code repository alongside updating the filter.xml file. If not, the content.xml should b...

@sethia_varsha - Even when  you have the above content.xml are you still getting the above error?

@sethia_varsha  - This looks correct! I created a MSM blueprint on the vanilla instance and tried to deploying as well.It worked as expected! But quick question you mentioned above that you are getting the above console error when you are deploying the code to higher environments. What happened when...

Hello @sethia_varsha -  But I see the code build is failed.Because as I mentioned it seems : That while creating the MSM blueprint you were trying to add the cq:dialog node as a child of the the parent node nt:folder which is not permissible.However, if you would try creating a cq:dialog node under ...

Hello @sethia_varsha -  Looking at the console error which you have attached above, It seems : That while creating the MSM blueprint you were trying to add the cq:dialog node as a child of the the parent node nt:folder which is not permissible.However, if you would try creating a cq:dialog node unde...