Resource Not Found / LabVIEW Error Code 3

[xkenneth86]

All,

I'm running into a pretty discouaraging build error here and I'd really like some help figuring it out.

I'm trying to use the vendor provided DLL to interface to a USB pressure sensor. The vendor provides an API for this, using the call library node. I wrote a simple application, created an EXE and Installer, and installed it into a test virtual machine. After a restart, when I ran the EXE in the test VM, I got the attached error for every VI that used the call library node. The text of the error is as follows:

"LabVIEW: Resource not found. An Error occurred loading VI 'FindSensor.vi'. LabVIEW load error code 3: Could not load front panel.

I thought this could possibly be some fluke error caused by some mis-linking of something as the vendor provided API seemed quite old, it didn't even use proper error terminals, it had custom ones.

I re-wrote a quick test application, from scratch, for interfacing to the first function to call from the DLL, and it did the exact same thing.

I've attached a screen shot of the error and project that you can compile to see if you can find the error yourself.

Thanks for any help in advance!

- Ken

[Matthew_Kelton]

You didn't include a build in your project.  I created a simple EXE and it seems to work.

Have you created an installer for it and are not placing the DLL where LabVIEW expects it?

[xkenneth86]

Hi,

I'm not sure why it didn't have the build specifications on the test project. I created a basic EXE and installer w/ the LV run-time engine. The problem doesn't crop up on the development machine; the EXE runs fine there.The problems occurs when I install the installer (LVRT + EXE) to a clean Windows 7 or XP machine.

- Ken

[Matthew_Kelton]

I ran the EXE on another PC w/o LabVIEW 2010 on it and it again ran fine.  Where are you installing the program and the dll?

[xkenneth86]

Should be a standar drictory, that's really weird. Let me try your solution.

[Dave-C]

Hi Ken,

I'd bet you've already seen it, but there is a Knoledge Base article that look at this issue.  http://digital.ni.com/public.nsf/allkb/8F68715444302CAB86256DDD0071C140

Unfortunately, it sounds like your issue may be deeper than this fix.  Is this problem occuring on several target machines?  Or do you only have the opportunity to try one other?  Similarly, including what's in the installer, what LabVIEW or Run Time Engine programs are on the target machine?

Thanks for keeping the forum posted

-Dave C

Applications Engineer

National Instruments