RemoteEXEServer.exe Not Working + Exception

[Al_Niz]

Hi Sir ,

am Trying to run an executable on a remote pc from Teststand. looking around i found a possible/easiest solution is to use that RemoteEXEServer.exe (wich is provided by installing Teststand) & Call Executable Teststep.

I configured every thing similar to 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" for details.

[mdoherty]

Have you seen these articles surrounding your error codes?

Error -17500 Using The Property Loader From Caller Sequence: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000001DdMLSA0&l=en-GB

TestStand Error -17502 Using Automation Server: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019ToqSAE&l=en-GB

Michael

[Al_Niz]

hi, 

yess, these 2 articles were di first thing tried.

have you got it to run? remotely? because locally every thing is ok! 

one problem appears  just by typing a password (error -17500 ) and i dont think that i have any influence on that (maybe a bug?). 

by the way am using Teststand 2017 SP1 32bit

[mdoherty]

Hello,

Have a look over this. 

Remote Execution in 32-bit TestStand and 64-bit TestStand: http://zone.ni.com/reference/en-XX/help/370052N-01/tsfundamentals/infotopics/64remoteexecution/

It might be to do with the set up

[Al_Niz]

@mdoherty

Sorry u misunderstood, CallSequence on RemotePC has nothing to do with RemoteEXEServer.exe and Call Executable:

CALL Executable Remote ConfRemoteEXEServerSquenceCALL

[Al_Niz]

did someone ever seen it working?