Guide to Updating Plug-ins
Table Of Contents
- Preface Using the FileMakerServer documentation
- Chapter 1 Welcome to FileMakerServer 5.5
- Chapter 2 Installing FileMakerServer in Windows
- Chapter 3 Installing FileMakerServer in MacOS 8.6 to 9.1
- Chapter 4 Installing FileMakerServer in MacOS X
- Chapter 5 Installing FileMaker Server in Red Hat Linux
- Chapter 6 Configuring FileMakerServer (Windows and Mac OS)
- Using the configuration assistants (Windows)
- Opening the Properties dialog box (Windows)
- Opening the Preferences dialog box (MacOS 8.6 to 9.1)
- Opening the Preferences dialog (MacOSX)
- Setting the number of guests
- Allowing disconnection of idle guests
- Authenticating guest log on (Windows)
- Setting the maximum number of files
- Changing the amount of memory used by FileMakerServer
- Adjusting memory (MacOS 8.6 to 9.1)
- Setting how often the cache is flushed
- Allowing single user files to be hosted
- Allowing software updates to be downloaded automatically
- Opening runtime solutions automatically (Windows and MacOS X)
- Opening runtime solutions automatically (MacOS 8.6 to 9.1)
- Enabling remote administration
- Specifying a custom host name
- Maximizing performance (MacOS 8.6 to 9.1)
- Choosing network protocols
- Setting the preferred IP address
- Recording usage statistics and settingsizelimits
- Setting a size limit for the Application Log (WindowsNT)
- Setting a size limit for the Application Log (Windows2000)
- Setting a size limit for the event log (MacOS)
- Using FileMaker Server with a directoryservice
- Restoring FileMaker Server defaultsettings
- Protecting files with a password
- How FileMakerServer behaves during system sleep (Windows 2000 and Mac OS)
- Chapter 7 Administering FileMakerServer (Windows and Mac OS)
- Starting FileMakerServer (WindowsNT)
- Starting FileMaker Server (Windows 2000)
- Stopping FileMakerServer (WindowsNT)
- Stopping FileMakerServer (Windows2000)
- Starting FileMakerServer (MacOS8.6to9.1)
- Quitting FileMakerServer (MacOS8.6to9.1)
- Starting FileMakerServer (MacOS X)
- Quitting FileMakerServer (Mac OS X)
- Using remote administration
- Automatically downloading the Server Administration plug-in to a remote computer
- Opening the Remote Administration window
- Listing hosted files and current guests
- Viewing usage statistics for FileMakerServer
- Hosting FileMakerPro5.x files
- Closing hosted files
- Disconnecting guests
- Viewing detailed information about hosted files andguests
- Sending messages to guests
- Sending messages to all guests
- Determining if you have exclusive access to hosteddatabases
- Using local administration (Mac OS 8.6 to 9.1 )
- Opening the local administration window (MacOS 8.6 to 9.1)
- Listing hosted files and guests (MacOS 8.6 to 9.1)
- Viewing usage statistics (MacOS 8.6 to 9.1)
- Hosting FileMaker Pro 5.x files (MacOS 8.6 to 9.1)
- Closing hosted files (MacOS 8.6 to 9.1)
- Disconnecting guests (MacOS 8.6 to 9.1)
- Sending messages to guests (MacOS 8.6 to 9.1)
- Monitoring server performance (Windows)
- Using reported events to track activities
- Recalculating the Today function inhosteddatabases
- Chapter 8 Scheduling administrative tasks (Windows and Mac OS)
- Scheduling tasks to run automatically (Windows)
- Scheduling tasks to run automatically (MacOS 8.6 to 9.1)
- Scheduling tasks to run automatically (Mac OS X)
- Viewing scheduled tasks in the Schedules list (Windows)
- Viewing scheduled tasks in the Schedules window (MacOS)
- Running scheduled tasks manually
- Changing scheduled tasks
- Duplicating scheduled tasks
- Deleting scheduled tasks
- Enabling and disabling scheduled tasks
- Using the command line to automate tasks (Windows)
- Using a script to automate tasks (MacOS)
- Making sure you don’t run out of disk space during backups
- Chapter 9 Using FileMaker Server in Red Hat Linux
- Getting onscreen help with command and preference syntax
- Administering FileMaker Server
- Starting and stopping FileMaker Server automatically
- Configuring FileMaker Server
- Editing the configuration file
- Applying configuration changes
- Setting the number of guests
- Disconnecting idle guests
- Setting the maximum number of files
- Changing the amount of memory used by FileMaker Server
- Setting how often the cache is flushed
- Allowing single user files to be hosted
- Allowing software updates to be downloaded automatically
- Specifying the location of hosted files
- Specifying a user account name and group name for FileMaker Server
- Enabling remote administration in FileMaker Server
- Using the fmspasswd utility to encryptpasswords
- Specifying a custom host name
- Specifying the preferred IP address
- Opening runtime solutions automatically
- Using reported events and statistics to track activities
- Using FileMaker Server with a directoryservice
- Chapter 10 Manually installing the Server Administration pluginonaremote computer
- About the Server Administration plug-in
- Manually installing the plug-in on a remotecomputer (WindowsNT and Windows2000)
- Manually installing the plug-in on a remote computer (Windows95 or Windows 98)
- Enabling the Server Administration plug-in using FileMakerPro (Windows)
- Manually installing the Server Administration plug-in on a remote computer (MacOS)
- Enabling the Server Administration plug-in using FileMaker Pro (MacOS)
- Appendix A Technical specifications and optimization
- Appendix B Performance and usage tips
- Appendix C Event log messages and troubleshooting
- Appendix D About the TechInfo database
- Index
Event log messages and troubleshooting C-3
Schedule schedulename 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 volume is an external or network drive, connect the drive or network. Try again
after the destination is correctly set up.
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 control panel (Windows) or TCP/IP control panel (Mac
OS 8.6 to 9.1) or TCP/IP preferences (Mac OS X). If FileMaker Pro 5.x 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), page 3-1 (Mac OS
8.6 to 9.1), page 4-1 (Mac OS X), or page 5-1 (Red Hat Linux) 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.
Message Explanation