2 Replies Latest reply on Dec 23, 2009 12:06 PM by pzingg

    New Server 10 install: Publishing Engine is not running

    pzingg

      Title

      New Server 10 install: Publishing Engine is not running

      Your post

      FileMaker Server version 10.0.2.206, OS X Server 10.5.8 (PowerPC), Apache 2.2, PHP 5.2.11.

       

      I am new to the FileMaker Server world.  I just got and installed FileMaker Server, and I cannot get the PHP Site Assistant to work.  When I try to connect to the server by fully qualifed domain name, I get "Publishing Engine is not running on the specfied server." (Which by the way has a typo in the word "specified").

       

      The "Enable PHP publishing" setting in the Configuration: Web Publishing Engine section of the Admin Console is checked.

       

      If I look at the Overview page in the FileMaker Server Admin Console, I see:

       

      Web Server 

      PHP - On

       

      Web Publishing Engine

      IWP - Off (I don't have Advanced Server, just vanilla Server)

      XML - On

      XSLT - On

       

      Database Server

      ODBC/JDBC - Off

       

      Is this correct, or should there be a PHP indicator in the Web Publishing Engine section?

       

      I ran the PHP test on the sample database (from the "Technology Tests" page), and it claims to be working. (I am using the version of PHP that was installed prior to FileMaker; and I had to add a include_path in the /etc/php.ini file that points to "/Library/FileMaker Server/Web Publishing/publishing-engine/php/lib/php").

       

      If I look at the "Publishing Engine Access" module logs, I see these entries:

       

      2009-12-21 16:26:00    Publishing Engine Access    Error    127.0.0.1:54199 - - "/fmi/conf/config.wpc?-php_enabled=yes" 401 0
      2009-12-21 16:26:00    Publishing Engine Access    Information    127.0.0.1:54202 - fmsadmin "/fmi/conf/config.wpc?-php_enabled=yes" 200 2243
      2009-12-21 16:26:02    Publishing Engine Access    Error    127.0.0.1:54209 - - "/fmi/conf/config.wpc" 401 0
      2009-12-21 16:26:02    Publishing Engine Access    Information    127.0.0.1:54210 - fmsadmin "/fmi/conf/config.wpc" 200 2243
      2009-12-21 16:26:06    Publishing Engine Access    Error    127.0.0.1:54219 - - "/fmi/conf/config.wpc" 401 0
      2009-12-21 16:26:06    Publishing Engine Access    Information    127.0.0.1:54220 - fmsadmin "/fmi/conf/config.wpc" 200 2243
      2009-12-21 16:28:49    Publishing Engine Access    Error    127.0.0.1:54312 - - "/fmi/conf/config.wpc?-xml_enabled=yes&-php_enabled=yes&-xslt_enabled=yes&-language=eng&-iwp_enabled=no" 401 0
      2009-12-21 16:28:49    Publishing Engine Access    Information    127.0.0.1:54313 - fmsadmin "/fmi/conf/config.wpc?-xml_enabled=yes&-php_enabled=yes&-xslt_enabled=yes&-language=eng&-iwp_enabled=no" 200 2243
      2009-12-21 16:28:52    Publishing Engine Access    Error    127.0.0.1:54320 - - "/fmi/conf/config.wpc" 401 0
      2009-12-21 16:28:52    Publishing Engine Access    Information    127.0.0.1:54321 - fmsadmin "/fmi/conf/config.wpc" 200 2243
       

      Is this normal?  It seems as though the access fails for the generic user "-" (401 status code), but succeeds with the "fmsadmin" user (200 status code).

       

      Should I just uninstall and re-install from scratch?  What is the best way to figure out why the "Publishing Engine is not running on the specfied server"?