AnsweredAssumed Answered

Remaining issue in FileMaker Server 13.0v2 with Perform Script on Server in multi-file solutions

Question asked by CamelCase on May 31, 2014
Latest reply on Mar 5, 2016 by Chris Irvine

Summary

Remaining issue in FileMaker Server 13.0v2 with Perform Script on Server in multi-file solutions

Product

FileMaker Server

Version

FileMaker Server 13.0v2

Operating system version

OS X 10.9.3, OS X 10.8.5

Description of the issue

When running a script with Perform Script on Server from a file that uses another FileMaker file as an external data sources, but where that external data source has not (yet) been "touched" by the FileMaker Pro user, the script performed on server is apparently not able to open the second file on its own. The script fails and an error code 100 "File is missing" is created in the server logs.

Steps to reproduce the problem

See above.

Expected result

Script performed on server can access any files that the account the script is performed with have access to.

Actual result

The script fails and an error code 100 "File is missing" is created in the server logs.

Exact text of any error message(s) that appear

Schedule "MyScriptName - Developer 9" scripting error (100) at "MyFileName : MyScriptName : Set Field".

Workaround

Anything that will "touch" the second FileMaker file before the script is performed on server seems to do the trick. Right now I'm using a "go to layout" right now, but I suspect any action that directly references the second file will do the trick.

Outcomes