"Deployment Completed With Errors" When Deploying my VI to an RT Target

Issue Details

"Deployment completed with errors"

As illustrated below, no additional information about the cause of the issue is displayed.
 

I have noticed that the message can appear during deployment under the following scenarios:

• I have modified my LabVIEW project recently by including a new VI or functions from a new toolkit.
• My LabVIEW project uses NI-XNET functions in a VI to read a cluster from a registered database.
• My LabVIEW project includes NI-XNET Sessions, as shown in the image below.

Solution

The "Deployment completed with error" message is usually related to a driver or module that failed to be correctly deployed due to invalid settings or configuration of the Real-Time target. In other less common circumstances, it can be caused by corruption in the software. Possible solutions to the issue are shown below:

• You can verify if, during the modifications, some controls, subVIs, or functions got corrupted by running a Mass Compile on your project and checking for a VI listed as Bad VI, so you can open it and check for errors. For further information about the Mass Compile process, please refer to the resource: How to Mass Compile in LabVIEW.
• If you use NI-XNET Sessions or functions in your LabVIEW project, verify first that the database can be deployed to the target. LabVIEW can't deploy NI-XNET databases to a password-protected target. To work around this, you can:           
  • Temporarily remove the password from the target before deploying the project.
  • Use the Alias Manager in the NI-XNET Database Editor to manually deploy the database to the target first. For detailed instructions, refer to the resource: How to Deploy XNET Database into Real-Time Targets.
  • Programmatically deploy the database by calling the XNET Database Deploy VI, and including the username and password in the IP address string, as shown in the image below. 

• If you still can't deploy the NI-XNET database or the project, you can try fixing the issue by repairing the NI-XNET driver. Please refer to the article Repair Software In NI Package Manager (NIPM).
• Finally, ensure that the chassis modules are well connected and don't remove them even if you previously deployed the code. The modules are hot-swappable but must be connected when you deploy the code.