Ce contenu n’est pas disponible dans votre langue préférée.

Le contenu est disponible dans une autre langue. Votre navigateur peut inclure des fonctionnalités qui vous aideront à traduire le texte.

Error 1 When Building Executable in LabVIEW

Updated Nov 17, 2023

Reported In

Software

  • LabVIEW
  • LabVIEW Application Builder Module

Issue Details

I'm trying to build a new executable from my LabVIEW project, when I press the Build button I receive the following error: 

Error copying files.
Source:..\....\test.exe
Destination: C:\Users\....\Documents\test

Librarian Path Location.vi"
Error 1 occurred at AB_Destination.lvclass:
Copy_File.vi->AB_Source.lvclass:
Copy_SourceItem.vi

or

LabVIEW: (Hex 0x1) An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

What is the problem?
 

Solution

  • The problem may be caused by anti-virus or Windows security policy on the development computer.
    • In order to solve this issue, you can try the following:
      1. Disable any anti-virus temporarily for troubleshooting.
      2. Run LabVIEW as administrator by right-click LabVIEW shortcut and select Run as administrator. 
      3. Make sure that the LabVIEW and shared folders are set to read/write instead of read-only.
      4. Open LabVIEW and then your project. 
      5. Build your executable. It should build without this error.
      • Note: In case you shutdown, restart or log off your computer, LabVIEW will return to the default privileges. 
    • If these steps resolve your issue, you may choose to examine your anti-virus and permissions settings in Windows for the source of the problem. LabVIEW does not normally require administrative rights to build applications, and works with most anti-virus software.
 
  • If you are using a low-level driver in your project, such as user32.dll, you may encounter this error when trying to include the shared library in your build. To resolve this issue, you can try the following:
    1. If using a Call Library Function Node, set the path to just the name of the dll, such as user32.dll in the Call Library Function Node settings. Do not specify the path as the full path to the dll.
    2. In your build specifications, navigate to the Additional Exclusions tab on the left side
    3. Check the box next to Exclude dependent shared libraries. This will cause the executable to rely on the operating system of the target computer to find and use the appropriate low-level driver that should already come installed with the operating system.
    4. Build your executable. It should build without this error.
 
  • If you are building a Real-Time executable in LabVIEW for an PXI, the error can occur due to the set options in the RT build specifications.
    • Try to disable the "Include RT PXI Target (XX.XXX...) hardware configuration" under the Advanced tab.
KB_PIC.png
 

Additional Information

If you want to configure LabVIEW that always will run as administrator, here are some suggestions how: 

Related Links

Additional Exclusions Page (Application Properties Dialog Box)

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.