Verifying the integrity of databases
If you suspect a database is damaged, verify its integrity by performing a consistency check:
Before starting the verification process, FileMaker Server sends a notification message to the FileMaker clients informing users that FileMaker Server must close the selected databases. When the delay time elapses, FileMaker Server disconnects any remaining clients and closes the selected databases, verifies them, and then reopens the databases that were successfully verified. If a database fails the consistency check, you must use FileMaker Pro to recover the file. For information on recovering damaged files, see
FileMaker Pro Help.
FileMaker Server logs a message in
Event.log indicating the success or failure of the consistency check.
Note If you are a group administrator, your server administrator must configure your administrator group to allow you to verify the integrity of the databases in your group folder. For more information, contact your server administrator.
Related topics