Error 63 - System Definition File Cannot Be Deployed to Real-Time (RT) Target from VeriStand

Updated Sep 18, 2023

Reported In


  • VeriStand
  • LabVIEW

Operating System

  • NI Linux Real-Time

Issue Details

I tried to deploy a system definition file to a PXI RT system, but the deployment failed with this error message:

The VeriStand Gateway encountered an error while deploying the System Definition file.

Error 63 occurred at Project Window.lvlib:Project >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to


This error can be resolved by trying the following steps:
  1. Make sure the NI VeriStand RT Engine is installed on the desired target. To verify VeriStand is installed correctly on the target, plug a monitor into the target if there is a display port out. Restart your target and after a minute you should see the monitor/console out say NI VeriStand engine idle. Awaiting command.
  2. Reboot the system, check the BIOS of the PXI controller to make sure the Disable Startup VI option is not selected, and verify that NI VeriStand.rtexe begins running.
  3. Check that the system is not in safe mode.
  4. NI VeriStand.rtexe will be damaged if you connect to the RT target from LabVIEW explorer when NI VeriStand.rtexe is running. You would need to reinstall the NI VeriStand RT Engine to the RT system and reboot the system. 
  5. If the error persists after reinstalling the VeriStand RT Engine, you may need to reformat the target that you're deploying to to resolve potential corruption or issues affecting the system outside the current installation of the VeriStand RT Engine.
  6. Ensure you do not have a firewall or other network protocols blocking the connection to the target.
NOTE: If you want to deploy a LabVIEW program without destroying the NI Veristand.rtexe, select Disable Startup VI in BIOS to boot the RT system without the VeriStand Engine first. There is also a tool to Reset VeriStand as Startup, but the code is provided as is and is not maintained by NI.

Additional Information

The root cause of this problem is that, to deploy the system definition file, we need to see a TCP connection to the NI VeriStand RT engine. The steps above try to ensure that the engine is properly installed and not in an unknown or corrupted state.

When you install the NI VeriStand RT engine on a system properly, you will see NI VeriStand RT engine launch as soon as the RT system is booted. This can be seen on the console out screen of the RT system.