Administrator’s Guide (Mac OS)

Technical specifications and optimization A-9
Guests can’t see open FileMaker Pro Server
databases, but can see non-server databases
in Hosts dialog box (for MacIPX).
For Mac OS users without an Ethernet or an Apple Token Ring card, who are using the
built-in LocalTalk port, load and bind the MacIPX Gateway software on the MacIPX
server. The server’s MacIPX frame type, or that of certain guests, may be set incorrectly.
All FileMaker Pro hosts and guests (including the server) must be using the same frame
type to communicate with each other. To change the server’s frame type, open the
MacIPX control panel and double-click the selected IPX interface. If Always
Auto-Configure Frame Type is selected, deselect it. Select another frame type and close the
control panel. Restart the server and start FileMaker Pro Server. If users still can’t see
open database files, open the MacIPX control panel and select another frame type.
(Typical Ethernet frame types are 802.2 and 802.3.) A guest on a Mac OS computer can
follow this procedure when using MacIPX to communicate with FileMaker Pro Server.
To change the frame type used by a FileMaker Pro for Windows guest, you must
change the configuration of the IPX/SPX compatible protocol in the Network Control
Panel. See your Windows documentation for more details.
Guests can’t see open FileMaker Pro Server
databases, but can see non-server databases
in Hosts dialog box (for TCP/IP).
There may be a problem with Local Hosts. Respecify the host IP address/name, or
contact your network administrator for help configuring the IP addresses on host/guest.
Receive “Application is busy or missing”
message when double-clicking a
FileMaker Pro file to be hosted by
FileMaker Pro Server.
FileMaker Pro files can’t be opened in FileMaker Pro Server by double-clicking. You
must open the files from within FileMaker Pro Server, or drop the files onto the
FileMaker Pro Server icon in the Finder. See “Starting the application and opening
files” on page 2-1 for complete instructions.
Receive “Communication with the host was
interrupted and could not be re-established”
message on guest computer.
The guest has been disconnected from a database by FileMaker Pro Server because the
guest didn’t comply with a request from FileMaker Pro Server to close a database. (See
“Closing a database file” on page 2-9). Another reason is communication between the
host and guest may have been disrupted due to a hardware failure (lost network
connection) or a software connection time-out (no response from guest for a given
period of time). The latter could be caused by a screen saver, debugger, or
processor-intensive operation, or by leaving a menu pulled down (in Windows).
Receive “File could not be opened: database
may be damaged; try opening in non-Server
version of FileMaker Pro” message when
trying to open a file in FileMaker Pro Server
(or in log file).
The file may be damaged and needs to be opened in FileMaker Pro. Start the
FileMaker Pro application, open the file, and follow any instructions on your screen.
(See appendix A of FileMaker Pro User’s Guide for more information on recovering
files.) Then try opening the file with FileMaker Pro Server again.
Receive “File could not be opened: must be
set to Multi-User in FileMaker Pro”
message when trying to open a file in
FileMaker Pro Server (or in log file).
FileMaker Pro Server can’t open files set to
Single-User. Open the file in the
FileMaker Pro application and choose Single-User from the File menu to switch the file
to multiuser status. Note that you must use AppleTalk or MacIPX with FileMaker Pro
on the same computer, because Open Transport doesn’t allow two applications to use
TCP/IP at the same time.
Receive “Host capacity exceeded” message
on guest computer.
You reached the maximum allowable connections or guests on FileMaker Pro Server.
Increase the number of guests allowed in the Preferences dialog box (see “Customizing
FileMaker Pro Server” on page 2-12), or disconnect AppleShare users (see
“Coexistence with AppleShare software” on page A-2).
Unable to administer FileMaker Pro Server
remotely using FileMaker Pro.
Check that Remote administration is enabled in the Preferences dialog box. See
“Specifying a password for remote administration” on page 2-14 for more information.
Unable to install FileMaker Pro Server. Check hardware and software requirements listed in “What you need” on page 1-1 to
ensure your equipment and software are compatible.
Unable to start FileMaker Pro Server. Check hardware and software requirements listed in “What you need” on page 1-1 to
ensure your equipment and software are compatible. Also check the FileMaker Pro
Server Log for a description of why FileMaker Pro Server couldn’t start. (See
“Examining the log file” on page 2-4 and “FileMaker Pro Server log file” on page A-5
for more information.)
Symptom Suggested solution or explanation