Error -123002 or -123011 When Compiling LabVIEW FPGA Code Locally

Updated Dec 22, 2023

Reported In


  • LabVIEW FPGA Module
  • FPGA Xilinx Compilation Tools

Operating System

  • Windows

Issue Details

I have installed the LabVIEW FPGA Module and am receiving one of the following error messages upon compilation of my FPGA VI:
  • An error occurred attempting to connect to this compile server
  • Error -123002 - NI-Farm: No worker has registered the given capability name.
  • Error -123011 - NI-Farm: Farm server is not responding. Be sure the specified hostname is correct, the server is running and configured to accept remote requests.

How can I fix this error and successfully compile my code?


When compiling locally, these compilation errors can have various root causes. Try the steps below to rectify these issues. If you are experiencing issues when compiling using the FPGA Compile Cloud Service, you will need to follow other troubleshooting steps for Cloud compiling.

  • Check if the FPGA module is correctly installed on your PC. You can do this by checking it on NI MAX or NI Package Manager (recommended).
  • Restart the FPGA Compile Worker on the computer you are compiling on:
  1. Open the Start Menu and search for FPGA Compile Worker. 
  2. Select FPGA Compile Worker. A notification will appear with the message Compile Worker is running
  3. Restart the compilation. 
  • Confirm the correct version of Xilinx Compilation Tools is a registered capability:
  1. ​​After starting the FPGA Compile Worker, click on its icon located on the taskbar. 
  2. The LabVIEW FPGA Compile Worker dialog box will open. Note the Xilinx Compilation Tool version is listed as a registered capability under the Jobs section. 
  3. If the version listed does not match the compatible version for your LabVIEW FPGA Module and FPGA target, install the correct version onto the computer. 
    1. Note: It is best to use the drop-down selectors to find the version of the Xilinx Compilation Tools that you need. Section 3 on the FPGA compatibility page, Xilinx Compilation Tools & Corresponding Hardware Support, lists the minimum version of the tools needed. For example, compilations for non-Virtex II targets that are listed under ISE 10.1 in the table will need the most recent version of the ISE compiler that is supported in your LabVIEW version, not necessarily 10.1. 
    2. Make sure to restart your computer after installing the Xilinx Compilation Tools or you may still run into Error -1230022.
  • Verify TCP port 3582 is open on your network as this is the port used by the worker and sever to communicate.
  • Make sure the NI System Web Server service and the NI Authentication service are running. These two services are needed by the compiler to work properly.
  • Confirm you are compiling for the correct target if you are running an example from NI Example Finder. For example, the Digital Line Output - R Series.lvproj example is targeted for a PCI-7831R, which requires Xilinx Tools 10.1. If you intend to compile for a different FPGA target and therefore have a different version of Xilinx Tools installed, you will receive one of the above errors if you do not change the target in the example project.
  • Confirm you have the correct version of the .NET Framework installed by checking the documentation of the version of Xilinx Compilation Tools you have on your machine. 
  • Isolate the issue to either the development computer or the compile server by using another development computer to compile example code for the same target.  If the error occurs, the issue is likely with the server.  If the error does not occur, the issue is likely with the development computer. In that case:
    • Repair the installation of the FPGA module if the problem is with the development computer.
    • Repair the installation of the compile tools if the problem is with the compile server.

Additional Information

If you are using LabVIEW FPGA Module 2013 SP1 Xilinx Tools 14.4, make sure to install the LabVIEW FPGA Module 2013 SP1 Xilinx 14.4 f1 Patch. This patch addresses an issue where compile worker fails to start if Microsoft .NET 4.5 or later framework is not installed.