Thank you for your post.
When FileMaker Pro opens a database file, a flag is set in the file to signify the file is open. When the file is closed, that flag is set back to closed. If FileMaker Pro crashes with a file open, then when FileMaker Pro tries to open that file again, it will see the file was not closed properly as the flag is set to open. FileMaker Pro will then notify the user the file was not closed properly and then perform consistency checks to make sure the file is usable. Once the file opens, you should be fine.
The underlining issue is FileMaker Server crashing. What are clients doing when FileMaker Server crashes? In the event log or access log, what are the last few entries? This may provide a clue.
What version of the OS: Server... ist it 2012R1 or 2012R2?
Is anybody else running FMS11 under 2012? We stick on 2008-version Server with FMS11
Just received another error message and had Filemaker abruptly close in the middle of entry. All of the previous entries appear to be deleted on screen. When the program restarts is goes through the consistency check again and states the program was not closed properly. This doesn't make sense as it was open and in use before it crashed. How could it throw this error regarding being closed properly?
Thank you for the screen shot.
Since the file was closed abruptly, it did not close properly and the flag (as mentioned in the previous post) in the file still shows it as open.
What do the event log and access log files show? System log? When you Recover the file, do any errors show?
Run a Recover on the last Backup. Does this show any errors?