Hi All, First apologies if this is redundant, but I thought I would "cast this net" before doing Testing or Google investigation of what is already out there.
Second, the client uses Windows; period. No options there so please don't recommend using a Mac. Third, I am in the process of documenting a list of script steps that Are and Are Not Web Compatible (it's in the documentation but not in an easy to check list) -- thus I cannot leave these scripts to the new ability of FMServer9 to run Scripts on a Schedule. Since it has happened for two different clients I cannot believe it is unheard of. When I open FM9 (normal or advance) and the quit. Sometimes it quits fully, and sometimes the .exe "hangs" in the TaskManager Process list and prevents opening FileMaker9 again until I end that process. That is an annoyance for the end user and a bigger annoyance for our HelpDesk people But it is a MissionCritical Error when it is the "Overnight" box that I have set up to use Scheduled Tasks to open a series of FMChronJob utility files I built that open and run a script-> that calls a particular overnight script and then the last step is Exit Application in the calling utility script. I have these running at 2am, 3:30am and 5:00am. However, when the first one runs and the next two DON'T because first Exit Application left the .exe Process hanging in TaskManager. Assuming that I will still have non-Web compatible steps in some of these scripts (and thus can't let the server run them) I would like a solution to this. I guess I could piggy back all three scripts into one, but then I would *still* have to clear the hanging Process every day, better but still not as automated as one would like. Okay, so I have just discovered that unlike with FM6 (or 5 or 4 or whatever when I created the utility), for FM9 ScheduledTasks will open a specific targeted file and run it's opening script EVEN IF FileMaker is running. (Of course, the file itself must be closed, but anything else can be open.) I have changed the ChronJob.fp7 files to Close instead of Exit Application and I think we are okay -- just leave FileMaker open on the Overnight box. (Probably be more meticulous about closing Called Script files now too...) Any other better options?... Any solution to the stupid Hanging Process thing?... Thanks in advance for any gems... -- Sincerely, Brad
