TestStand Deployment Issues

[schm1347]

Right now we are in the process of building deployment packages for our test stations in TestStand.  We basically have some model customizations as well as the actual client sequence file, which calls VI's.  These VI's do have sub-VI's which are distributed with the package.  I can get the whole package to deploy (both install and image files), but when I try to run the deployed package on the target computer using a customized user interface, I recieve error -18001.  The error dialog box informs me that the VI cannot be run, because the NI LabView Development System cannot be found.  In my client sequence file I went through all the VI's and made sure they always run in runtime mode.  I also set the LabView adapter on my development computer to runtime v8.5 for when I deploy.  I'm quite baffled at this point as to why I'm still having issues.  Could it be an issue with my user interface instead, or how do I remedy this issue?

Message Edited by schm1347 on 10-26-2007 10:42 AM

[schm1347]

I just dove a little bit deeper into it I discovered that the adapter is not defaulting to run-time I distribute the package as a deployment.  Is there a way to automate this?

[Song_D]

Hi, schm1347,

The adapter info is stored in <TestStand>\cfg\TestExec.ini file. So when you make your deployment, you should include this file and deploy it to the same folder on the target computer, as shown in the attached screenshot.

In general, if you want to keep the TestStand settings on the target machine the same as the development computer, you should include the cfg folder. It includes user management, station global, execution options, etc.

Regards,

Song D

Message Edited by Song D on 10-29-2007 11:36 AM