I set up a Windows batch file that simply opens a non-hosted FileMaker file. When the FM file is run, it performs some tasks, then exits.

When I run the batch file as is, it works just fine.

I setup a FMS schedule to run said batch file. I set it up to run under a Windows Admin account that I know is good (I manually ran the file using the same account). Each time the schedule fires, it aborts with a status of 'System script error'. Looking in the log viewer, I see an error of 692 - 'returned non-zero status -1"

Now I can understand this being a problem if the schedule was run under the Local System user or other non-priv user. But this is set up as a user with Admin level privileges to this machine.

Did I miss something? :

What's this non-hosted file supposed to be doing? Why would you schedule it with the FMS scheduler?

The obvious difference would be that you're trying to run a UI operation with nobody logged in. If you ran it manually it would work just fine because it would be possible to draw an UI in your user space.

It's running a time-range report, creating a PDF, and then emailing it to specific people.

The PDF creation part of this is the reason why I'm not using FMS script schedules.

What error (if any) do you get when you schedule the same batch file but with the Windows Task Scheduler?

Also are you trying to run this with nobody logged on (in the OS)?

I figured out what was going on. I'm able to run the same process successfully using the Windows Task Scheduler. BUT I had to run it under Server 2003 mode, so it'll use session zero.