![]() If I do ExecuteSystemCommand( "cmd.exe /c dsquery" -1 ), it works in that this just brings up help text for the dsquery command. Interestingly, with the older ExecuteShellCommand, I find that the cmd.exe /c is not needed with my dsquery command. I am using "cmd.exe /c m圜ommand" format as your help file indicates. Note that in production with ExecuteShellCommand, I have always used the parameter of 1 to tell it to wait. I have tried ExecuteSystemCommand without a timeout parameter, with a parameter of -1 and a parameter of "-1". The full command is as follows: (I have not shown the specific info below for security reasons)ĭsquery group "OU=xxxx,OU=xx Groups,OU=xx,DC=nnnn,DC=adroot,DC=yyyy" -limit 0 -o dn Testing Once the data starts showing, it only takes another second or two before it completes. When I run this command interactively in a command window, there is a 2-3 second pause before data starts showing in the window. The specific command I am using "dsquery" with various parameters. If I watch with Task Manager, the FM app will immediately show as "not responding" when it hits the script step with this command in it. In my testing, it appears that if a command is one where it does not start writing output immediately, it will hang FileMaker with ExecuteSystemCommand. The app shows as not responding in Task Manager and has 0% CPU and the memory allocation does not change at all. What is happening is that the FM application or FM server is hanging. Note that this error also exists with FM Server Advanced 11v3. When I run manually, I am seeing the same behaviors.īE Plugin: 2.0.1 (loaded in FM for interactive and as a server plugin for FM server)Įnvironment: I am in a large organization that is mostly Windows based and is running Active Directory.įM Version: FileMaker Pro Advanced 11.0v3 and FM Server Advanced 11v5. Normally, my task executes on the FM server as a scheduled task. It has been running fine with ExecuteShellCommand for over a year using BE plugin 1.3.1 / 1.3.3 / 2.0.1 I have a task that is currently using the ExecuteShellCommand function and am trying to switch over to ExecuteSystemCommand. I have encountered an odd situation with ExecuteSystemCommand. fileĭrwxr-xr-x 2 root wheel 64 Feb 7 08:22. VolumeIcon.icns -> System/Volumes/Data/.VolumeIcon.icns He might have more insight.īE_ExecuteSystemCommand ( "ls -al" 10000 )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |