Deployment missing directory

[jvh75021]

My deployment is missing a directory and its files. The file is C:\Automation\Avionics\Database\TestStand Results.mdb. The directory and file are listed in the workspace file. What else must I do to make it get picked up?

Thanks,

jvh

[~jiggawax~]

A couple things I can think of:

-Make sure that your search directories can see that file...  i.e. that file is located directly in a search directory or in a subfolder of a searchdirectory with the subfolder option selected.

-In the TestStand Deployment Utility on the System Source tab make sure that you are using the workspace which contains the file.

-In the TestStand Deployment Utility on the Distributed Files tab there is a drop down.  Choose the View Sourceoption and make sure that your file is selected.  Everything in your Workspace should show up there.  Then you can choose the View Destination and point the files to the proper locations.

Hopefully this helps!

[jvh75021]

Thanks for the post.

I found the problem but not sure how to cure it. To troubleshoot I deleted the Database directory and re-added the folder from disk. Turns out there is an NI directory called Database too. I could use an absolute path to my directory or a relative path to the NI directory. How about a relative path to my directory? However I think the build will be OK because the destination is set for the installation directory.

[jdubs]

jvh,

Generally, absolute paths are not best practice because it complicates deployment.  Since that is precisely what you are doing, relative paths will probably serve you better.  You probably want your own database directory.  To use a relative path to it, try renaming the folder something that is not some other default folder.  You may need to replace some paths in your TestStand project.  The Find/Replace utility in the Edit menu should help with that.

Regards,

Jen W

Applications Engineer

National Instruments

ni.com/support

[jvh75021]

---

@jdubs wrote:

jvh,

Generally, absolute paths are not best practice because it complicates deployment.  Since that is precisely what you are doing, relative paths will probably serve you better.  You probably want your own database directory.  To use a relative path to it, try renaming the folder something that is not some other default folder.  You may need to replace some paths in your TestStand project.  The Find/Replace utility in the Edit menu should help with that.

Regards,

Jen W

Applications Engineer

National Instruments

ni.com/support

---

Yep, I would need to replace a lot of references as this project has gotten out of hand with over 1600 VIs. For now I changed the name of the file in the NI directory but really that doesn't seem necessary because even though I set up a absolute path, declaring its destination to be the destination directory seems to place it just fine.

thnaks.

[Rick_Francis]

jvh,

I was trying to reproduce the problem but I was able to get it to work with a few different relative paths.   Note: the TSDU works from the workspace on disk so you have to save the workspace after you add the folder to it.  

Could you try :

Removing the database directory from your workspace.

Add the database directory selecting a relative path.

Save the Workspace.

Anlayze the workspace in the TSDU.

If you don't get the file in the TSDU then go back to the workspace right click on the TestStand Results.mdb and select properties, and post the Path Name.     Also, What version of TestStand are you using?

-Rick Francis