It is showing msm api dependency missing while I am installing AEM Forms add ons package. | Community
Skip to main content
New Participant
April 21, 2025
Solved

It is showing msm api dependency missing while I am installing AEM Forms add ons package.

  • April 21, 2025
  • 3 replies
  • 1052 views

When I am installing AEM Forms add ons package, Channel Core Implementation is not getting active. It's in installed state.


It is showing msm api dependency missing while I am installing AEM Forms add ons package.
com.day.cq.wcm.msm.api,version=[5.9,5.11) -- Cannot be resolved

And when I have checked, this version of msm.api dependency is also not there on maven repository.

Best answer by EstebanBustamante

Hi,

 

This usually happens when the AEM version doesn't match the AEM Forms add-on. Can you check if you're using a compatible version of AEM? You can verify it here:
https://experienceleague.adobe.com/en/docs/experience-manager-release-information/aem-release-updates/forms-updates/aem-forms-releases

 

Hope this helps

3 replies

Khushwant_Singh
Employee
April 24, 2025

@shadanaa1 , Is the issue resolved or are you still looking for information to resolve the issue? 

ShadanAa1Author
New Participant
May 2, 2025

Hi @khushwant_singh,
It was a version mismatch issue and it's resolved when I have installed the correct version.

Khushwant_Singh
Employee
May 2, 2025

Thanks for confirming, @shadanaa1 

Employee
April 23, 2025

Hi @shadanaa1,

 

Can you please confirm which version of service pack you are trying to install. It might be some issue related to the installation.

Thanks
Pranay

EstebanBustamante
EstebanBustamanteAccepted solution
New Participant
April 21, 2025

Hi,

 

This usually happens when the AEM version doesn't match the AEM Forms add-on. Can you check if you're using a compatible version of AEM? You can verify it here:
https://experienceleague.adobe.com/en/docs/experience-manager-release-information/aem-release-updates/forms-updates/aem-forms-releases

 

Hope this helps

Esteban Bustamante
ShadanAa1Author
New Participant
May 2, 2025

Hi @estebanbustamante,
Yes, It was a version mismatch issue and it's resolved when I have installed the correct version.
Thanks.