LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Weird error: error-no error?

I can't understand what is wrong here?

sorcery.PNG

 

Any idea?

0 Kudos
Message 1 of 6
(4,792 Views)

This is certainly not supposed to happen, but I have seen it occasionally. Often this means either that the VI is corrupted or that LV has some problem.

 

The first step to try is to restart LV and see if anything changes.

If that doesn't help, you can try adding something which will break the VI and then removing it, but I can say that that usually doesn't help.

If that doesn't help, you can try copying the code in the VI to a new VI. This usually helps.

If that doesn't help, you should restore your VI from source code control, assuming you have it. If you don't have it, you just encountered one of the reasons for having it.


___________________
Try to take over the world!
0 Kudos
Message 2 of 6
(4,786 Views)

I ran across this when I upgraded my version of Labview from LV 8.2 to LV2011. Someplace on the board was a post about dropping a "super cluster" on the front panel....it's a cluster of 1024 DBL Numerics. I don't remember exactly what it does (maybe allocates more memory for the errors or the VI?), but then I was able to list the errors to know what the problem was, fix it, and then delete the "super cluster". (The problem turned out to be that General Error Handler - CORE.vi was broken in every VI that used it).

Good luck.

0 Kudos
Message 3 of 6
(4,778 Views)

Hi everyone!

 

This behaviour, sadly, can be caused by several different reasons, with some of them being harder to fix then others. Please check out these documents on how to fix this:

 

http://digital.ni.com/public.nsf/allkb/56F3F1DA24A5270286256C020070F67B?OpenDocument

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/8d2a6d74062a9eaa86256993006f0471?O...

 

If these tips don't do the trick, at worst a LabVIEW reinstalllation should stop this behaviour.

 

Regards:

 

Andrew Valko

NI Hungary

Andrew Valko
National Instruments Hungary
0 Kudos
Message 4 of 6
(4,732 Views)

i fixed this issue that I made my entire VI again. couldn't solve the problem in any other way. 

0 Kudos
Message 5 of 6
(4,717 Views)

It is not entirely unusual for instance. a global.vi with a bad block diagram will not display the error.  Heap Peak will usually show the troublesome node.


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 6
(4,709 Views)