What do we not understand about interaction between FileMaker Pro 13 Advanced and Windows Server 2008 R2?
The problem to solve: At unpredictable intervals (perhaps averaging 3-5 days), the FileMaker Pro client crashes. (We need it to run a script every 9 minutes or so (different from the one below); maybe the crash is due to a memory leak or something similar.)
The solution we're pursuing: Via Task Scheduler, check each 15 minutes whether FileMaker has crashed. If it has, start it.
We wrote a batch file that queries Windows’ tasklist.exe whether FileMaker is running and restarts it via a call to FileMaker Pro 13 with a parameter pointing to a “.fmp12” file that's a shortcut to a particular FileMaker database. If we call the batch file manually from the command prompt, the batch file works well. (If FileMaker isn’t running, the batch file starts both a FileMaker process and an application window; if FileMaker is running, the batch file takes no action.)
When we call the same batch file from the Task Scheduler, the batch file starts the FileMaker 13 process, but does not start the FileMaker application window. (We can see the process we want listed in the Task Manager; we have no application window on the screen.)
What can we do (whether in the batch file or elsewhere) to reliably start both a FileMaker 13 process and application window from calls made by the Task Scheduler? For that matter, any suggestions as to why FileMaker crashes?
Related background. Read, skim, or skip at will.:
Here's the batch file.
@echo off setlocal ENABLEEXTENSIONS set target=FileMaker Pro Advanced.exe set startWith1=C:\Program Files (x86)\<fully qualified path>\FileMaker Pro Advanced.exe set startWith2=C:\Users\Administrator\Desktop\Splunkopener.fmp12 tasklist /fi "IMAGENAME eq %target%" /fi "USERNAME eq administrator" /fo csv 2>NUL | find /I "%target%" 2>NUL if "%ERRORLEVEL%"=="1" goto StartFileMaker if "%ERRORLEVEL%"=="0" goto EOF :StartFileMaker call "%startWith1%" "%startWith2%" :EOF exit
We filter for "administrator" because this computer routinely lists three tasks in Task Manager for "FileMaker Pro Advanced.exe". Only one is for "administrator" and it turns out to be the one we need to have running.
Thanks in advance ...