Resource not found error - possible library missing?

[DrMoriarty]

I have the same problem (I 'm using Labview 2009 +XP64) The executable does not work on different computer (XP64 + LV2009 RunTime).

First there was ""Resource Not Found" error - Could not load front panel" error message, later on after changing "build" settings the error message became

"Missing external function from function.dll"

The problem was solved by moving the nesessary function into a different DLL, with a different C++ compiler options. 

I'm curious about what coul cause such a behaviour? 

[goofylogic98]

That is exactly my problem, however your solution doesn't really work for me as I don't know how to build a DLL in C (or C++ or C#) or anything in C as I have never worked with this.  Anybody have a clue as to what is causing it.   I didn't build the first DLL, it was a third party DLL.  The .exe file that comes with the product works fine on both computers.

[Kristen_K.]

Hi dre99gsx,

As for the Resource not found error:AE KB 4Q79HLKG: Resource Not Found Error When Running My LabVIEW Executable

Here is a good resource for steps on calling a DLL.  Also try calling the DLL from the example VI.  

Are you running Windows XP 64-bit as well?  Because LabVIEW is not officially supported on XP 64bit.  Here is a list of supported software.

Can you call any other DLLs successfully? 

I hope this helps.

Kristen H.

[goofylogic98]

I can run other dll's just fine.  As a matter of fact, the product (CP2103 USB-UART Bridge) comes with two dll's.  CP210xmanufacturing.dll and CP210xruntime.dll.  The product creates a comport on the computer but also has GPIO.  The runtime.dll allows me to exercise the GPIO on the product.  the manufacturing.dll is the one that opens and closes, gets status information, allows programing of the eeprom on the device.  It is the manufacturing.dll that is not working properly, the runtime.dll works fine.

The only difference in setup between the development system and the target system is that the development system is XP Pro and the target is XP Home.

[Kristen_K.]

Hi goofylogic98,

Are you able to call the problematic DLL from any other environment successfully?  If not, it is likely a problem with the DLL itself.  

Kristen H.