Error during progressive backup of a newer copy will be used or made. If the Database Server can free up enough space to make a new backup by deleting old backups, it logs this message. ![]() The Database Server detected that there is not enough free disk space to make a complete copy of the databases that are part of the backup. Deleting backup folder(s) to free KB of disk space needed for new backup. The specified maximum backups to keep was exceeded and the Database Server deleted the oldest backup folder. If the free space gets too low, FileMaker Server reports an error and does not allow changes to the databases. Use your operating system tools to increase the free space on the disk so the database files can expand. FileMaker Server attempted to increase space by deleting temporary files. The disk containing the hosted database or the temporary files is getting low on free space. Database or temporary file low disk space, only KB free! Searched temporary files and freed KB. 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. Database was not closed properly, performing consistency check. (See Claris Pro and FileMaker Pro Help for information about recovering files.) Then try opening the file with FileMaker Server. Try opening the file in FileMaker Pro: start the FileMaker Pro application, then open the file and follow any onscreen instructions. The database or its associated temporary file is damaged. Database or temporary file is damaged and has been closed. Convert the database file to FMP12 or CLARIS format. Databases need to be in FileMaker Pro 12 (FMP12) format for FileMaker Server or Claris Pro (CLARIS) format for Claris Pro before you can host them using the current version of the host. The database might be in an older format. Database could not be opened in its current state: open it in FileMaker Pro first. The specified file failed the consistency check. Database may be damaged use the Recover command in FileMaker Pro. The file may need to be recovered in an earlier version of FileMaker Pro. ![]() The specified file is being closed by FileMaker Server because of an error condition. ()Ī connected client's computer has stopped communicating with FileMaker Server because of a network disruption or a software error. Client no longer responding connection closed. must enter a unique license key in FileMaker Pro. Two clients cannot use the same license key. Client denied access because the license key is already in use by client. To fix this problem, start Bonjour from the Services control panel before starting FileMaker Server. ![]() However, users can still connect to FileMaker Server by specifying an IP address or host name. The result is that FileMaker Server does not appear in the local hosts list in the Hosts dialog box for FileMaker Pro clients, or in the Launch Center of FileMaker Go clients. The Bonjour service is not installed or not running when FileMaker Server starts. FileMaker Server will not be visible to FileMaker clients. Bonjour service is either not installed or not running. ![]() Note In macOS, FileMaker Server Helper writes events to the Event.log. Variables returned by FileMaker Server or the operating system, such as the name of the destination or file, are in square brackets ( ). The following is an alphabetical list and explanation of some of the log file messages you might see in the Event.log or in the Windows Event Viewer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |