LabView 8.5 crashes when opening this VI

[Wiebe@CARYA]

"hempi23" <x@no.email> wrote in message
news:1202163008294-649163@exchange.ni.com...
> The funny part is that the code itself is still executed correctly when
called by another VI.

This means you can actually load it (don't open the front panel). Instead of
running the calling VI, save the calling VI to a previous version. Then
reload it. Perhaps the conversion will resolve the problem.

Regards,

Wiebe.

[hempi23]

I tried sving the calling VI f as version 8.0 and 8.2 but it crashed before any file was written.

Is there a way to open the problematic VI without the front panel or to reset the front panel?

[Wiebe@CARYA]

I'm not sure what you mean by resetting the front panel. If you load a vi
that has the problematic vi as subvi, the front panel isn't giving any
problems. This doesn't help much if you can't save the VI.

Anyway, the problem seems to be solved by JB...

Regards,

Wiebe.

[hempi23]

Thanks Wiebe.

I thought if I could reset the front panel in any way I would be able to reopen the SubVI. The thing is that although the SubVI is executed normally I cannot open it for any changes and updates. The fornt panel of the VI is not important at all, if I could just recover the block diagram.

JB couldnt solve the problem too, he tired another SubVI, which has a very similar name.

[JB]

I have just done several trials with VI server but I was unfortunately not able to restore your VI. The only thing I get is a picture of the front panel... I have no further ideas now !

I suggest to contact NI because they may have other tools...

[Wiebe@CARYA]

Has anyone tried to save a VI with the problem VI in it as a sub VI to a
previous version jet?

Also, perhaps seaching the heappeak might help. I don't have 8.5 installed,
and might not install it for some weeks... Search heappeak for more
information on this (in LAVA or this forum).

Regards,

Wiebe.

[MikeS81]

Hi

yes i have tried it. to save the demaged vi as sub vi with 8.5 is no problem, but for previous version LV crashes.

Everything i try to read the blockdiagram shows the same error message. And i think to save it for a previous version, LV has to read the code.

Mike

[hempi23]

Thanks everybody trying to help me with this issue!

I also tried VI server and came as far as JB: a picture of the front panel while everything else crashes. I contacted support too and was positively surprised that they got back to me quite fast. They also tried different ways to recover it via VI server but weren't successful either.

I will take a look into heappeak, but at this point I will probably start over again. Would be still nice to figure out what went wrong and if there is a way for recovery. I the meantime I will use make a little tool that constantly backups he code. That btw would be a great LabView feature that can be easily implement: an automatic backup copy prior to saving a VI. I guess I just learned the hard way that I have to take care of this myself.

[hempi23]

Read up about heappeak ... Unfortunately there is no error message created when LabView crashes on me - so I am missing the starting point. Also, since I cannot open the VI without having LabView crashing there is no way of using this debug feature at all

[Wiebe@CARYA]

Yes, the heappeak isn't easy to use. And can be a big problem to find the
problem, and even then it would be hard to fix it in this situation.

Saving to previous was a long shot too, but since it's so easy to try, it is
worth the effort.

About the backup tool... LabVIEW 8+ has a recovery tool embedded. It does
restore the VI's you are working on if LabVIEW crashes. But it doesn't help
if your VI crashes. I think there have been some initiatives for backup
systems, so you might try searching the web before you start building this
yourself.

Regards,

Wiebe.