NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem Description: LabVIEW and TestStand Projects Conflict After Deployment Following Upgrade to 2024 Versions

I recently upgraded my LabVIEW and TestStand environments from version 2019 to 2024 on a virtual machine. After the upgrade, I mass compiled my project, which includes multiple LabVIEW projects, VIs, and Python scripts, all contained within a single project folder. The mass compile completed without any errors. I also mass compiled some libraries under Program Files\National Instruments\LabVIEW 2024.

After the compilation, I created a deployment for my project. The deployment process completed successfully without any errors. However, when I tried to run my project post-deployment, I encountered a conflict in two specific LabVIEW projects. TestStand reported a conflict error for these projects.

To resolve the issue, I had to manually open these two LabVIEW projects. When I attempted to close them, I received a message stating that "an attribute of this project has changed," prompting me to save the projects. After saving them, the conflict was resolved. This process must be repeated each time I deploy my project, as these two specific projects consistently encounter this issue.

These two projects have several dependencies, including the OpenG library and NI data types. After deployment, my project includes a new "Support VIs" folder that contains all the dependencies required by the project. I am unsure why only these two projects are affected in this way after deployment and would appreciate any insights or solutions.

 

If i mass compile the project after Deployment (before i resolve the conflict) i get the following errors:


C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\_LaunchHelpUrl.vi (_LaunchHelpUrl.vi)
- The VI expected to be at "C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\Error Cluster From Error Code.vi" was loaded from "C:\work\D\Deploy\target\SupportVIs\Error Cluster From Error Code.vi".


C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\Get Type Information.vi (NI_Data Type.lvlib:Get Type Information.vi)
- The VI expected to be at "C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\Error Cluster From Error Code.vi" was loaded from "C:\work\D\Deploy\target\SupportVIs\Error Cluster From Error Code.vi".


C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\GetRefnumInfoInternal.vi (NI_Data Type.lvlib:GetRefnumInfoInternal.vi)
- The VI expected to be at "C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\Error Cluster From Error Code.vi" was loaded from "C:\work\D\Deploy\target\SupportVIs\Error Cluster From Error Code.vi".


C:\work\D\Deploy\target\SupportVIs\Write PNG File.vi (Write PNG File.vi)
- The control expected to be at "C:\work\D\Deploy\target\SupportVIs\imagedata.ctl" was loaded from "C:\work\D\Deploy\target\VI\Lib\HF\ProjectName\VIs for ProjectName\SupportVIs\imagedata.ctl".

0 Kudos
Message 1 of 2
(165 Views)