02-25-2013 09:36 AM
Thanks Michael for helping debug the issues. I will investigate the LLB issue later today and determine if it's a general Third Party Licensing & Activation Toolkit issue or only a problem with VIPM.
Austin, I'm glad you have your problem solved now, but let us know if you have any other questions/issues.
02-25-2013 09:48 AM
Hey David,
Thanks for following up. I've been able to duplicate the behavior again, and it seems as much tied to residual license files in the c:\ProgramData\National Instruments\Partners directory as anything else. The past few days have seen a flurry of install/uninstall of packages, and the usual workflow now is:
1.) Uninstall a packages
2.) Completely close Labview and VIPM
3.) Delete the residual license file and directory in the Partners folder above ***only for my company***
4.) Open up the package to install via VIPM
5.) Install it
6.) Completely close Labview and VIPM
7.) Open it back up and it is good to go
Skipping the close down portions or no deleting the residual license files usually breaks things.
Austin