'SubVI not executabel', but has no error?

[LuI]

Hi all,

I've got a quite large project (400+ VIs) in LV 7.1 (english) on a German W2k.
In the last weeks I had some situations, that, during editing, the main VI was not executabel. The Error List showed that one of the subVIs was not executabel. When choosing that SubVI, the run arrow was broken, but the Error List did not show any cause. Weird!!!
After doing some editing this went away and all was good.
I can not remember having done any special actions; it might even have helped to delete and recreate a wire.

Is this a known issue? Is it serious? Anything to be done?

Greetings from Germany!
-- Uwe

[shoneill]

Hi Uwe,

could it be that a LabVIEW process is running in the background which is accessing the sub.vi? This way it will show that it can't be run (is already executing), but of course there'll be no errors.

Hope this helps

Shane.

[cs42]

Hi Shane,

but that's not shown by a *broken* error, is it?

Carsten

[LuI]

Shane, Carsten,

I might have not been as clear as possibel. Sorry for that.

No, the SubVI was neither executed nor 'reserved for execution' by another process. It simply showed a broken arrow, which in my understanding shows an error in the particular VI or problems in a subVI. In this case one could normally follow the path in the error list down to the broken subVI.
But here I came to a 'final' subVI with a broken arrow, that showed no errors in the Error list but still had a broken arrow.
Looks like some insane objects within LV, does'nt it?

[alipio]

Hi Uwe

Take a look at this link. Perhaps recompiling can help you.

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

Hope it helps
Alipio

[LuI]

Alipio,

thx, this is it.

My project operates free running processes that are instantiated from a template.
During test phase I usually have the template open as well as a new instance. So I can test the instance and 'repair'-edit the template. This might cause that problem.

Thx again and
Greetings from Germany!

[JeanPierre]

This happens once in a while...

It is usually corrected by forcing the VI to recompile (Ctrl+Run Arrow).

[shoneill]

---

@cs42 wrote:
Hi Shane,

but that's not shown by a *broken* error, is it?

Carsten

---

It is on my LAbVIEW system (6.1, WinXP).

By setting a sub-vi to execute, any VIs "above" this sub-vi which are dependent on the VI have a broken arrow until the sib-vi is finished executing.

Maybe it's different on LV 7?

Shane.