Can't open a VI

[carolyne]

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.

[chrisger]

hi there

i tried to open your vi with LV 7.1 on XPSP2. after selecting the vi from the file dialog LabVIEW shows no reaction at all! then i tried to open an reference to the VI, but "Open VI reference" function returns error code 7 "file not found" (funny...)

i suggest to contact NI, maybe they have more tools.

[carolyne]

Dear Chrisger,

I have already sent a request to NI.

Thank you for your try, by the way, I'm working with the 8.0 version.

[chrisger]

ok, but LabVIEW dosn't even reach the point where the version is checked, it shows no reaction at all.

good luck!

[pincpanter]

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.
Paolo

[EdDickens]

When I try to open it, I get the following error dialog.



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

[EdDickens]

---

@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.
Paolo

---

7.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]

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?")

Paolo

[carolyne]

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

[Stuart_R]

Yeah unfortunately that VI seems bad. Don't know how it happened but do know that unless you have a backup, you'll probably have to start again and there isn't a magic tool for fixing this.