Fixing Server 9 Crashes on Windows XP/2003
From FMWebschool Reference
This section contains a number of useful hints that stabilize FileMaker Server 9 performance on Windows XP and Windows Server 2003 operating systems. The steps outlined below are experimental and have been found to help stability within FMWebschool servers - however performing any of these changes is done at your own risk with absolutely no implied warranty or support from FMWebshool Inc. We encourage you to discuss these suggestions and seek support at our FileMaker Server 9 Forums.
Removing Indexing from Installation Folders
So far this seems to have made the most significant difference within our servers: the Windows Indexing Service seems to cause fmserver.exe to crash (more specifically segfault) during its scans of this folder and the databases contained within it.
One possible explanation of this is the method with which FileMaker obtains and implements locks on its open database files. Accessing those files and reading certain areas of them might interfere with certain processes such as caching, flushing to disk, or simple disturbing the actual file pointer that FileMaker Server keeps in memory.
The solution to this problem is to either shut down the indexing service, or simply exclude the whole FileMaker installation from being indexed. The latter option is explained below.
- Open Windows Explorer
- Browse to C:\Program Files\FileMaker\ (or your installation location)
- Right click on the whole FileMaker directory, select Properties
- On the first "General" tab, click "Advanced..."
- Within the Advanced dialog, remove the "For fast searching, allow Indexing Service to index this folder" (see screenshot on the right for the location of this checkbox)
- When asked to apply changes to this folder only or subfolders and files, choose "Apply changes to this folder, subfolders, and files"
That is it, now your FileMaker Server will hopefully be much more stable while operating within the Windows environment.
It has been reported by some users that antivirus services can interfere with FileMaker Server. Most anti-virus services have settings to disable scanning certain folders which should be use to exclude the FileMaker Server folder.
Just like the indexing service interference, anti-virus software attempts to monitor and read any changes made on the hard drive which can interfere with the internal mechanics of FileMaker server caching and interaction with open database files.
Disable scanning of the whole FileMaker installation directory using your anti-virus configuration dialogs.