I reconfigured my scheduled script on the server to run a new script whose single script step (Perform Script) runs the slave machine's single script (now functioning as a call-back script). This script executes properly from a client session. To defeat me, when the server schedule executes that same script the single Perform Script step in it generates an Error 100 in the Server Log - so it doesn't execute and I'm beat.
The suggestion of using a slave (robot) machine to overcome script steps that are not supported server-side is to run EVERYTHING on the robot machine, not have the server initiate something on that robot machine.
I'm not a big fan of robot machines (need to have a user logged into the OS at all times, need to baby-sit that the files are properly opened, need to monitor that the scripts execute...
You can still do everything server-side but you need to do an intermediate step: export to the FMS documents folder in csv format, import that into the other table. FMS does not support direct FM-to-FM importing.
Not sure how much data we're talking about on each execution but you could do this without the import and export by storing all the data in variables and transporting it that way between the tables.
1 of 1 people found this helpful
FMS will not import from within the same file. You need to export out to an
intermediary file and pull the data back in. That might be your problem.
Direct/FaceTime/Text - 781.223.8884