Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

RunShellScript 'not recognized command...' problem on windows


This topic is 4613 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi there,

I'm trying to run a command with RunShellScript, to use PsExec on windows (win 7 pro x64 / FMP11adv / SM 4.132).

(this exe allows to run a command or batch on a remote computer, allowing me to control my FileMaker Server over command line)

the exe is in C:\Window\system32, and from within a system cmd window, everything is working fine.

But using ScriptMaster RunShellScript (from the example file), it returns a shell error :

java.lang.RuntimeException: 'psexec' is not recognized as an internal or external command, operable program or batch file.

I tried some native commads, such as ipconfig, netstat, copy, systeminfo, ... : everything is working fine with SM.

I also tried different syntaxes : psexec , psexec.exe , C:\Windows\system32\psexec.exe etc. but to no avail.

These are my first attempts with this RunShellScript module... Am I doing something wrong ?

Thanks !

Posted

Any reason why you can't just use the Send Event script step to fire off the command line or shell script? Or do you want to capture the return result?

Posted

Actually, I didn't even try, because this is just some testing I'm running. But the return result could be helpful indeed.

So, I tried with Send Event, and I got the same results.

I double-checked everything, the presence of the exe in the system32 folder (even if this was obvious, since everything works fine in a regular command shell), the windows variables (%PATH%), and all.

Then something came into my mind : I copied the exe in the C:WindowssysWOW64 folder (the 64bit equivalent of system32) and tried again with send event : it worked.

So it seems that on a x64 Windows system, Send Event and also the RunShellScript are calling the 64bit version of the exe, even if one specifies its full (32 bit) path !

The 'duplication to the 64 folder' workaround does the trick for SM too.

This is quite puzzling, and I'd be curious to find any explanation...

Thanks anyway for your suggestion, because it helped me find this out.

This topic is 4613 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.