Solution
The solution to this issue is different for LabVIEW and VeriStand users. See the steps for the software environment you are using:
LabVIEW
This error message is usually displayed because your database has not been deployed to the RT target. Thus, when the VI tries to access the database, there isn't one to reference.
To deploy your database to the RT target follow the steps outlined here.
You can also explicitly deploy the database at run time using one of these two methods:
If you are using I/O names for database objects, you can click on an I/O name and select Manage Database Deployment. This opens a dialog that you can use to assign new aliases and deploy them to the RT target.
- Using the File Management Subpalette VIs:
To manage database deployment from a VI running on the host (Windows computer), use VIs in the NI-XNET File Management palette. (see the image below) This palette includes VIs to add an alias and deploy the database to the RT target.
To delete the database file from the RT target after execution of a test, you can un-deploy the database by using either option described above.
VeriStand
When a VeriStand project contains XNET signals, those signals must be present in a referenced database. Since VeriStand automatically deploys the database file to the RT target as part of the deployment process, you do not need to manually deploy the database. Therefore it is more likely that there is a mismatch between the signals that are defined in the System Definition File and the database file. Here are some scenarios where that could occur:
- If you have previously used a different database, ensure all signals from the old database have been removed from all of your NI-XNET CAN, LIN and FlexRAY cards in the VeriStand System Definition File. Only signals that are present in the database can be used in the project.
- This error can also occur if you have upgraded software versions or moved files around on disk which could break the database aliases. To fix this:
- Open the XNET Database Editor from the Windows Start menu or from the VeriStand System Explorer
- Select Manage Aliases...
- Ensure that any registered database files have the correct filepath specified
- If the database that you want to use is not registered, add a new alias for that database
- After registering the database, open the VeriStand System Explorer and ensure that all XNET interfaces specify the correct database that contains the signals you are using in the project
If issues still persist, remove all signals under the NI-XNET cards and re-add the signals in groups to identify the cause(s).