LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

EXE building, where can I found "get info.vi" ?

When i was building exe i get next error msg.
"
Error 7 occurred at Librarian Get Info.vi--File not found

Possible reason(s):

LabVIEW: File not found. The file might have been moved or deleted,
or the file path might be incorrectly formatted for the operating system.
For example, use \ as path separators on Windows, : on Mac OS, and / on UNIX.
---
NI-488: Non-existent board.
"
How i can avoid this problem ?

I did not find it NI web site and not in my Local C inside of LLB:s

I have LV70 , win2000 and quite big sw Main VI and
74pc of sub VI:s.

-HeVi-
0 Kudos
Message 1 of 7
(3,016 Views)
Hi,

Last time I had this, the main vi was refering to a non existing help file
(took me forever to find out). Just delete the path to the help file in the
vi properties. That should do it.

Regards,

Wiebe.



"-HeVi-" wrote in message
news:50650000000800000098CF0000-1079395200000@exchange.ni.com...
> When i was building exe i get next error msg.
> "
> Error 7 occurred at Librarian Get Info.vi--File not found
>
> Possible reason(s):
>
> LabVIEW: File not found. The file might have been moved or deleted,
> or the file path might be incorrectly formatted for the operating
> system.
> For example, use \ as path separators on Windows, : on Mac OS, and /
> on UNIX.
> ---
> NI-488: Non-existent board.
> "
> How i can avoid this problem ?
>
> I did not f
ind it NI web site and not in my Local C inside of LLB:s
>
> I have LV70 , win2000 and quite big sw Main VI and
> 74pc of sub VI:s.
>
> -HeVi-
0 Kudos
Message 2 of 7
(3,016 Views)
Do u mean "Main.vi" , File , Vi properties and where over there , eg. documentation category i don't have anything help file "Help Path".

I think allso that there could be refer to some vi what i dont have !

Is there problem if i insert all possible LLB:s in to source file. I mean that if there is some vi:s or LLB:s what my sw dont use , is that reason to this File not found problem ?
0 Kudos
Message 3 of 7
(3,016 Views)
Hi,

I mean the main vi, e.g. the top level (and this could very well be called
main.vi).

If you can load the main (top level) VI, try "Save all". That will save
everything. Perhaps some vi(s) are in an older version. Vi's in llb that are
not used are not a problem.

I don't know why you would insert all LLB's into the source file. Normally,
you only need to add one top level vi, and that should be enough to build an
executable.

Regards,

Wiebe.

"-HeVi-" wrote in message
news:506500000005000000947B0100-1079395200000@exchange.ni.com...
> Do u mean "Main.vi" , File , Vi properties and where over there , eg.
> documentation category i don't have anything help file "Help Path".
>
> I think allso that there could be refer to some vi w
hat i dont have !
>
> Is there problem if i insert all possible LLB:s in to source file. I
> mean that if there is some vi:s or LLB:s what my sw dont use , is that
> reason to this File not found problem ?
0 Kudos
Message 4 of 7
(3,016 Views)
Hi HeVi,
Please take a look at the following document that discusses your error:

When Running My Executable Made in Application Builder it Gives ERROR 7

Search for the Get Info file on your computer. Add it as a dynamic VI as the document above indicates when you build your application.

Sincerely,
Feroz
National Instruments
0 Kudos
Message 5 of 7
(3,016 Views)
Hi all !

Thanks for answers !

I found reason for "Error 7" , it was vi what was
defined a two times to source file.

-HeVi-
Message 6 of 7
(3,016 Views)
Just to clarify. This was a problem I also found but didnt understand this solution until I had fixed the problem myself. Simply I had created a top level VI and added a sub directory which included the top level VI. In effect this meant that I had included the VI twice in the build. Once I removed the top level VI from the directory this solved the problem.
Hope this makes things clearer.
0 Kudos
Message 7 of 7
(3,016 Views)