How do I make TestStand find Is that it should be finding, instead giving "Code module must be able to load"?

[bmihura]

Occasionally TestStand forgets where its VIs are and I have to waste a lot of time reminding it. Here's what I'm trying to avoid:

1. Occasionally I will analyze my sequence and TestStand shows in its Analysis Results pane hundreds of unexpected errors with the red alert symbol with the text "Code module must be able to load."

2. I double-click  any of those errors and I get taken to the offending Module pane with its red alerty symbol flashing over to the right; and in "VI Path:" there is only the VI name but not the path.

3. Click the "Browse for Path..." icon just to the right of the path, and a file dialog box opens always starting in the exact directorycontaining the exact VI TestStand supposedly "can't" find. If I use that file dialog box to select the VI manually then that error is fixed and I move on to one of my hundreds of other uninvited errors.

4. I have TestStand's search directories set correctly, I hope: In its Configure >> Search Directories... menu item I have my project's parent directory checked and its "Search Subdirectories" checkbox checked as well.

5. I tried TestStand's Tools >> Update VI Calls... menu item with the "Force Prototype Reload" option selected for the various VI calling items and that didn't work either.

How do I fix this problem?

[bmihura]

That's supposed to say "VIs" in my post. Would a moderator please edit that or delete the post?

[dug9000]

What is the path set to before and after you correct it? Does it say "file not found" underneath the path before your correct it?

I recommend you avoid using "Search Subdirectories" and instead use partial relative paths like:

subdir1\subir2\myvi.vi

The reason is that you are more likely to have name conflicts and match to the wrong vi if you just use a simple name like:

myvi.vi

Also "Search Subdirectories" has a performance cost to it which can slow down your module loading times, especially if the path is on a network drive.

-Doug

[bmihura]

TestStand says "(File not found)" underneath the path before I correct it.

Sometimes TestStand has the correct path underneath the VI and it still "can't find" it. What's wrong?

[Shako]

Is there any solution to this problem?

I am having the same problem just with a CVI DLL.

[danniwithNI]

Hi Shako, 

What specific error message are you getting? This article might be helpful if you're getting error -17709. 

[Shako]

Hi danni

Thanks. My problem was a missing dependency. I did not know where to find out which DLL it was looking but have since figured out where to find the error message describing that.