Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Automatic startup of FileMaker Pro Server Apps
FileMaker Pro Server 5.5 on Mac OS X won't startup automatically when the machine boots. According to the documentation and FileMaker technical support, the only way to start the so-called "server" is to run the FileMaker Server Config app and click the "Start" button. Since this is totally lame and unacceptable, I devised a workaround.

Read the rest of this article for the how-to...


STEP BY STEP DIRECTIONS
  1. Logon as root.

  2. Edit /etc/hostconfig and add the following line somewhere in the file:
    FMPSERVER=-YES-
  3. In /Library/StartupItems, create a new directory named "FMPServer".

  4. In the new FMPServer directory create two files, one named "StartupParameters.plist" and the other named "FMPServer".

    Contents of StartupParameters.plist:
    {
    Description = "FileMaker Pro Server";
    Provides = ("FMPServer");
    Requires = ("Resolver");
    OrderPreference = "None";
    Messages =
    {
    start = "Starting FileMaker Pro Server";
    stop = "Stopping FileMaker Pro Server";
    };
    }
    Contents of FMPServer:
    #!/bin/sh

    . /etc/rc.common

    ##
    # Start up FileMaker Pro Server
    ##

    if [ "${FMPSERVER:=-NO-}" = "-YES-" ]; then

    ConsoleMessage "Starting FileMaker Pro Server"

    # If the FileMaker Server 5.5 folder is in a different location
    # from the one shown below, modify the path appropriately!

    cd "/Applications/FileMaker Server 5.5/FileMaker Server Config.app/Contents/Resources/"
    ./fmserverd start -c fmserver.conf

    fi
  5. Restart the server. FileMaker Pro Server should start automatically.
If you ever want to disable automatic startup, simply edit /etc/hostconfig and change "FMPSERVER=-YES-" to "FMPSERVER=-NO-".
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[21,104 views]  

Automatic startup of FileMaker Pro Server | 10 comments | Create New Account
Click here to return to the 'Automatic startup of FileMaker Pro Server' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Very nice
Authored by: eagle_eyes on Jan 03, '02 06:20:14PM

Now what I want to know is why couldn't filemaker server add that automatically. This hint makes a good product great!!



