AnsweredAssumed Answered

Filemaker dBs freeze on only some workstations (not all)

Question asked by Visor on Oct 9, 2009
Latest reply on Nov 4, 2009 by AHunter3_1


Filemaker dBs freeze on only some workstations (not all)

Description of the issue

FileMaker Product(s) involved:Filemaker 8.5v2 Operating System(s) involved:File Server: Windows 2003 Server Standard Edition SP2Workstations: Windows XP SP2 & SP3 Detailed description of the issue:For certain Filemaker databases (appears to be random) that reside on one of our servers, some client PCs are able to open them without issue, while other PCs get stuck on a blank grey screen within Filemaker.  Sometimes the database will finally open after ~10 minutes, other times the database won't open at all (we usually give up after 30 mins).      Exact steps to reproduce the issue:1.  Browse to Filemaker database on server (via either inside Filemaker, in Windows Explorer, or just a desktop shortcut to the shared folder).2.  Open the Filemaker database (by clicking ‘open’ in Filemaker, or double-clicking on the filename in Windows Explorer / Share).3.  If double-clicking on file outside of Filemaker, then the Filemaker app loads, (splash screen appears briefly). 4.  Filemaker goes to a grey screen with no File menu at top (just the icon menu below it).5.  After ~10 minutes (best case), the login screen will appear for the user to provide a password.5a. If database doesn’t open (we usually give up after about half an hour), Filemaker cannot be killed in Task Manager so a reboot is required.6.  Once user provides password and the database opens, performance is normal, although sometimes running a query/report causes another freeze.Any additional configuration information/troubleshooting that is relevant to the issue:1.  Databases open quickly & with no issues when accessing directly from the server, and on certain PCs (random).2.  All workstations involved are well over the minimum system recommendations for running Filemaker.     (ranges from P4 @ 2.8 GHz to Core2Duo @ 2.6 GHz, and from 512MB - 2GB RAM).    3.  Server is a Virtual Machine (VMWare) that has been provided with an AMD Operton @ 2.2 GHz (single-core) w/ 1 GB RAM (typical CPU usage is < 5%; typical RAM usage is only ~350 MB).  4.  VM farm is located in a building separate from user sites.  Always accessed via WAN.  5.  All workstations belong to the same domain, and can view the server via Windows Explorer, pings, etc. without issue.  6.  Filemaker Server Admin program is not installed on this server.  Users are simply accessing their databases through a share that was created for them on the server.  Any workarounds that you have found:1.  “Recover” option sometimes works, but not always.  2.  Making a copy of the Filemaker file to the local PC usually alleviates the problem (but defeats the purpose of hosting it on a file server).    Feel free to ask me more questions about the system setup. Thanks, RyanCalgary, Canada