I am running Filemaker Server Advanced and trying to schedule a ScriptMaker Script to be run server-side. I have two databases: 1) testsRecords and 2) messagesDB. The testsRecords DB has a table from messagesDB in it (added as external datasource, fmnet). The script in testsRecords creates a new record in table from messagesDB and runs fine either on a client or through IWP.

When I have the script run using a schedule on the server, however, I get a file is missing error (100) when it gets to the step where the record is created in the messagesDB.

Is there any reason why server-side scripts can only access tables that are local to the database file that has the script?

Did you resolve this issue? I have the same probem and filemaker support hasn't been able to help as of yet.

Nope, still have the problem.

I have the same problem, any news?

Is there any reason why server-side scripts can only access tables that are local to the database file that has the script?

Because that is how FileMaker designed it. They told us that we can not use server-side scripting to write from a served file on one FMS box to a served file on another. And yes, it is a big mistake on their part. We have Interfaces (incoming data from many external sources) on one server which we keep separate because of intensive resource use from our main solution.

But we had to go back to Windows Scheduler to fire it as a bot because server-side scripting would not work.

Edited July 4, 200916 yr by Guest
Added quote

we can not use server-side scripting to write from a served file on one FMS box to a served file on another

If I read the post correctly the problem surrounds 2 files on the SAME SERVER - is the problem still the same in this situation?

That isn't what I read at all. Again ...

Is there any reason why server-side scripts can only access tables that are local to the database file that has the script?

A server-side script can write to another FM file that is being served locally to the file with the running script. But if the second file is being served on another server, it will not and you will receive Error 100 < File is Missing>.

In addition to us being told directly by our FM representative, here is a link where FileMaker answers about it. I also posted to FileMaker website in December and here on forums about the Import Script step not greying out (or not displaying NOT COMPATIBLE) in the script-step itself like it does with other non-compatible steps.

I am dismayed that this entire issue is STILL kept so quiet (by FileMaker) when the first reports were at LEAST seven months ago. At least the script-step (incorrectly indicting it as compatible) should have been fixed for 10.0v2 updater recently released.