The solution to this issue is different for LabVIEW and VeriStand users. See the steps for the software environment you are using:
This error message is 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.
It can also occur in a VeriStand project if you have updated the XNET alias to a new database file or version, but have referenced a signal which is no longer present. To resolve this either:
- Update the VeriStand project to reflect the new database.
- Remove the XNET alias in XNET database editor and add the correct database file.
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.
For VeriStand users, this error typically points to a problem in the NI-XNET database itself. Investigate the database and check the validity of the signals in the database.
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.
If issues still persist, remove all signals under the NI-XNET cards and re-add the signals in groups to identify the cause(s).