I'm trying to create a file with FileMaker Server Scheduler. If I run the script, it works just fine. If I schedule the script to run, I get a "scripting error 800" (Unable to create file on disk).

I'm thinking it is some kind of a permissions issue, but I can't seem to figure out what account FMServer 11 is using to try to create the file.

I'm thinking it is some kind of a permissions issue, but I can't seem to figure out what account FMServer 11 is using to try to create the file.

Local System. And that may not have write privileges to the directory where you're sending the file. You can use the "Run As" option to specify another Account.

Steven

I'm trying to create a file with FileMaker Server Scheduler

If you are using a FM script and the "new file" script step then it won't work. It's not supported server-side. You can tell by switching to "server" in the dropdown on the lower left corner of the script editor.

Local System. And that may not have write privileges to the directory where you're sending the file. You can use the "Run As" option to specify another Account.

Steven

I thought it was "local system" but my sysadmin doesn't see that account to grant it additional privileges.

By "run as" do you mean "when running the task, use the following user account"? Because I do have that one set to use my admin account but to no avail.

The task exports to a file, it doesn't use the "new file" script step. It also used to work on our old 2003 server.

A-ha! I got the answer on the FileMaker Today forum.

I could never get FileMaker scheduler to work on the old server either. So, I did a workaround where I'd have Windows Scheduler open a small FM file that would run the script. It used to work just fine. As I said, on the new server neither way would work.

I did not know that scripts running from the FMS scheduler can only create files in the Documents folder until a user on the other forum mentioned it.

So, I changed the script to export to filewin:/C:/Program Files (x86)/FileMaker/FileMaker Server/Data/Documents/filename and it worked like a champ.

Because I do have that one set to use my admin account but to no avail.

That's a FileMaker Pro database account, no doubt? You need an OS level Account.

Please also see this article on the main page of FM Forums.

Steven

Thank you for the post, but no, it is not a FMP database account I was referring to. I was referring to the account I log into the Server with, which is an admin account.

It does turn out that my problems aren't all solved. I had two processes I needed to schedule. One is a simple export, which exporting to the Documents folder solved. But, the second one creates a PDF, appends two other reports to it, then emails it out. I still can't get that one to work since creating PDFs isn't supported by Server scripting. So, I need to find a way to get Windows Scheduler to open the starter file that I used on the old server to run the script I need.

So, I need to find a way to get Windows Scheduler to open the starter file that I used on the old server to run the script I need.

You might not want to do that on the server, since it's running with no user logged in. Using the Windows Task Scheduler to run FileMaker Pro in that state can have some very nasty effects (leave your box unstable).

A better way is to use a robot machine and use FileMaker's ActiveX interface in a VBscript to run whatever scripts you need to. The robot machine would be a client of the FMS machine, using the hosted file.