Jump to content
odjau

Packaging Licensed VI

Recommended Posts

Hi JKI team,

 

I've come across some issues building licensed package with VIPM 2010. I don't know if it's wrong use or bug of VIPM 2010 (it can be LV activation feature too).

 

1 - I build successfully licensed package for my toolkit. I install it successfully. I activate the license. Every thing is right at this point.

Issue come when I want to access VI block diagram from toolkit, I can(!) and I don't want the end user can see diagram.

In my understanding "Library protection" tab in "licensing & activation" category of VI Package Builder adds password to all lvlib VIs, am I wrong ? I've tried to apply password in "Source File Settings" but an error occurs during the build.

 

2 - Setting an "automated Online Activation URL" result an error (code :-314515 source : _ValidateAutoActivationURL) during the build process (I've tried several form http, https,...)

 

Thanks for your help

Share this post


Link to post
Share on other sites

I think I was very tired last week...

I've solved all these "issues" today.

Just a setting mistake :)

 

Hope you don't lost your time with me

Share this post


Link to post
Share on other sites
I think I was very tired last week...

I've solved all these "issues" today.

Just a setting mistake :)

 

Hope you don't lost your time with me

 

No problem at all. I'm happy you got it working. It's funny how such small things can create such big problems :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.