Error -307661 NI VeriStand Failed to Deploy the System Definition File

Updated Dec 11, 2020

Reported In

Software

  • VeriStand

Issue Details

  • I have recently updated my version of VeriStand
  • I am trying to open a VeriStand project that I created in a previous version or VeriStand
  • I added files from a previous VeriStand project to my current project and now it failed to deploy

When deploying my NI VeriStand Project I see:





Error -307661 occurred at NI VeriStand Gateway.lvlib:VeriStand Server Wrapper.vi >> NI VeriStand Server.lvlib:NI VeriStand Server.vi

Possible Reason(s):

NI VeriStand: NI VeriStand failed to deploy the system definition file

Solution

This error occurs when a LabVIEW model that was created in a previous version of LabVIEW, is added to your VeriStand project. 
Different versions of VeriStand require a specific version of LabVIEW Real-Time. The LabVIEW Models need to be recompiled in the updated or corrected version of LabVIEW and then readded to the project.
The version of LabVIEW required is the same as the version of VeriStand you are using. For example, VeriStand 2019 uses LabVIEW 2019 runtime so LabVIEW models must be compiled in LabVIEW 2019. For clarity, check the readme for the version of VeriStand you are using.
  1. Ensure you have the correct software installed on your host PC and target. Check the readme for the version of VeriStand you are using to find the versions of the software needed and ensure the versions on the host and target match.
    1. Installing Software on Phar Lap Real-Time (RT) PXI Controller
    2. Installing Software to Offline NI Linux Real-Time Targets
  2. To verify VeriStand is installed correctly on the target plug a monitor into your 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"
  3. Once you receive error -307661, VeriStand will not successfully deploy even an empty project until your target is restarted. Open up NI Measurement and Automation Explorer (MAX) and select the target (e.g PXI, cRIO) you are deploying to and click Restart
  4. Wait for the target to restart and give it a minute to start the VeriStand Engine and connect with your host PC.
  5. Either rebuild all of your LabVIEW models in the required version of LabVIEW or you can identify the specific models you need to rebuild (suggested only if you have many LabVIEW models and rebuilding them all would be time-consuming)
    1. To identify specific models that need rebuilding create an empty project and add your LabVIEW models 1 by 1 to identify the model(s) causing the issue. Follow steps 3 and 4 to restart the target once the error occurs again, or you will not be able to deploy any VeriStand project. 
  6. Check the readme for the version of VeriStand you are using to find the version of LabVIEW the models need to be built-in.
  7. Use the LabVIEW VI source for the LabVIEW model to build the model for use in NI VeriStand
  8. After ensuring the target has been restarted since the error was last received, add the model to a VeriStand project and try to deploy the project. 

Additional Information

If a monitor is attached to the display/console out of your target, you will see a failure message be printed to the console out that provides more detail.
For example, using VeriStand 2020 with a model created in LabVIEW 2019 (incorrect version, LabVIEW 2020 is required) deployment prints this error on the console:
Can't find liblvrt 19.0