Jump to content


  • Posts

  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Billy_G's Achievements


Newbie (1/14)



  1. Thank you, dadreamer! There is, in fact, a dependency on cvirte.dll, which is installed on my development host, but not on the deployment host. I tried installing RTE 5.5, but it would not run on Windows 10, no matter what compatibility settings I pick (I tried all options back to Win 95). So, instead, I matched the version of the cvirte on the development machine (19.0. ...), not of the vendor's code, and voila!
  2. As I have said in my original post, I tried placing the DLL in most of the locations you enumerated, including a directory tree perfectly matched to the project location, with no luck. All the vendor gave me were one LLB and one DLL in a zip file. I just unpacked and added them to the LabVIEW project. There was no driver installation, no subsequent copying of some DLLs but not others. And the fact that the error messages are about missing functions in that DLL makes me think that it is not related to other DLL dependencies. I emailed a zipped up executable to a colleague with a LabVIEW IDE, and I have no idea where he unzipped the files or what his version of LabVIEW was, but he said it loaded without an error message on the first try.
  3. I recently decided to try out the Debug Application or Shared Library feature of LabVIEW for the first time, but I can't connect to any application! I tried running an application both on a local and a remote host. I opened the firewall, the IP is correct, Enable debugging is checked in the application builder, and the application runs, but I always get the "No debuggable applications or runtime libraries found" message. I tried two different applications. What else is there to try? My two Win 10 machines are on a corporate domain. I have local admin access. One runs LV 2017 32-bit IDE, the other - a matching runtime engine.
  4. Hello, I wrote a LabVIEW program to communicate with a hardware sensor using vendor-provided LLB and a DLL files. The program runs fine on my workstation both from LabVIEW IDE and from a compiled executable. The problem starts when I copy the entire executable folder to a target host without a LabVIEW IDE (only with a runtime engine). The application opens with a broken Run arrow and a "missing external function" error message appears for every function call I made to the DLL (see attached). I have tested my application on 5 completely different Windows 10 computers managed by different people. On three of them with various versions of LabVIEW IDE my executable opened with a whole Run arrow and no error message. Two other machines previously had no LabVIEW, so I installed a Runtime Engine 2017f2 32-bit with default settings to match the version of my IDE. Both gave an identical error message. The DLL is always included in the application build. I have tried placing the DLL in every conceivable location on the target host: in the executable folder, in the /data folder, in the c:\Windows and system32 folders... I even created a full folder tree matching the location of the project on the developer workstation. Same error. When I intentionally hide the DLL, my executable prompts me to point to it upon being opened, and when I do, I get all the same error messages. Vendor documentation only asks to put the two files in the same folder. From programmer's manual: " The driver was written in LabWindows/CVI, version 4.0.1 and is contained in a dynamic link library which can be linked with a variety of programming languages." There is no vendor-provided support. One way I actually got rid of the error message was by editing every Call Library Function Node in every VI in the LLB to use relative path to DLL together with the Application Directory VI. However, I feel that there has got to be a better way to compile than by editing a vendor-provided library, especially since it works as-is on some computers. Can anyone suggest what it is? Thank you for your time!
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.