What to Do When Vi Continues to Search and Wont Load Application Labview
I can't open my VI. There is a message " Labview.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created ".
I send to you the VI and the failurelog file.
I think maybe there was a problem during the saving and Labview doesn't find all components to open it.
Thank you for your help I need this VI.
lvlog05-02-06-08-32-36.txt:
http://forums.ni.com/attachments/ni/170/182483/1/lvlog05-02-06-08-32-36.txt
global 3 charac relay.vi:
http://forums.ni.com/attachments/ni/170/182483/2/global 3 charac relay.vi
ok, but LabVIEW dosn't even reach the point where the version is checked, it shows no reaction at all.
good luck!
When I try to open it, I get the following error dialog.
<img src="Loading Image... ">
This usually means that who ever saved it last, saved it without the
block diagrams (not really a good idea) and it's looking for a subVI
that it can't find. Probably one that that was created instead of one
that comes with LabVIEW or it would be able to find it. Note that the
dialog says the VI is broken.
Since there are no block diagrams, LabVIEW cannot open the VI because
the source code is gone and it can't figure out what to do with it.
Even if you had the missing subVI, since the blick diagrams are gone,
you wouldn't be able to do anything with it except run it. And even
then you'd have to have to open it in the same version of LabVIEW that
it was saved in. (no block diagrams is a bad thing).
Ed
Message Edited by Ed Dickens on 05-02-2006 02:39 PM
open error.gif:
http://forums.ni.com/attachments/ni/170/182649/1/open error.gif
Dear Ed,
I don't know how I did to not save the block diagram, I've already saved a lot of VI and I've never had this problem...
But thank you for you answer.
To insterested persons : Here the answer of my support request :
Hi Caroline,
I tried opening the VI you sent in and it crashes on my computer aswell.
Unfortuneately it seems you VI is corrupted, there is not much you can do
with a corrupted vi other than deleting it and restoring from a backup. The
only thing I would suggest would be to mass compile the VI. To to this open
up LabVIEW goto Tools>>Advanced..>>Mass Compile and select thr directory
which contains your vi. This tool loads up VI's and recompiles them, If it
still crashes then I dont think there is much more we can do.
Regards
Jonathan Bowers
National Instruments
Applications Engineering
carolyne wrote:
Dear Ed,
I don't know how I did to not save the block diagram, I've already saved a lot of VI and I've never had this problem...
But thank you for you answer.Since you didn't
purposly save it without the diagrams, then something must have
happened during the regular Save process that damaged the VI. If you
don't have recent backup, you're stuck starting over.
This is a good time to remind everybody to always keep daily backups.
Even if it's just a mirror copy of your projects to a second location
on your hard drive. There's a few free backup and sync tools that I use
for this.
One is called <a href="http://www.xs4all.nl/%7Elploeger/TreeComp3.htm" target="_blank">TreeComp</a>. This let's you manually sync directories either loaclly or across a network or to an FTP site and even into a Zip file.
Another is called <a href="http://free-backup.info/" target="_blank">Back2Zip</a>. This
is a system tray application that you setup to automatically backup
directories you specify. It can keep numerous dated copies so you can
go back several versions if needed and can backup to standard Zip files.
A new one I've been playing with is from Microsoft called <a href="http://www.microsoft.com/windowsxp/using/digitalphotography/prophoto/synctoy.mspx" target="_blank">Sync Toy</a>. Basically the same as the Back2Zip. Not sure which on I like better, but I'm leaning towards the Back2Zip.
Ed
pincpanter wrote:Chris,the same happened to
me opening a (supposedly) good 8.0 vi with 7.1. I didn't get any
message and of course the vi was not opened.The vi was intended to give an example of using MathScript nodes.Paolo7.1
cannot open 8.0 VIs directly. You must first open them in 7.1 and do a
"Save As" and select, "Save for Previous Version". It will then save it
in a format that 7.1 will be able to open. Of course any 8.0 only
features that were used in the VI will not convert back to 7.1 and the
VI may be broken and need a little work.
Ed
pincpanter wrote:Thanks Ed, I already knew this. But generally we get at least a warning message.In
this particular case, I was almost sure the vi was 8.0, because the
author said it contained MathScript nodes (my attempt to open it was a
programatically hopeless action, just to be able to say "I tried
anyway"), but if we don't know the actual version of a vi we are trying
to open and we get nothing, there seem to be two possibility open:
wrong version? vi damaged? Boh!? (Boh!? is an Italian way to say
"who knows?")PaoloNot
getting the dialog at all is a little strange. My guess would be the VI
is damaged. If that's the case, not much you can do except try to find
it again.
You might actually want to submit that VI to NI through the support
request page so they can try and investigate what's going on with it.
Ed
Hi Ed,
very often I don't get a message from LV7.1 when trying to open a
LV8-vi. It seems to do nothing when "opening" such vi's... But LV8
opens those vi's without any problems.
But the vi from carolyne still is broken (as said by you earlier).
Source: https://comp.lang.labview.narkive.com/5uknJXS0/can-t-open-a-vi
0 Response to "What to Do When Vi Continues to Search and Wont Load Application Labview"
Post a Comment