exe can't find simple vi's

[GovBob]

I'm having problems with created exe's finding even the simplest vi's when I try to run them. I created a new project today LV2009SP1 with 4 subvi's from the 34401A instrument library and built it into a .exe. I tried to run the exe on my development computer and it asked me to find these subvi's. Attached is the simple block diagram of top level vi.

I tried mass compiling the instrument library

I can't repair LabVIEW because it's SP1 so I don't have the disks.

This is just and example of the problem.

The vi runs just fine in the development enviroment.

The instrument pallette looks just fine.

The project is just fine i.e. it doesn't open dirty.

In the options menu I left the default search paths.

Any Ideas what else I could try?

[Guruthilak]

I created an exe based on your snippet and it ran without any problem....

[srikrishnaNF]

Hi GovBob,

   I guess the problem will be with the build specifications options.First thing i can ask you whether have you included all your subvis in the project ?

Next question,so if you added then see the set destination for all contained items option should be unchecked ,if checked see the option should be same as caller.It will be good if you added the screen shot of your project and build specifications.

Thanks and regards,

srikrishnaNF

[GovBob]

Thanks for trying that out Guru. At least I know it can be done. I'm really suspecting something with the installation of LabVIEW is messing with me. I'm working with NI to try to figure it out and will post when I find a solution.

srikrishnaNF, the project is really simply that snippet I posted. Any subvi's needed are part of the dependencies. I'll be looking more into the build options.

[GovBob]

Well still no joy in Muddville. What I've tried recently:

Deleted the build in the 'build' folder. Deleted the build specifications. Basically started from scratch. Used the Ctrl+Shift+run button method to recompile the top level vi and all of its subvi's. Saved the vi and made a new executable. Same problem- wants me to direct it to all of the subvi's such as initialize.vi, close.vi, configure.vi, Error clluster from error code.vi etc.

Checked to make sure it was getting the subvi's from the 2009 instrument llb folder.

Talked with the good folks at NI to make sure I have the application properties selected correctly. Not using the LV 8.x file layout.

Question: In the properties for the application window under the 'Destinations' selection there is a 'Support Directory' option that has a destination listed as c:blah blah 'my application'/data. After I build this simple app and explore that directory all I see is the .exe file, a .ini file, and an alias file. There isn't anything listed as data! Should there be?

Grasping at straws.

[GovBob]

OK I tried building this on my PXI8106 controller running XP and LabVIEW2009 (version 9.0). Same problem. Tried explicitly including the Agilent lvlib. Same problem.

I went and looked at a coworkers build (different app) that worked using LabVIEW 8.5. I noticed a 'data' folder in the build.

.

Hmm, no data folder when building an application using LV2009.

What would prevent LV2009 from created a proper 'data' folder? Is there a setting I missed somewhere?

[Vivek_N]

I was able to create an executable from the VI snippet you posted and run it successfully. There will be no 'data' folder generated when none of the source files are chosen to be added to the 'support directory' in the source file settings in application properties. When I built the application, there was no 'data' folder either - thats not a problem.

From what I understood, you have been able to see this behavior on two separate machines now. Is that correct? If so, did you install LabVIEW 2009 SP1 with the same disks/installation files on these machines? Is there anything that is stored on a network server that LabVIEW may need to access to run the executable? I would check for any possible restrictions caused due to the IT policy there, if any. I would also ensure you are logged in as administrator on these machines. 

[GovBob]

Thanks for the reply Vivek and sorry for my late response. Yes I did try this on 2 seperate machines. One was running SP1 and the other was the very first edition of LV2009 (no patches). Neither of these computers are on a network. I am running both of them as an administrator. The SP1 machine has a corperate image on it but I still have admin rights. The other is actually a PXI system with a non RT 8106 controller with XP as loaded by NI.

 Thanks for confirming that a 'data' folder is not part of the build process. I have been on the road so my ability to work on this problem is limited. Last week I tried using a different sensor (Precon Humidity Sensor Serial) and create a build with that. When I tried to run the .exe it again wanted me to direct it to all of the subvi's. When time permits I'm going to try to direct the build to a higher level in the file structure to see if that helps.

[Dennis_Knutson]

Can you attach the actual project and VI?

[GovBob]

Thanks for your interest Dennis. Attached is a zip file with the project, the top level vi, the project .aliases and .lvlps and the version of Agilent 34401A driver I am using.