deployment utility wont copy files

[charlestippett]

Hello,

I am using tests stand 3.5 and am having problems deploying a labwindows cvi project. I am trying to deploy an EXE and config file that I have in my bin directory but for some reason it wont copy in the deployment utility to the installer destination. I can see the file and see it in the deployment files but it just wont copy. Any thoughts?

Thank you for your timem

Charles

[James M]

Hi Charles,

Do you see the EXE and config file in your image folder under .\image\target?
Does the deployment utility have any error messages or warning when you build the installer?
Is there something special with the directory you are trying to install to on the target machine?
Maybe you could post the TSD, EXE, and config file?

Regards,

[charlestippett]

I figured it out. The directory path in the tsw file was not being recognized.  Thank you for the help.

[AllenP]

What directory path was not being recognized?  I am curious what was causing the problem so that we can catch this in the future and give users a better error message when this happens.

Allen P.
NI

[charlestippett]

When i migrate an existing project to a new machine the test stand workspace does not recognize my file paths. even though i am looking at the same directory it wont pick up the files. For example I have gacutil.exe sitting in a bin directory that is an output from a CVI project. When i load up the TSW file the gacutil.exe item in the tree has a red X over it until i manually look for the file in the exact same place that it is already looking for it.

[Captain_Jack]

Allen,

I've run into something like this before, where a binary (.exe) file that was not in one of the TestStand Search Directories would get 'lost', while other files in the exact same directory where found by the deployment. This appears to have happened because the binary file was was not referenced with an absolute path, while the other files in this directory where using absolute paths. When the build was migrated to the Configuration Management build machine, the TestStand workspace 'lost' the file. Our workaround was to make the binary files path absolute.

The deployment utility did not throw a warning that it could not find a file in the workspace, and just omitted it from the deployment when it was built. So we ended up with Engineering builds that worked, but a CM release build that didn't. If the deployment tool did throw an error message, it was lost in the several dozen warning messages that where also thrown (we deploy sequences that reference several separate binary DLL's that aren't deployed as part of this particular deployment, and use expressions for sequence paths and sequence names).

Even though it performed an analysis, it didn't clearly warn that one of the files in the workspace environment had a problem.

Hope this helps...

-Jack