Property Node Gets Stuck

[paul_a_cardinale]

This code (usually) gets stuck at the first property node.  I can't figure out why; it's just supposed to return a reference to the owning library (and it does actually have an owning library).

[Kyle97330]

I have never seen this happen so I have no direct ideas other than "maybe there's something weird or corrupt about this particular library", so... questions.

Have you tried this on multiple libraries or just one?

Does it work if you call this from a VI not in the library after being passed a reference to this VI that is in the library?

If you try to open the library independently, via the "Library.Open" Application invoke node, does that work?

[paul_a_cardinale]

I've got some additional information:

• The code is called from the configuration VI of an Express VI.
• Upon initial configuration (when the Express VI is dropped on a BD), the code always gets stuck.
• On subsequent configuration calls (i.e. double-clicking on an instance of the Express VI), the code works OK.
• The code is a dependency of both the configuration VI and the Express VI.

At this point, my best guess is that on the initial call to the configuration VI, not everything is really ready in the instance of the Express VI (however adding a long delay doesn't help).

[paul_a_cardinale]

---

@Kyle97330 wrote:

I have never seen this happen so I have no direct ideas other than "maybe there's something weird or corrupt about this particular library", so... questions.

Have you tried this on multiple libraries or just one?

---

So far just this one.

Does it work if you call this from a VI not in the library after being passed a reference to this VI that is in the library?

---

What?

---

If you try to open the library independently, via the "Library.Open" Application invoke node, does that work?

---

Nope.  It gets stuck at Library Open.

[Kyle97330]

---

@paul_a_cardinale wrote:

---

Does it work if you call this from a VI not in the library after being passed a reference to this VI that is in the library?

---

What?

---

---

The property node in question has no reference input, so it operates on "This VI", i.e. itself.  Equivalent to this:

I have observed that sometimes operations that operate on "self" do not work, but when done from outside of "self" they do, like if you did it like this:

However, now that you have made your additional post with more information, I see that it's from an Express VI.

I would venture that is more likely to be the cause.  I don't know exactly what goes on "under the hood" of the whole Express VI mechanism, but I know that they are instance VIs, meaning that they essentially are a VI embedded inside another VI, and it could be that during the initial configuration the library status of them is not fully defined yet so it hangs.