Application Builder issue with NI supplied config.llb. "Get Next Character.vi" Password Protected ?!?

[Mark B Roberts]

During application builder build of my application I get "Authentication" dialog box asking:
Get Next Character.vi is password-protected. Enter the password to access the block diagram.

In "Warnings" dialog box I get:
FlashTest.exe.lvlib
    - The VI expected to be at
"C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb\Get Next Character.vi"
    was loaded from
"\\Topaz\m. . . . \builds\FlashTest\Flashlight Test\internal.llb\Get Next Character.vi".

when I open the "C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb\Get Next Character.vi"
the front panel opens OK but indeed I can't open the block diagram.  At the front panel when I enter <Ctrl E> to view the block diagram
I get an "Authentication" dialog box saying:
Get Next Character.vi is password-protected.  Enter the password to access the block diagram.

All other functions in this llb seem to have no trouble opening their block diagrams.

My file "C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb"
is dated 7/24/2007 8:55 PM and with a size of 1,213,387 bytes.

Note:
In Build Errors box in "Details" sections the following text is shown:
--------
Visit the Request Support page at ni.com/ask to learn more about resolving this problem.
Use the following information as a reference:

Error 1051 occurred at AB_Source_VI.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  A LabVIEW file of that name already exists in memory, or exists within a project library already in memory.
-------

Any and all suggestions appreciated.

Sincerely,
Mark

[tst]

LabVIEW can not have two VIs with the same name in memory at the same. One of your VIs has the same name as one of the NI VIs that the app builder needs. When it tries to load it, it finds that your VI is already open and it uses your VI instead, but it can't work with your VI, so it throws an error.

In LV 8, NI added libraries, so that the library name is part of the VI name and you can have VIs with the same name in different libraries, but they haven't moved all of their old code into libraries.

The solution for you is simple - you need to change the name of your VI. You can do this either by doing a save as on it or by adding it to a library. If you do a save as, be sure to do it when the VIs calling it are open, because otherwise they will not know to link to the new file name, and be sure to save them as well.

Interestingly, the error says that a file of that name is in memory or is in a library which is in memory, which seems to indicate that putting the VI in a library will not help you, but as far as I know, it should. I don't use 8.x, so I can't test it.

[Amanda_H]

Thanks for the great response, tst! Did this clear up your problem, Mark?

[Mark B Roberts]

I tried opening all the vi's in a stripped down project, doing a "save as" on each before closing them all and then did a build which failed in the same way.

I also tried creating a .lvlib library file, added the vi's to it and got the same build failure.

I did manage to get a NI SRV # opened to get support on this issue.  I've attached a zip file of the reduced project that I send to NI, if anyone's interested. 

In the CfgIni2Cluster.vi if I remove one of the last two remaining cases, the error changes to one referring to "Config Data Refnum.vi" in the same library, "config.llb".
In this case the "Build errors" dialog box shows the following:
---------------------
The build was unsuccessful.
 
Possible reasons
----------------
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb\Config Data RefNum
Destination: C:\ECL\builds\FlashTest\L&S Flashlight Test\internal.llb\Config Data RefNum
 
Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>
--------
Details
--------
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
 
Error 1051 occurred at AB_Source_VI.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
 
Possible reason(s):
 
LabVIEW:  A LabVIEW file of that name already exists in memory, or exists within a project library already in memory.
---------------------------------------------------------------------------------------

Thanks for your comments and ideas.

Sincerely,
Mark

[tst]

OK, I got to play with it in 8.5, and I can build without errors. I do get the password dialog and the VI is used from the temporary LLB LV uses for buliding the executable, but the build completes.

I'll let NI deal with that part, but I just wanted to point out that there are tools for saving and loading arbitrary clusters to and from INI files and you might want to use those instead. Two that come to mind are tools from OpenG and MGI, both free.

[HollywoodGunner]

Has anyone found a fix for this problem yet? I added some code that was to read from an .ini file, and the application fails to build, telling me that the "Get Next Character.vi" is password protected. I have searched and cannot find any other vi or text with that name or letters.

[HollywoodGunner]

 Additional info on Error:

Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  Incorrect password.

Method Name: Lock State:Set

[G-Money]

HollywoodGunner-

           The problem stated before arose from referencing VIs that had the same name as another VI on the system. Mark thought he was referencing the correct one in his lvlib file but was not. You can check to see what VIs you are using by going to Project Explorer>>Project>>Show Item Paths. This tool displays the path of the VIs in the Project Explorer to the right of the name. A workaround that helped Mark out was if you go to Executable Properties (Right-click on your executable name in Project Explorer) and go to Destinations, we found that if you turned off the "Add Files To New Project Library" that the problem would go away. I can't explain why this works but it did help until the final solution of referencing the correct VIs was found. Please let me know if this is helpful. Thanks and Good Luck!!

[BobDylan]

Helo,

 I just upgraded from 8.5 to 8.6 and the following problem occured in the build process:

An error occurred while saving the following file:

C:\READ86\KAST.vi

Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi
->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->
AB_CreateNewWizard_Invoke_CORE.vi->EBUIP_CreateNewWizard_Invoke.vi->EBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>

I tried to save the source in 8.6 down to 8.5 and compile (build) the program, and it works fine there. I would like to build the program in 8.6 without this

ANNOYING ERROR

kind regards

'the duck Hawk'

[G-Money]

BobDylan-

            I would try recreating the code in a completely blank VI. If you carried over any of these invoke nodes, then chances are that they have changed since 8.5. You also might have better luck getting more people to look at this problem if you post this in your own thread instead of buried in this old one. Let me know how it works. Thanks!!