Teststand 3.5 deployment error: "Error: The following file(s) could not be copied:"

[Swill]

I am trying to deploy a project in TestStand 3.5 and I am using LabVIEW 8.2.  When I build my project, I always get the following error message "Error: The following file(s) could not be copied:".  Then it lists about 20 VI's that it is apparently unable to copy.  The VI's listed appear to be randomly chosen from the 8 LabVIEW libraries I included in my TestStand workspace file.  What are the possible reasons that TestStand is unable to copy these VI's?

As a side note, I have successfully mass compiled all the VI's without any errors.

[Caseyw]

Hello,

I would be glad to help you out with this issue; to start with, I could use some more specific information regarding the error you are seeing. Could you please attach a *.txt file containing your build status log? This will help me to see which specific files can not be copied.

How many VIs are you including in your TestStand workspace? Does it seem like the "could not be copied" error is happening for every included file, or just some files? I would recommend creating a very simple workspace that contains only one of the problem VIs that can not be copied. If you can reproduce the issue with a very simple workspace, I would be glad to take a look at the workspace (and all included files) directly and investigate the issue further on my end.

I am sure that we can work together to determine exactly what is going on here; have a great day!

Regards,

Casey Weltzin

Applications Engineer

National Instruments

[Swill]

Hello Casey,

I have created a new workspace from scratch with some simple VI's that demonstrate the issue.  Please look at the attached folder that includes the code and a text file of the build status log.  This log looks a little different from my original, but it still has the same error.  This code was generated in TestStand 3.5 and LabVIEW 8.2.1.

It appears to give this error on (some) files that have a decimal point in the filename.  This error started occurring when I upgraded from LabVIEW 7.1 to 8.2.

Thank you.

[Patrick_P.]

Hi SWill,

We greatly appreciate you attaching the example workspace.  It looks like this might possibly be a bug in either TestStand or LabVIEW.  I am going to look into this, and I will keep you posted.

[Patrick_P.]

Hi all,

It looks like this problem can be avoided by not adding the LLB directly to the workspace.  TestStand will parse through any deployed sequence files and determine which VIs need to be deployed (including subVIs).  The only scenario where the LLB needs to be added directly to the workspace is if the VI is being called through VI Server.  In this case there is no way for TestStand to know that a VI is being called dynamically and needs to be deployed.  Even though this is a workaround, a corrective action request has still been filed to R&D to have this issue fixed in future versions of the software.  Sorry for any inconvenience this has caused.

[Phil_T.]

I have a similar problem except that I am using TestStand 4.0 and Labview 8.2. However my problem is the .seq files could not be copied instead of the .vi files. Anyone have any suggestions?

[Josh_L1]

Hi PhilT,

It looks like this question has been answered by snowpunter on your new thread. I'm just posting the new discussion thread below for reference to other potential knowledge seekers.

http://forums.ni.com/t5/NI-TestStand/Build-Error-The-following-file-s-could-not-be-copied/m-p/171834...

Regards,

Josh L.