NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand 2024 Q4 (64-bit) does not run on deployment pc

Solved!
Go to solution

Hi All,

 

We are planning to migrate all our teststand sytems to 2024 Q4 64-bit (now we're on 2021 32-bit). To start easily, I thought let's first create a simple sequence file and see if it runs on a deployment pc. But even this is not working.

 

What I've done:

I created an installer with the 64-bit deployment tool for teststand 2024 Q4 and labview 2024 Q3 (both 64-bit). To run the sequence file on the deployment pc, I use the default batchmodel and the full operator interface (Labview source) that ships with teststand 2024 Q4.

 

I ran the sequence with the "test UUTs" entry point, but then an error pops up:

Nick1991_1-1732887582476.png

 

Does anyone else encountered this problem?

 

PS: I first completely removed old teststand and labview installations before I installed the new versions.

 

 

0 Kudos
Message 1 of 3
(122 Views)
Solution
Accepted by topic author Nick1991

Hi Nick,

 

We have tried to reproduce this by creating a TSD that includes three components in the installer. We checked the "Include TestStand Runtime" option under the Installers tab and ensured the TS runtime, Process model runtime and User Interface conponents are checked like shown below:

 

image.png

 

I have also attached the TSD file we had used to create the installer. On deploying this installer to a clean machine, we were able to run any sequence file in all process models without errors.

 

I feel the difference might be in the way the TSD was created so would you be able to share a TSD file that you had saved or even the screenshots of the relevant tabs to show how the deployment was done. We can then try to reproduce using the configuration you had. Meanwhile, you can also try deploying using the TSD attached to see if you get any difference in behavior.

 

Regards,

trj

Message 2 of 3
(68 Views)

Hi TRJ,

 

Thanks for your reply!

 

Now I know what I've done wrong. I made a custom user interface and included this one and the original full user interface as files (Testexec.exe, Testexec.ini, ...) in the deployment. After installation these files are copied to the public teststand folder, because I configured this in the deployment utility.

 

But apparantly I needed to include the "Teststand 2024 Q4 User Interfaces (64-bit)" in the installer, like you did. Probably because this installs the required dependencies for the user interfaces.

 

Anyway, after I included this I was able to run our sequence files with our custom user interface.

 

Thanks!

0 Kudos
Message 3 of 3
(51 Views)