Trouble launching LabVIEW VI from Explorer in Windows XP

[tommiejb]

Has anyone had trouble opening a VI by double-clicking on it in Explorer on a Windows XP machine?  On our systems, if you double-click on a VI, the titlebar of the VI will appear, but the front panel won't show up.  After about 30 seconds, a window pops up with the message "Windows cannot find XXX.  Make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search.", where XXX is the VI that you just double-clicked on.  I've enclosed a screenshot of this problem.

If you launch LabVIEW first, then double-click on the VI, it opens fine.

Any ideas on what is going on?  It's not a major issue, but it is annoying.  Also, I suspect that it is related to another problem we are having, in which the program hangs on a dynamic call, after which you cannot open any VI by double-clicking on it in Explorer.  In both cases, it seems to be a problem with LabVIEW and Windows XP.

Tom

[tommiejb]

I forgot to mention in my last post that we are using LabVIEW 7.0.

[~jiggawax~]

Hey Tom,

So I found a knowledge base that explains in more detail about this issue and what causes it.  We have seen it several times.  If you do this and the problem continues then let me know.  Here's a link to the KB: Windows Cannot Find VI Error When Opening a VI

[tommiejb]

These suggestions did not help.  However, it did help in a way, because it is a timing issue.  The problem is that it is a User Interface that runs automatically when launched (i.e., it is set to Run When Opened).  Normally, this wouldn't be a problem, but the first thing this VI does when it runs is to launch TestStand (ActiveX Automation Open).  If I put a delay before launching TestStand, it opens fine.  So now I just need to figure out what the right delay is.  I tried 5 seconds, but that is probably longer than is needed.  In any case, I solved my problem, but the link you gave did get me thinking along a different line which led to the answer, so thanks!

Tom