NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime "vi is not executable"

Hi All.
 
 
I have a problem with the base package / Runtime option.
 
I have build a seq in the editor, and it runs without any problems, all my files are on a network share, also the configuration.
 
If I start the NI Simple OI on my developer PC, then it works ok, also when I change the labview adapter to Runtime
Then I want to run this seq from a new PC only with the base package, but then I cant run any of my custom step types anymore, it tells me that the VI is not executable.... but how can I found what it is wrong...... if I change the license (I have a ´VLM) to a TS debug version... then it works...
 
I am not using the deploy tool, the file is called from the same place as my developer PC, the paths and everything is the same.
 
I have tried to rebuild the OI, I found a thread on the forum, that stated that could be the issue... but it was not in my case.
 
Any ideas ???
 
Regards Thomas
0 Kudos
Message 1 of 4
(3,257 Views)

Hi Thomas,

Have you tried putting the viSearchPath tag in the ini file that you will find in the OI exe file directory.

Its the same format as the labview.ini file.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 2 of 4
(3,255 Views)
Hi Ray.
 
Thanks for your try... but it was not the solution.
 
I found out that the VI's in TS like get and set parameter is saved in an older format when installed (LV6), så the runtime server was not very happy to call these VI's, so after I had gone into devel mode, and resaved all VI's (mass compile), then everything was working again.
 
 
/Kind regards Thomas
0 Kudos
Message 3 of 4
(3,222 Views)

Ah, the ol' mass compile solves all.

Glad you sorted it out.

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 4 of 4
(3,219 Views)