(We can see the process we want listed in the Task Manager we have no application window on the screen.) 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. (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.) If we call the batch file manually from the command prompt, the batch file works well. 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. The solution we're pursuing: Via Task Scheduler, check each 15 minutes whether FileMaker has crashed. (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 problem to solve: At unpredictable intervals (perhaps averaging 3-5 days), the FileMaker Pro client crashes. Add the high-level features of FileMaker Pro Advanced and FileMaker Pro Server.What do we not understand about interaction between FileMaker Pro 13 Advanced and Windows Server 2008 R2?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |