Help
Table Of Contents
- FileMaker Server 9 Help
- About FileMaker Server
- New features in FileMaker Server 9
- Deploying FileMaker Server
- Starting Admin Console
- Hosting databases
- Hosting websites
- Starting and stopping FileMaker Server
- Configuring general settings
- Configuring Database Server settings
- Configuring web publishing settings
- Administering clients
- Administering databases
- Using ODBC and JDBC with FileMaker Server
- Monitoring FileMaker Server
- Managing plug-ins
- Securing your data
- Scheduling administrative tasks
- Troubleshooting
- Checking for updates
- About the license key
- Command line reference
- Glossary
- Registration
- Customer support and Knowledge Base
- Copyright information
Troubleshooting FileMaker Server event log messages
F
ILEMAKER SERVER 9 HELP 164
FileMaker Server event log messages
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. Variables returned by FileMaker Server or the
operating system, such as the name of the destination or file, are in [brackets].
Client [client name] no longer responding; connection closed. ([error
number])
A connected client's computer has stopped communicating with FileMaker Server due to a
network disruption or a software error.
Closing database [filename] due to serious error. ([error number])
The specified file is being closed by FileMaker Server due to an error condition. The file may
need to be recovered in an earlier version of FileMaker Pro. See FileMaker Pro Help for
information about recovering damaged files.
Database cache size: [x] MB.
The specified amount (x) of memory is usable for the database cache. This message is logged
when FileMaker Server starts. You can adjust application memory by changing the RAM
reserved for database cache in the Database Server > Databases tab. The new cache size
takes effect immediately.
Database [filename] consistency check skipped by administrator, database
opened. Use of this database could result in data corruption.
Administrator omitted the file consistency check via the Open a database action in the
Databases pane. See Opening hosted files
(page 96).
Database [filename] could not be opened. Database may be damaged; use
the Recover command in FileMaker Pro 9.
The specified file failed the consistency check. 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] could not be opened in its current state: open it in
FileMaker Pro first.
The database might be in an older format (databases need to be in FileMaker Pro 7 (.fp7)
format before you can host them using FileMaker Server 9). For information about converting
files, see FileMaker Pro Help.
Database [filename] is being opened for the first time in FileMaker 9,
performing consistency check.
Since the specified file was created in FileMaker Pro 7 and has not been previously opened in a
FileMaker 8 or later product, FileMaker Server performs a file consistency check.