filemaker server load script

On my computer, I have filemaker client. I can open the database and manually execute scriptmaker script.

Now, I need to execute the script on the filemaker server. I have the admin console open. How do I open the database and execute the script? I tried to click on the database, and I selected the database, selected open, clicked on "perform action", nothing happens.

Also I created a schedule, I run the schedule, I know the script does not run successfully since the data I needed didn't come in. Is there any log file or something to let me know which step is wrong or tell me the script execute status etc? Thanks.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will LovingPresident, Dedication Technologies, Inc.Commented:
I only have a moment right now, but take a look at this knowledgebase article and see if it helps along with the additional links at the bottom.
xiaoyunwuAuthor Commented:
I was able to figure out on the server machine, there're filemaker server and filemaker pro. Filemaker server is where I schedule script etc. Filemaker pro is where to open all the database and make the scriptmaker script. And now I see in the schedule after I run the script, there's a status tell me "scriptmaker script aborted", if I run the script via filemaker pro under that database and execute directly, it works. But if I schedule with server, it does not work, status is aborted. I make the script as simple as open a database, still get the same error, not sure what's the problem.
Will LovingPresident, Dedication Technologies, Inc.Commented:
Well, part of the problem is with your test script using "Open File". That script step is not supported for Server-side scripting. To see which script steps are supported, open Scriptmaker and then your test script. Go to the lower left corner of the Edit Script window and change the "Select Compatibility" option to Server. Only the script steps that are NOT grayed out are available for server side scripts.

I would suggest using the Set Field script set. Select a field that is easy to see the change in or create a new field for test purposes and add it to a layout out. You'll also probably want to use a Go To Record step before Set Field to make sure you're either on the first or last record.

Show script step compatibility
OWASP: Forgery and Phishing

Learn the techniques to avoid forgery and phishing attacks and the types of attacks an application or network may face.

xiaoyunwuAuthor Commented:
Now my problem becomes: how to schedule a script in filemaker pro instead of filemaker server. Or is this possible? Since the script is there already and can run perfectly in filemaker pro manually. I do not know how to and do not have time to rewrite the script. I only want the script to run daily by itself.
xiaoyunwuAuthor Commented:
my version: FileMaker Pro 9
Will LovingPresident, Dedication Technologies, Inc.Commented:
Using Server-side scripting is the only simple way I'm aware of to have something run automatically in the background on a daily basis. There are other ways to do it but all require more involved scripting and setup. If the server-side script was working previously then it should be possible to get it working again.

You may get a clearer picture of what the error is by checking the FM Server Events log. See this FileMaker Knowledgebase article for more info on where to find it:

In addition, the fact that the script runs fine in FileMaker Pro probably means that there is something Server specific that is not right. I can think of two things that might cause that:

The use of an Import File location that is NOT allowed for FM Server - FM Server has a more restrictive set of allowed locations.
A script step that is not Server compatible.

Of those two options, I consider the first one to be the most likely since it doesn't appear that the script has been edited to include a step that is not server compatible.

If the script worked previously, then what has changed? Is the file to be imported being saved in the EXACT same location with the EXACT same name? Is that location one of the allowed location for FM Server? (it might be allowed for FM Pro but NOT server)  When you run it with FM Pro is the file being imported without a dialog or are you getting a dialog popping up indicating that the saved location for the file is not proving to be valid?
Will LovingPresident, Dedication Technologies, Inc.Commented:
> my version: FileMaker Pro 9

Another possible problem. If you are also using FileMaker Server 9, I'm pretty sure that server-side support of Import and Export was not introduced until FM Server 10. I recommend that you:


Check to see what version of FM Server you are running


Open the script with the SAME version number of FM Pro


Check to make sure that all script steps used in the script are compatible with the version of Filemaker Server.
If you moved this database "in-house" did you possibly switch from FileMaker Server 10 to FMS 9, for which Import and Export are not supported?
xiaoyunwuAuthor Commented:
server version: FileMaker Server 9
All the server didn't change, since we used to have someone comes in or remote access our server to make things happen. Since I can't see anything in the scheduled list of server. And there're a lot of open, import steps in the script. I'm guess they somehow run the script somewhere else.

I found this one even though I'm not totally understand it yet.
Will LovingPresident, Dedication Technologies, Inc.Commented:
There are a number of options there though probably the best one is to have the script triggered by the last user closing out of the program. You use the option to run a script on File Close  (under File -> File Options) and it checks to see if Get( UserCount ) = 1  - meaning that person is the last person accessing the db - and then triggers the script.

However, that may not work if your Import file is not local on the machine that is running script. There is also a plug in called "ScriptFire" which may let you do what you are talking about with FM Server 9 but you'll need to figure out the programming.

I think that simplest and probably least expensive option in terms of both time and money (your time presumably being worth money)  to do at this point is to consult with former developer and find out how they did it and why it may not be working.

I would again say I can't understand how the script could have been run automatically using server-side script scheduling using FileMaker Server 9. It is my understanding that that function simply wasn't supported by FMS 9. If they were using 9 and doing importing, then they must have been triggering the script another way.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
xiaoyunwuAuthor Commented:
Hi willmcn,
Thank you so much for all the help.
I eventually used scriptfire plugin as you mentioned in the link: It works great.
I did see "Run script daily.fp7" on the server that might have been what former developer used.
Thanks again!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.