Help

Troubleshooting FileMaker Server event log messages
F
ILEMAKER SERVER 9 HELP 165
Database [filename] is damaged and has been closed.
Try opening the file in FileMaker Pro: start the FileMaker Pro application, open the file, and
follow any instructions on your screen. (See FileMaker Pro Help for more information about
recovering files.) Then try opening the file with FileMaker Server.
Database [filename] was not closed properly, performing consistency check.
The specified file was in use when FileMaker Pro or FileMaker Server shut down abnormally;
therefore, FileMaker Server performs a file consistency check to examine the file’s blocks.
FileMaker Server is going to sleep. The entire cache will be flushed. All
schedules will be suspended.
If the server computer is configured to sleep during periods of inactivity, before doing so the
operating system prompts each open service
or application to find out if the service or
application can accommodate energy-saving mode. If any clients are currently connected to a
hosted database, FileMaker Server denies the sleep request and the server computer does not
sleep. If no clients are connected, FileMaker Server writes any unsaved changes to disk
(flushes the cache) and allows the server computer to sleep. During sleep, all scheduled tasks
are suspended and do not run again until the next scheduled time when the server computer is
awake.
FileMaker Server is now awake. All schedules will now be resumed.
This message is sent to the log by FileMaker Server when the server computer wakes up from
sleep mode. During sleep, all scheduled tasks are suspended and do not run until the next
scheduled time when the server computer is awake.
FileMaker Server quitting! An unrecoverable error occurred. ([error number])
FileMaker Server detects a severe error during network use, due to a network failure or other
causes. Check network installation, settings, and the system error log.
Registration with directory service failed. ([error number])
Registration with the directory service failed because the error number reported is an LDAP
error from the LDAP server.
Schedule [schedule name] aborted; [destination] could not be found.
The specified destination could not be found. If the destination is a removable medium, make
sure it is inserted in its drive. If the destination is an external or network drive, connect the drive
or network. Try again after the destination volume drive is correctly set up.
Schedule [schedule name] aborted; no open databases to operate on.
The schedule specifies a folder in which FileMaker Server currently has no databases open.
Therefore, the scheduled task can't proceed. Make sure that the schedule specifies the correct
folder to operate on and that all databases have been opened correctly.