I know this will sound contrary but try running Filemaker on OSX instead of OSX Server. I have had better luck that way.
Otherwise I can't help and you may need advice from elsewhere.
I think there is a bug logged for OSX Server and FM13 and an update is in the pipeline. If anyone is good at searching the FM bug list could you please post here?
Known bug list: http://forums.filemaker.com/posts/ad61a7e781?page=1
Do you have any server side plugins installed? Even if you aren’t using them they can cause crashes. Remove them, don’t just disable them.
Have you kept Java up to date? Should be at 7v51.
Have you checked the drive and permissions? Disk Util should always be used to repair permissions after doing any installations. Installers are notorious for changing permissions so they can finish doing the install but not changing things back to where there were.
Drive and or RAM issues can also cause problems. Have you done a hardware check? Apple Hardware checker or TechTool Pro7 or similar would be a good idea.
I don’t know the history of this systems upgrades and installs so I’d suggest a complete system install on a clean hard drive and install only FMS.
Turn off any Virus testing of the FMS folders. Most especially the data folder.
Turn off Spotlight indexing of the Data folder.
Had a similar issue with FMS 13 on a windows 2008 R2 server. Impossible to disconnect clients, impossible to close databases... some clients appeared 3-4 times in the list... Had to restart the server. I just hope it won't happen to often...
The same for me on windows Server 2008 R2 64bit. This happen with regularity every weeks.
Just happened to me again this morning... I'm just wondering if I should go back to 12 until we know more about this....
I think we will go back to 12 until there is an update addressing this problem. We never had a crash in 12. It is also my understanding, although perhaps not well known, that we can still develop in 13, with popovers, animation, etc., which can be accessed in 13, even on a 12 server.
This also happens on a regular basis for on of our clients. Windows Server 2008 R2 64bit. Have you found a solution?
You should open a support ticket with FMI and have them look at the deployment. I doubt that there is a silver bullet.
If you were running FMS12 on the exact same machine without issues and the load and the files have not changed since then, I would suggest removing FMS13 and going back to 12.
In the meantime:
- any DMP files in the FMS logs folder, with creation times that correspond to the crashes?
- what does the windows system and application event log report around the time of the crashes
- what does the FMS stats log say around those times: is FMS reporting high numbers in any of the 4 bottlenecks (disk i/o, network, memory, processing)