Administrator’s Guide

Event log messages and troubleshooting C-3
Schedule
schedulename aborted; the destination
destination is not writable
The specified destination is locked or read-only. If the destination is a removable medium, you might need to
remove it, make it writable, and reinsert it.
Schedule schedulename aborted; no open databases to
operate on
The schedule specifies a directory in which FileMaker Server currently has no databases open. Therefore, the
scheduled task can’t proceed. Make sure that the schedule specifies the correct directory to operate on, and that
all databases have been opened correctly.
Schedule schedulename was unable to back up file filename ;
can’t replace item with that name on destination
When FileMaker Server backs up a file, it first checks if a file with the same name already exists on the
destination volume and attempts to rename the existing file. In this case, the existing file could not be renamed,
and therefore it could not be replaced with the new backup. Move the existing file to another location or give
it a name that doesn’t conflict with the file being backed up.
Schedule schedulename was unable to back up file filename ;
error writing to destination ( error number )
An unexpected operating system error occurred when FileMaker Server attempted to copy files to the
destination volume. Refer to the system error log or look up the specified error number in your operating
system documentation to determine the cause of the problem.
Schedule schedulename was unable to back up file filename ;
file on destination is locked
The named file already exists on the destination volume and is locked or read-only. For the backup to succeed,
you need to either move the locked/read-only file to a different folder or change the schedule definition to use
a different destination. The file could also be open by another application, in which case it must be closed
before it can be moved or renamed.
Schedule schedulename was unable to back up file filename ;
not enough free space on destination
The destination volume does not have enough free space to hold a copy of the specified file. Check the free
space on the destination or choose a different destination for the backup.
TCP/IP network initialization failed; an unexpected error
occurred ( error number )
FileMaker Server couldn’t initialize TCP/IP due to an unexpected operating system error. See the system event
log (Windows) or your operating system documentation for an explanation of the specified error. Check the
TCP/IP configuration and reconfigure or reinstall, if needed.
TCP/IP network initialization failed; the TCP/IP address is
already in use or an address could not be obtained
( error number )
The IP address selected for use by FileMaker Server is already in use or isn’t correctly configured. Verify the
IP address and TCP/IP configuration in the Networks (Windows) or TCP/IP (Mac OS) control panel. If
FileMaker Pro 5 is already running on the same computer and is set to use TCP/IP, FileMaker Server is
prevented from using the same IP address. You should run FileMaker Server on a dedicated computer.
TCP/IP network initialization failed; not enough memory There is insufficient memory to use TCP/IP. See “What you need” on page 2-1 (Windows) or page 3-1
(Mac OS) for RAM requirements.
TCP/IP network initialization failed; protocol is not installed
(
error number )
Windows: FileMaker Server can’t initialize TCP/IP, because the TCP/IP protocol is not installed or not
configured correctly in the Networks control panel. Check the network installation and setup procedures in the
Windows documentation and reinstall, if necessary.
IPX/SPX network initialization failed; an unexpected error
occurred ( error number )
Windows: FileMaker Server can’t initialize IPX/SPX. Check network settings and system error log.
Message Explanation