NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Run executable file on remote computer.

New to Test Stand, so bear with me here...

 

Trying to run an executable file on a remote computer.  The file resides on the remote computer file directory.  I map my controller computer to that drive location and execute it with my controller computer (where Test Stand is installed).

 

I run the "Call Executable" step in Test Stand no problem.  It calls the executable and opens the window for the application.  The problem is that the application opens on my controller computer, not the remote computer.

 

I am not running a Test Stand server on the remote computer.  Is that the problem or is there another way to do this without running a remote server.

 

 

0 Kudos
Message 1 of 4
(6,163 Views)

To run the Executable on the other computer, you cannot just map the drive to be a local drive.  You will need to change your executable call to use a remote call.

 

First you will need to have the Remote EXE Server running on the remote machine.  This server is located in the RemoteServer directory on your TestStand CD, or located in the <TestStand>/Components/StepTypes/CallExec/RemoteServer/ directory (for 4.1 and greater), or the  <TestStand>/Components/NI/StepTypes/CallExec/RemoteServer.  Copy the RemoteEXEServer.exe to that machine.  You will need to configure the server with the Port (default is usually OK and a password (blank is also ok).  You may wish to uncheck the "Show this Screen on Startup" item to avoid seeing this dialog on startup.  Click ok.  You will see the Remote EXE Server icon visible in your tray.

 

After you have done this, you will need to configure the step in TestStand to call on a remote machine.  You can do this by clicking the Remote Settings button for the step configuration.  Check the "Run Executable on a Remote Computer".  Give the Host Name, port, and password you specified before.  You may need to update the File Pathname since the remote computer cannot use TestStand Search directories.  I recommend using the full path on the remote machine here.  When you run the step, it should run on the remote machine.

 

Allen P.

NI

0 Kudos
Message 2 of 4
(6,159 Views)

Hello,

since am facing some trouble getting the think to work with RemoteEXEServer.exe, i though it would be a good idea to post it here. I know dis Topi will celebrate ist 10th anniversary  next month. 

Am using Teststand SP1 17.1.0.130 (32-bit).

 

i did AllenP's description.Trying to put a password already throws an exception from HRESULT:0xFFFFBBA4 Error Code: -17500, Operation Failed.Source: NationalInstruments.Teststand.Interop.Api. see "exception_pwd.png" for details.

leaving di password field empty then running the teststep causes a Run-Time Error: -17502; System Level Exception. See second picture "run_time_error.png"

 

 

 

Download All
0 Kudos
Message 3 of 4
(3,434 Views)

Have you seen the following articles on those specific error codes?

 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019ToqSAE&l=en-US

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Wf3SAE&l=en-US

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019ToqSAE&l=en-US

 

If those don't answer your question, it's probably best to post your question as a new forum post. Since this is an older thread, not as many users will see your new question.

Christine B
Technical Support Engineer
National Instruments
0 Kudos
Message 4 of 4
(3,423 Views)