Skip to main content
Solved

System Caller PSExec Running a workspace remotely

  • May 17, 2020
  • 1 reply
  • 9 views

ciarab
Contributor
Forum|alt.badge.img+9

Hi 

 

I was wondering would anyone know what I am doing wrong here? I need to run an FME workspace on a second machine in an automated way from my first machine. So I am using the systemcaller and passing the following using PSExec to remote call the fme workspace on the second server. Nothing is happening and im getting the exitcode 1

 

PSExec \\myservername "c:\Program Files (x86)\FME2019\FME.exe" d:\FME_Workspaces\test.fmw

 

If I run the above in cmd directly this runs exactly how I expect, is there something I am missing on the system caller side?

I have tried a few variations by adding cd C:\Windows\System32 before PSExec but I cant seem to get anywhere. It is essential I find a method to start an fme workspace remotely from the first machine, seems like it would be easy to do ?? Any ideas?

 

Thanks

 

0684Q00000ArERpQAN.png

Best answer by ciarab

Okay turns out I need to put the PSExec.exe into the following location C:\\Windows\\SysWOW64 I just had it in C:\\Windows\\System32 which worked ok from the cmd but not within fme . Persistence finds an answer!

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

ciarab
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • 167 replies
  • Best Answer
  • May 17, 2020

Okay turns out I need to put the PSExec.exe into the following location C:\\Windows\\SysWOW64 I just had it in C:\\Windows\\System32 which worked ok from the cmd but not within fme . Persistence finds an answer!