LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Resource not found error - possible library missing?

I cannot find a solution to this problem.

 

I created a very simple .vi which calls a function within a C .dll file.  This dll is a wrapper which in itself calls functions in a C++ dll file.  It works great in the development environment.  I can create a .EXE application and it will also work great on my PC.  As soon as I transfer it over to another PC containing LV 8.6 Runtime, I get this "Resource Not Found" error - Could not load front panel.

 

I made sure both my .dll's were in the same directory on the other PC.  It works fine on the PC which I built the application from.  It almost seems as if its not seeing the C++ library (not the C wrapper dll I created). 

 

Any advice?  I've even tried putting both .dlls in the system32 directory.  

0 Kudos
Message 1 of 15
(7,250 Views)

I stripped down this VI to get to the bottom of it.  This is the actual error I get:

 

"Missing external function from function.dll:  ?DestroyController@@YAXPAXH@Z:C in test.vi"

 

What is strange in the Call Library Function, I can select the functions from my DLL, but the function prototype on the bottom displays:

 

"void  ?DestroyController@@YAXPAXH@Z(int32_t controller, int32_t index);"

 

The program still works fine on my PC, either in development environment or in .EXE built application, but not on a different PC as an EXE.

0 Kudos
Message 2 of 15
(7,249 Views)

Ok I fixed the above ?function@@ problem.  I added "extern C" to each function call in my .cpp wrapper.  I was unaware Labview library calls don't support C++.

 

But, still seeing same problem.

0 Kudos
Message 3 of 15
(7,242 Views)

dre99gsx,

 

How are you defining the path to the DLL? Are you doing it from within the Call Library Function node, or by wiring a path into the node on the block diagram? Also, do you have any other support files that the VI uses that it might not be finding? You may want to try building a version of your EXE that you can specify the exact location of the DLLs, just to make sure their locations are known by the EXE. Also, are you always keeping the DLLs in the same folder that you are specifying to call the wrapper?

Will
CLA, CLED, CTD, CPI
LabVIEW Champion
Choose Movement Consulting
choose-mc.com
0 Kudos
Message 4 of 15
(7,213 Views)

Problem fixed.  Unbeknownced to me, I was building the .DLL in debug mode.  I switched to release mode and aside from a missing msvcr80.dll file (using depends.exe), she fired right up and worked.  Its the little things sometimes that bite you...

 

Hopefully this helps anyone else with the issue.  I had also installed the latest Visual C++ 2008 redistributable package before hand, although the error still occured after doing so.

 

Thanks.

0 Kudos
Message 5 of 15
(7,204 Views)
And to ellaborate, I installed Labview dev. env onto a 2nd pc.  It was there that once I loaded the original .VI, it complained of the side-to-side configuration error.  I then went hunting for missing .dll's. 
0 Kudos
Message 6 of 15
(7,195 Views)

OK.  I am getting this error.  I have built a VI's from a DLL provided by a thrid party.  The program works great on my development system.  However when I transfer it to another PC I get this error.  I only have 1 DLL and .h file for this function.  It is a USB to UART Bridge CP210X.  I have attempted to put the dll in the folder with the program, a folder in the same path as on the developmental system, the system 32 folder nothing seems to work.  I am running Labview 8.6. 

 

When I build the .exe file without the VI's from the DLL in the Sources section I get missing front panel error.  When I put it in the Sources section I get an Resource not Found Error.

0 Kudos
Message 7 of 15
(6,836 Views)

How are you defining the file path for the dll?  You should probably wire in a default data directory constant and then put the dll in the data folder (this folder should be at the same level as your application).

 

Please let me know if you have any questions.

Justin Parker
National Instruments
Product Support Engineer
0 Kudos
Message 8 of 15
(6,804 Views)
I ran the build vi's from DLL application in Labview to create a series of VI's from the DLL.  The stand alone application works on some machines but not others. 
0 Kudos
Message 9 of 15
(6,784 Views)

What are the differences between the computers?  Different or same operating system?  How does it now work- errors?

 

Kristen H.

0 Kudos
Message 10 of 15
(6,763 Views)