NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Several deployments on same PC

I have several teststand deployments on the same Deployment PC. All my deployments include the StationGlobals.ini and Resultprocessing.cfg for reports. My issue is that some deployments cause other previous deployments to have a runtime error when executing those deployments. See attachment for error. 

 

I use the same base directory for all deployment installations.

The VIs are not broken, it ran before. So it must be an issue with finding them. What could cause my previous deployments to stop working with this error? 

 

Should I perhaps add the searchdirectories.cfg to each deployment? 

0 Kudos
Message 1 of 6
(817 Views)

Have you considered using TestStand environments?

 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x3d9CAA&l=de-DE

 

No complete isolation / sandboxing yet it should do the job

0 Kudos
Message 2 of 6
(783 Views)

Hi Oli

 

No, I have not. Will give it a try.

By The way, I attached a PDF link to two different projects to show my deployment settings, Can you have a look to see if something is off?

 

https://drive.google.com/file/d/1JRj1QvRKjbOfeREHytxkIfaOFnn5rYYC/view?usp=sharing

 

 

Thanx for feedback

 

 

0 Kudos
Message 3 of 6
(779 Views)

I am ooo right now… will take a look soonish 

0 Kudos
Message 4 of 6
(753 Views)

I am not really sure if this works. If it does, I doubt that this is maintainable, too many dependencies between the projects.

So I strongly recommend using environments, even though they might not be perfect.

 

BTW.... I would not install my TestSequence to Program Files (x86)... this is where "real" programs go so Windows takes some extra care about security there

 

 

0 Kudos
Message 5 of 6
(708 Views)

I'll have to investigate, but I think it's the way I created my folders for the VIs. I think there is a SupportVI folder that overwrites when another installation is made.

 

0 Kudos
Message 6 of 6
(701 Views)