Building a TestStand Deployment that Includes VIs in a LabVIEW Class may Sometimes Produce a Bad DeploymentPrimary Software: TestStandPrimary Software Version: 4.2 Primary Software Fixed Version: N/A Secondary Software: LabVIEW Development Systems>>LabVIEW Base Package
Problem: I am trying to deploy my TestStand system. I am using LabVIEW, and some of my code modules are VIs in a LVOOP class, or call VIs that are in a LVOOP class. When I deploy my system using the TestStand deployment utility, the build completes fine, but I get error -18002 on my target machine. If I open one of these VIs in the <Image> folder that was produced by the deployment utility on my development machine, I see that it is marked with a 'dirty dot' and needs to be re-saved.
Even when I do a source distribution of my VIs using LabVIEW, I still see the same problem. Solution: There are two potential ways to solve this problem:
If you believe that you are experiencing this issue, please contact National Instruments support at www.ni.com/support Related Links: KnowledgeBase 4V58878Z: -18002 Errors in TestStand Attachments:
Report Date: 04/28/2009 Last Updated: 11/20/2009 Document ID: 4WRAKGT3 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
