Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.

---

Trying to install the NSM License gives an error: Invalid License File.  Failed Integrity Check. 

The license file fails to load into NSM properly.

There are three reasons for a NSM license to fail:
1.  License file is corrupt or contains extra information.
2.  NSM is running as non-root and there is a permissions issue.
3.  The license is not for this version of NSM:   HA, non-HA, wrong license for this server, etc.
 

To troubleshoot these issues, follow these steps.

1.  License file is corrupt or contains extra information.
View the license file.  The license file should not contain any extra information above the line:   -----BEGIN PGP SIGNED MESSAGE----- 
This can happen when the license file is downloaded from the Juniper Support site.
See KB11505 for an example of what a NSM license should look like.

The license format is like this:

-----BEGIN PGP SIGNED MESSAGE----- 
brief info.
-----BEGIN PGP SIGNED MESSAGE----- 
key
-----END PGP SIGNATURE-----

Any extra info above the first ----BEGIN PGP SIGNED MESSAGE----- header should be deleted.


2.  NSM is running as non-root and there is a permissions issue.
If the NSM services are running as non-root, verify that the install ID is the same for both the root user and the NSM user.

a)  become user root:   su - root
b)  run /usr/netscreen/GuiSvr/utils/licenseDebug.sh installId
c)  become user nsm:   su - nsm
d)  run again:   run /usr/netscreen/GuiSvr/utils/licenseDebug.sh installId

The Installation Id shown in step b) and d) should be the same for both the root user and the NSM user.  If there is a difference, there is a permissions issue and JTAC should be contacted.


3.  The license is not for this version of NSM:   HA, non-HA, wrong license for this server, etc.
An NSM license for a standalone server will not install on an HA NSM server.  View the license and verify the license was generated properly. See KB11505 for an example of what a NSM license should look like.
Also, the installId may not be correct.  run /usr/netscreen/GuiSvr/utils/licenseDebug.sh installId and verify the Installation ID matches the Installation ID listed in the license file.
 

2020-10-18: Tagged article for EOL/EOE.