[ Reply to This | # ]
Addendum
Authored by: jgardner on Jan 22, '02 11:12:57AM
One item I forgot to mention, that has caused trouble for some folks...you must be sure that the /Library/StartupItems/FMPServer script is executable; otherwise the script won't run:

# chmod 755 /Library/StartupItems/FMPServer

[ Reply to This | # ]
Addendum II
Authored by: jgardner on Jan 22, '02 11:16:20AM
Make that:
# chmod 755 /Library/StartupItems/FMPServer/FMPServer
Sorry.

[ Reply to This | # ]
Answer by FileMaker Inc.
Authored by: osax on Jan 20, '03 03:11:18PM

The FileMaker KB now shows an article how to create such a startup item: http://filemaker.com/ti/107911.html

It is not very well written, as it doesn't allow the "stop" or "restart" parameter; also the console messages are the same for starting and stopping.

If you have used the previous hint, you may consider to change all names according to this article (its "provides" line to "FMP", hostconfig entry to "FMSERVER" instead of "FMPSERVER" and the directory name to "FileMakerServer") to be on the safe side (i.e. if FileMaker brings its own startup item in the next release).



[ Reply to This | # ]
Start FileMaker Server at Boot (not as root)
Authored by: mmcleary on May 05, '03 01:28:05AM

Although this works it does create a problem because FileMaker Server
now runs as root. The impact is that FileMaker Server Config runs as the
the logged on user and hence cannot control (i.e. Start and Start)
FileMaker Server.

It may look like FileMaker Server Config stops FileMaker Server, but
Process Viewer will reveal that its still running.

The solution is to start FileMaker Server at boot as the user which
normally logs on to the machine. To do this use the following;

sudo -u username ./fmserverd start -c fmserver.conf

where username is the account under which you want FileMaker Server
to run.



[ Reply to This | # ]
Automatic startup of FileMaker Pro Server
Authored by: osax on Jul 03, '03 12:22:42PM
This script tries to incorporate all of the tips above:
#!/bin/sh

. /etc/rc.common

##
# Start FileMaker Server
##

FMS_PATH="/Applications/FileMaker Server 5.5/FileMaker Server Config.app/Contents/Resources/"
FMS_USER="admin"

StartService ()
{
	if [ "${FMSERVER:=-NO-}" = "-YES-" ]; then
		ConsoleMessage "Starting FileMaker Server"
		sudo -u $FMS_USER "$FMS_PATH""fmserverd" start -c "$FMS_PATH""fmserver.conf"
	fi
}

StopService ()
{
	ConsoleMessage "Stopping FileMaker Server"
	sudo -u $FMS_USER "$FMS_PATH""fmserverd" pause
	sudo -u $FMS_USER "$FMS_PATH""fmserverd" close
	sudo -u $FMS_USER "$FMS_PATH""fmserverd" stop
}

RestartService ()
{
	StopService
	StartService
}

RunService "$1"


[ Reply to This | # ]
Automatic startup of FileMaker Pro Server
Authored by: bradrellinger on Jul 07, '04 02:16:42PM

i followed the directions on FileMakers site but changed two things:

1 - added sudo - u admin, to make it run as the admin instead of root

2 - pointed the directory to the Applications folder

Here is what the FileMakerServer file looks like:

#!/bin/sh
. /etc/rc.common
##
# Start FileMaker Server
##
FMS_PATH="/Applications/FileMaker Server 5.5/FileMaker Server Config.app/Conten$
if [ "${FMSERVER:=-NO-}" = "-YES-" ]; then
ConsoleMessage "Starting FileMaker Server"
sudo -u admin "$FMS_PATH""fmserverd" start -c "$FMS_PATH""fmserver.conf"
fi

this works great on Mac OS Server 10.3.4



[ Reply to This | # ]
Automatic startup of FileMaker Pro Server
Authored by: JeffTronics on Aug 31, '04 03:53:31PM

Hi,

I want to thank everyone who put this post together because it became a valuable source of information for me. I recently upgraded an OS 9 G4 to Jaguar 10.2.8, and was stunned to find that FileMaker Server 5.5 does not Auto-start the server. I was also amazed that FileMaker Inc created a Tech Info document (referenced in this thread), with misleading steps. Specifically, they begin their steps having you create the FileMakerServer directory in the /System/Library/StartupItems, while the two files that belong in that directory, FileMakerServer and StartupParameters.plist, are in /Library/StartupItems. This was greatly confusing to me when comparing the steps posted here and at FileMaker's site. It didn't take me long to compare the two before realizing their steps won't solve the issue unless they make a correction in their technote.

Realizing this problem has been around for sometime now, I don't hold much confidence FileMaker Inc will come out with a fix, but rather continue it's future development with later server versions that don't have this problem. The trouble is I'm a little strapped for cash right now to shell out a thousand bucks for a bug fix! I'm certain they can spend half that on development, testing, and post a fix.

Unfortunately for me, regardless of what I tried, the steps did not work for me. This made me crazy, but realized after trying them over and over for hours, I would have to advise the user of this machine to click the Start Server button after any restart. Fortunately that will be infrequent because the machine is rebooted once a month.

For those of you more interested, the problem I was having, was the startup script was saying the path to the config file was incorrect. However it was not. To keep things simple, I tried configuring the script to locate the FileMaker Server 5.5 folder at the root, and or in Applications. Sometimes I would get the Starting FileMaker Server at boot, but it was too unpredictable. After the reboot I would verify it was truly running by checking the Process viewer and using ‘top' in Terminal. It was not.

In addition to the resources I found here, there are other helpful places on the web that offer the same steps with a twist, that include using other utilities too. However I was able to find a couple of USENET posts that too had no success even though they went through these steps. One thing is clear, there's nothing specific about what operating system everyone is having success with. Again, this machine was updated to Jaguar, while it appears problems are not reported with 10.1 or Panther – go figure.

Here are the links outside this post:

4) http://www.afp548.com/forum/viewtopic.php?forum=29&showtopic=2228

5) http://www.afp548.com/articles/system/fmpserver.html

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=8ba4ce9c.0303081231.7370b05c%40posting.google.com&rnum=1&prev=/groups%3Fq%3DFileMaker%2520Server%25205.5%2520AutoStart%26num%3D100%26hl%3Den%26lr%3D%26ie%3DUTF-8%26safe%3Doff%26sa%3DN%26tab%3Dwg

Again, thank you all for this brilliant and outgoing solution. I value this is a community of users helping users. Too bad FileMaker couldn't have take the energy equal to this and posted a downloadable solution.

Best,

JeffTronics.



[ Reply to This | # ]
Automatic startup of FileMaker Pro Server
Authored by: jepler on Jan 04, '07 09:19:11AM

I am running a standard version of FMP (not server). Do the following parameters "fmserverd" start and "fmserver.conf" need to be changed in the FileMakerServer shell script?

---
Jim Epler
San Diego, CA
[link:]http://mytechmusings.blogspot.com



[ Reply to This | # ]
Automatic startup of FileMaker Pro Server
Authored by: Crackle on Feb 22, '10 04:29:03PM

mmm Problems with finding route to directory, changed it. This worked for me, also use Batchmod.app on files

FMPServer file
root RWX wheel R_X everyone R_X

StartupParameters.plist file
root RW_ wheel R__ everyone R__

#!/bin/sh

. /etc/rc.common

##
# Start up FileMaker Pro Server
##

if [ "${FMPSERVER:=-NO-}" = "-YES-" ]; then

ConsoleMessage "Starting FileMaker Pro Server"

# If the FileMaker Server 5.5 folder is in a different location
# from the one shown below, modify the path appropriately!
cd ..
cd ..
cd "Volumes/MacWorld HD/Applications/FileMaker Server 5.5/FileMaker Server Config.app/Contents/Resources/"
./fmserverd start -c fmserver.conf

fi



[ Reply to This | # ]