VIPM Versions Affected
VIPM 2014 through VIPM 2018 (builds 2020 and earlier are affected)
Fixed in VIPM 2018f1
Issue
When users attempt to deactivate an add-on that was built using VIPM (with license-binding done by VIPM at package build time), the deactivation fails with an "UNKNOWN ERROR!" message.
Workaround
To work around this issue, swap the Client Key and Server Key inputs on the Licensing & Activation (page) >> Deactivation (tab) of the VI Package Builder build settings editor.
This will allow building the package such that Deactivation of the Licensed Add-on works correctly.
Comments
8 comments
The idea of allowing developers to store VIP versions inside the LVPROJ is to .... the linker just changes the subVI paths for affected project VIs. geometry dash
This should to be incorporated inside the HTML record this is covered in VIPM. adding to the rundown settled my association issue, anyway this isn't constantly expressed in Appendix B. the best approach to physically arrange your LabVIEW variant to allow VIPM correspondence. 1000-word essays
a very detailed and easy-to-understand article, thank you very much for your contributions to the community, I admire you so thank you candy crush soda
In conclusion, we can all agree that both the art and child centred therapies do play a big role in the shaping of lives of most children who are suffering from various disorders like mental problems amongst other related challenges. article writer
Thank you for sharing! I have nothing to say except click the "yes" button below the question "Was this article helpful?"
impossible game
we can all agree that both https://bit.ly/3N25ozA art and child centred
Copy the set up for the VI package on a USB disk. When you save a file in VIPM, if the necessary packages have not driving directions previously been downloaded, VIPM will do it automatically.
Yes, it does work correctly, even in 2023. Cheers!
Julianna from chi-nese.com
Please sign in to leave a comment.