NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I deploy teststand 3.5 to a different directory?

We did already update setup.ini as instructed:

[SingleDirectoryDialog]
DirText1=4
DirText2=7
Dir1EditLabel=12
Dir2EditLabel=13
Dir1=NIDIR
Dir2=TESTSTAND350DIR

Could there be another reason for the error?

Thanks,
Dave
0 Kudos
Message 11 of 18
(2,322 Views)
The only other time I saw this error was when I tried these modifications on an installation that did not include the TestStand Engine (IE just a sequence file). Since this installation isn't trying to install any basic TestStand components to the NI Default directories, it errors out on those spec file directory assignments.

Let us know if this is the case. Thanks!
Dan Weiland
0 Kudos
Message 12 of 18
(2,306 Views)
Hi:

In the deployment utility, we have checkmarked 'Install Teststand Engine'. This should be sufficient, correct? We are not trying to deploy any of our sequence files using this installer. 

I tried rebuilding the deployment from a different PC and I still get the same error. I've attached our deployment TSD file, setup.ini and template_spec.txt. Are you able to determine from these files what is going on?

Note that without specifying template_spec.txt, the installer *does* allow us to change the directories manually. But we are trying to change the defaults automatically so we don't have to change the directory on every PC that we install this on.

Thanks,
Dave
0 Kudos
Message 13 of 18
(2,277 Views)
Any update on resolving this?
Thanks,
Dave
0 Kudos
Message 14 of 18
(2,215 Views)
Hi Dave,

One thing I noticed was that you're deploying your files from a "deployable image". During my testing I was deploying from a TestStand Workspace instead. I'm continuing to work on my end, but can you try using a TestStand Workspace with the correct sequences specified and see if this makes a difference on your side?

Thanks
Dan Weiland
0 Kudos
Message 15 of 18
(2,199 Views)
Hi:

I couldn't get it to work. We've now abandoned the idea of installing to c:\Teststand. At any rate, it creates a problem for users that need to have both Teststand 2.0 and 3.5 installed at the same time.

However, I have another question. Now that we are using the default directories, can the deployment installer run silently? I could not figure out how to do this. I checked 'Do Not Ask User For Installation Directory' and 'Hide License Dialog' in the deployment utility Installer Options tab, yet both of these show up when running the installer. I also tried running the installer with the '/q /acceptlicenses yes' option but then it didn't run at all.

Thanks for your help.

Cheers,
Dave
0 Kudos
Message 16 of 18
(2,154 Views)
Nevermind - I figured out I can disable the prompts from setup.ini.
Thanks for all your help.
Cheers,
Dave
0 Kudos
Message 17 of 18
(2,148 Views)

Hi,

When you ran the setup exe generated by the deployment wizard for TS version 2.0 you can use the cmd line argument of -noprompt.

I dont know if this still applies with deployment file for TS3.5.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 18 of 18
(2,148 Views)