LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Library Password causes NI Application Builder Error (LV2009.SP1) [Build won't proceed unless Library is unlocked with password]

[cross-posted to LAVA]

 

Howdy!

I am having the following issue whereby my build is error-ing out.
It is because I have Library(s) that are Password Protected (note: so are their VIs).
I have to enter the password in order for the build to work.
If the Library is just Locked then there seems to be no issue and the build works.

Has anyone else have this issue?
Should this be happening or is this a bug?

 

Build Error - Library Locked.png 

Certified LabVIEW Architect * LabVIEW Champion
Message 1 of 4
(2,761 Views)
It is going to be pretty difficult since the vis are also password protected. Any back up?
0 Kudos
Message 2 of 4
(2,733 Views)

jg-code wrote:

[cross-posted to LAVA]

 

Howdy!

I am having the following issue whereby my build is error-ing out.
It is because I have Library(s) that are Password Protected (note: so are their VIs).
I have to enter the password in order for the build to work.
If the Library is just Locked then there seems to be no issue and the build works.

Has anyone else have this issue?
Should this be happening or is this a bug?

 

Build Error - Library Locked.png 


I have seen similar but don't know if I can call it a bug.

 

What I saw was when I was trying to do a source distribution of some of NI's LVOOP version of the toolkits (DB or was it the config file stuff?).

 

It appeared to be a way to keep me from buggering up NI's classes so I wrote it off as LV protecting itsefl from me (not the first time Smiley Wink ).

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 4
(2,728 Views)

Ben wrote: 
I have seen similar but don't know if I can call it a bug.

 

What I saw was when I was trying to do a source distribution of some of NI's LVOOP version of the toolkits (DB or was it the config file stuff?).

 

It appeared to be a way to keep me from buggering up NI's classes so I wrote it off as LV protecting itsefl from me (not the first time Smiley Wink ).

 

Ben


I was leaning towards a bug as I can't see a point in PP a Library then distributing it, if a developer has to ever enter a password!

Kinda defeats the purpose if you know what I mean! 🙂

Certified LabVIEW Architect * LabVIEW Champion
0 Kudos
Message 4 of 4
(2,715 Views)