Server Management
FileMaker Server 9インストールの注意点4 03/08/2008 03:55:39

ファイルメーカー サーバーv.9のインストールは、v.8以前のものに比べて格段に複雑な構造になっている。まっさらなOSへのインストールならまだ良いようだが、アップグレード時にさまざまな問題で正しく完了できないケースが多いようだ。先日は、v.8からのアップデートの際に失敗し、写真上のような「Deployment/Configuration error -150 WPE(wpe1)コンポーネントの開始に失敗しました。エラーコード = 2504」というメッセージが出てしまった。


-ライブラリ/FileMaker Serverフォルダ内のファイルメーカーデータファイルとXMLテンプレートファイル以外を手作業で削除する。Windowsでは、ファイルが開いていて削除できない場合があるので、その際はPCを再起動してから行う。
(# The following line was added by FileMaker Server Web Publishing Engine in order to add の下の、Include '/Library/FileMaker Server/Web Publishing/web-configuration/WEB-INF/conf/mod_jk.conf' の行)
-MacOSXの場合、アプリケーション/ユーティリティ/Java/J2SE 5.0/Java環境設定 を起動し、インターネット一時ファイルを削除する。(写真下の右下にある「ファイルの削除」ボタンをクリック)

その他の点について、詳細下記および当サイトFileMaker Server 9インストールの注意点を参照されたい。

FileMaker Server 9, FileMaker Server 9 Advanced

Please reference the FileMaker Server 9 Getting Started Guide for assistance in installing FileMaker Server 9 and FileMaker Server 9 Advanced. If you run into any issues with the installation or configuration please refer to the information listed below for additional assistance:

Before Installing FileMaker Server 9 or FileMaker Server 9 Advanced

Read Chapter 1 of the FileMaker Server 9 Getting Started Guide.
Remove FileMaker Server 8 or FileMaker Server 8 Advanced using the 8.0 uninstaller.
Open the FileMaker Server install folder and make sure no other folders remain except Data (which has your databases) and xslt-template-files. If any folders like Admin/Conf or web-server-support remain, clean them manually before you begin the installation. The Windows operating system might prevent you from deleting files, when some processes are using it or if the files are open. If this happens, reboot your machine and then delete the files.

Reboot before next installation: Also, as a rule of thumb you should reboot the machine after an uninstall and before the next installation.

FileMaker Pro: Make sure FileMaker Pro is not running when you install FileMaker Server 9, there are port conflict issues. If you installed FileMaker Server 9 while FileMaker Pro was running it is necessary to uninstall FileMaker Server 9 and reboot your computer before reinstalling.

Check IIS and Apache for any left over configurations:

On IIS, Open Default web site and make sure fmi-test and Jakarta are removed.
On Windows Server 2003, check under Web Service Extensions and make sure PHP and FMI Web Publishing are removed.
Right click on Default Web Sites > properties
Go to Documents tab and make sure index.php is removed.
Go to Home Directory tab and click on configurations. In the mappings tab, Applications Extensions, make sure PHP is removed.
Go to Directory Security tab, click on Authentication and access control and make sure Integrated Windows authentication check box is not checked.
Right click on Web Sites > properties
Go to ISAPI filter tab and make sure PHP and FMI Web Publishing are removed.
Restore Apache: On Apache, after an uninstall, make sure web server is running. If not, try to restart it by issuing the command on a terminal sudo apachectl restart. If Web Server fails to start due to any issues you can revert to the default configuration of Apache by doing the following. Please note that if you have special web configurations, you will loose them by doing so.
Open a terminal, and stop Apache by issuing the command
sudo apachectl stop
To back up httpd.conf, go to /etc/httpd
cd /etc/httpd
Issue the command to back up httpd.conf file
sudo cp httpd.conf httpd.conf.bak
Copy over default configuration file by issuing the command:
sudo cp httpd.conf.default httpd.conf
Start apache by issuing the following command
sudo apachectl start
Clear Java Cache if you had a previous FileMaker Server 9 installation:

On Mac OS X, Applications > Utilities > Java > J2SE 5.0 > Java Cache Viewer > Preferences, click on Delete Files. Open the browser and empty cache.

On Windows, Start menu > Control panel > Java- General tab-on Temporary Internet Files > click on settings and click on Delete Files. Also clear browser cache: open a browser, Internet Options > General tab- click on Delete Files.

If any of these configurations were left behind and you had to manually remove it, make sure you restart the Web Server and reboot the system before installing.

Check List for Deploying, Launching and Configuration issues:

Java Issues:
Java versions- While launching the FileMaker Admin Console via Java Web Start, on Mac OS X, if you don’t have Java 5, you will get a message that you don’t have Java 5, you need to install Java 5 before you can launch. You should not get this if you have run the software update with Java.

Java Software Update - If you ran the software update on Mac- “Java for Mac OS X 10.4, Release 5” ( with daylight saving time fixes), you may receive the following error:

"Unsupported JNLP version in launch file: 1.5. Only version 1.0 is supported with this version. Please contact the application vendor to report this problem."

To fix this:

Select the downloaded admin_console_webstart.jnlp file (JNLP) and do a Get Info ( Command+ I)

You can locate the admin_console_webstart.jnlp file where your browser saves downloaded files

Change the “Open with “ which is set by default to “Java Web Start (11.5.0)” to “Java Cache Viewer 11.5.0”
Click on the “Change All” button and click OK on it’s dialog to apply to all JNLP files
Now you should be able to double click and launch application from JNLP with out an error
Web Server issues during deploy:
On Mac OS X, open a browser and type http://localhost, if your web server is running, you should get the default apache web page. If you get an error page, that means the web server is not running. Note that deploy tool turns off the web server to update configuration files. Open a terminal and issue the command sudo apachectl start, to start the Web Server and continue deployment.

On Windows, use IIS management tool or Services to restart IIS.

Other PHP Installations: On Windows, if you already have PHP 5.2 installed in your system and on the deployment wizard, you chose to install FileMaker PHP API and engine, which is the default option, it fails to disable the old PHP. You will get an unknown error on the browser while accessing FileMaker databases. Work around, uninstall your PHP and rerun deployment wizard or choose the second option to use your own PHP and include FileMaker API in the include_path.

Network changes and JNLP issues: If your network or IP address has changed or if you have renewed the DHCP lease, you will not be able to launch the Admin Console from the desktop icon on saved jnlp file. Open the Admin Console Start Page by typing http://:16000 and click on Start Admin Console.


Add comment for this article
Password (You can revise your comment later with this password.)
Security Code
Input this text in the right textarea.
Server Management
Cool Gizmos
Web Design Beyond
FileMaker Tips