Deployment build with TS4.1 & LV9.0

[FredTest]

I am having a problem creating a deployment with TS4.1 and LV 2009.

I get the following error pop-up when building. The files are present in the locations searched

How can I get around this error?

ThanksNAdvance

FredTest

[John_M.]

Hi FredTest,

It would probably be helpful for us to take a look at your Deployment Utility Log to get a better idea as to what may be happening. For TestStand 4.1, you can find this log file at <TestStand Public>\Cfg\DeploymentUtility.log. Please reply with the log attached, and we will look over it.

(For TestStand 4.0 and previous versions, the path for the Deployment Utility Log is: C:\Program Files\National Instruments\TestStand x.x\Cfg\DeploymentUtility.log)

Also, do you have other versions of LabVIEW installed, or only LV 2009? If you are trying to use a VI which is saved in the wrong version of LabVIEW, this error can happen. In that case, doing a mass compile on the VI's directory can resolve the issue. Also, if you have a subVI which is missing, that can trigger this message. For troubleshooting, it could be helpful to save a copy of this VI to outside of the LabVIEW installation. Then, use the copy in your TestStand sequence.

Best Regards,

John M

[FredTest]

Only 2009 is used on this station

Thanks for your help

[John_M.]

Thanks for the log. Next, it would be helpful for us to take a look at the .tsd file for your deployment.

Also, are you deploying the TestStand Public directory?

Lastly, we have a tool called the TestStand VI Search Tool. This tool allows you to specify a VI, and it will search all steps in the open sequence file LabVIEW steps. In each LV step, it will search its subVIs for the specified VI. Please run this tool and search for the "Convert PID Parameters.vi". Then, let us know what information the tool returns for you.

Thanks,

John M

[FredTest]

Thanks for the Reply.

At first I was deploying the Test Stand Public directory per refernce manual. I forgot to disable it hence aborted.

Attached is my .tsd file (it has a .jpg extension) change to .tsd

In addition, i ran the TestStand Vi Search tool and looked for the Convert PID Parameters.vi:

Results:

Expand/Collapse All Step Results

VI Search Results

Search:	Convert PID Parameters.vi
Station ID:	IVPFLASH
Date:	Thursday, September 30, 2010
Time:	5:31:44 PM
Operator:	administrator
Sequence File:	C:\Rockwell Collins\811-5551-001\Sequence\811-5551-001.seq

---

Search Complete - No Results Found  Expand/Collapse All Step Results

VI Search Results

Search:	Convert PID Parameters.vi
Station ID:	IVPFLASH
Date:	Thursday, September 30, 2010
Time:	5:31:44 PM
Operator:	administrator
Sequence File:	C:\Rockwell Collins\811-5551-001\Sequence\811-5551-001.seq

---

Search Complete - No Results Found

[John_M.]

Thanks for the additional information, although I am still confused on one point. Have you run the deployment utility with the "Deploy Files in TestStand Public Directories" box Unchecked (as shown in the attached picture)? Please run the Deployment Utility with that box unchecked and post the deployment log for that deployment for us to look over.

Thanks!

John M

[FredTest]

see attached. Thanks a bunch for your help

[John_M.]

Thanks! As a next step, please save a copy of the VI, Convert PID Parameters.vi, to somewhere outside the LabVIEW installation. Then, use this new copy of the VI in your sequence rather than the copy inside the examples directory. Once you've had a chance to do this and rerun the deployment utility, please let us know the results.

John M

[FredTest]

I did that and successfully created my deployment. Afterwards, i installed the deployment on the other computer and cannot run the sequence.

I get the following messsage:

"This file does not have a program associated with it for performing this action. Create an association in the folder options control panel."

What is this about?

I installed TestStand afterwards and activate the deployment engine and still get this error.

Thanks a bunch for your help

FredTest

[FredTest]

In addition, the only way to run the sequence is to run with Sequence Editor. Is this how TestStand works?