Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Blogs / Dedicated to all Microsoft Dynamics AX users / Common issues and solutions...

Common issues and solutions while importing ISV license file

Urminavo Das Profile Picture Urminavo Das 81
Dear Friends,

When we think about preparing an ISV solution, Microsoft Dynamics AX 2012 allows ISVs to create encrypted license files using x509 certificates, to protect their intellectual property. When customers deploy ISV modules to their environment, they are required to import the license file to enable the module. During the license import process, the certificate that is used to sign the file is checked against the root certification authority to verify its validity. In certain cases, however, the root authority may not be available in the system and thus requires an internet connection to check the validity through CA (Certificate Authority). The process steps are –
  • Perform the standard installation.
  • Import the certificate (this needs to be imported under “Trusted Root Certification Authorities”).
  • Import the model or model store (certificate needs to be imported prior to this, as this will change the signature of model to “Yes”).
  • Import the license file (the license file needs to be generated by the ISV partner, seeking the required details from the customer or partner, where ISV will be deployed; and providing the certificate related inputs).
  • Synchronize the database.
  • Compile and full CILL of the application.


But at times, in spite of importing the certificate and the model/model store; we get stuck while importing the license file. To achieve this, the following steps needs to be followed –

  • Launch MMC.exe.
  • Go to File > Add/Remove Snap In.
  • Go to Certificates.
  • Click “Add”.
  • Select “Computer Account”.
  • Click “Next” and “Finish”.
  • Click Local Computer > Trusted Root Certification Authorities > Certificates > Import.
  • Follow the wizard to import the certificate.
  • Try importing the license file.



This was originally posted here.

Comments

*This post is locked for comments