Jump to content
Sign in to follow this  
Gnurps

Deployment fails with new FMS12.0v6 installer

Recommended Posts

The new installer for FMS12 on Mac 10.9 does not work for me. During deployment, the Web Publishing Engine fails to stop and fails to start. I initially tried to deploy with the OS X version of PHP, then tried with the Filemaker-provided PHP and got the same result. Here is the deployment log. You can see the Error: 10007 instances on starting/stopping WPE. I don't know how to solve this problem. Machine is an Intel Core 2 Duo 2.66GHz with 4GB RAM running new install of OS X 10.9.1.

Deployment started at 2/17/14 12:59 PM
---------------------------------
SETUP: PRECONFIGURE WEB SERVER

Stop web server                                             succeeded
Create FMI virtual directory configuration file             succeeded
Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded
Update WPE deployment configuration                         succeeded
Test web server (http://172.16.19.2:80/fmi-test/test.xml)   succeeded
SETUP: PRECONFIGURE WEB SERVER

Stop web server                                             succeeded
Create FMI virtual directory configuration file             succeeded
Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded
Update WPE deployment configuration                         succeeded
Test web server (http://172.16.19.2:80/fmi-test/test.xml)   succeeded

UNDO EXISTING DEPLOYMENT

Step 1: Unconfigure Web Publishing Engine (WPE):
Stop WPE                                                    Error: 10007
Set WPE AutoStart to disabled                               succeeded
Update JWPC prefs file                                      succeeded
Update WPE deployment configuration                         succeeded
Step 2: Unconfigure web server:
Stop web server                                             succeeded
Restart web server                                          succeeded
Update WPE deployment configuration                         succeeded

START DEPLOYMENT

Step 3: Save settings:
Save administrative configuration settings                  succeeded
Step 4: Configure Web Publishing Engine (WPE):
Stop WPE                                                    Error: 10007
Set WPE AutoStart to enabled                                succeeded
Add JVM Route to JWPC Server XML file                       succeeded
Create WPC prefs file                                       succeeded
Create CWPC prefs file                                      succeeded
Update JWPC prefs file                                      succeeded
Start WPE                                                   Error: 10007
Update WPE deployment configuration                         succeeded
Update mDNS service info                                    succeeded
Step 5: Configure web server:
Stop web server                                             succeeded
Back up apache configuration file                           succeeded
Create FMI virtual directory configuration file             succeeded
Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf succeeded
Disable line in httpd_server_app.conf: AddDefaultCharset    succeeded
Disable line in httpd_server_app.conf: LoadModule info_module succeeded
Disable line in httpd_server_app.conf: LoadModule status_module succeeded
Disable line in httpd_server_app.conf: AddModule mod_info.c succeeded
Disable line in httpd_server_app.conf: AddModule mod_status.c succeeded
Disable line in httpd_server_app.conf: <Location /server-status> succeeded
Disable line in httpd_server_app.conf: <Location /server-info> succeeded
Add FMI status config file to apache config file            succeeded
Create FMI mod_proxy config file                            succeeded
Disable line in httpd_server_app.conf: LoadModule proxy_ajp_module libexec/apache2/mod_proxy_ajp.so succeeded
Add mod_proxy_ajp to apache conf file                       succeeded
Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf succeeded
Update FileMaker API PHP setting: : $__FM_CONFIG['hostspec'] = 'http://127.0.0.1'; succeeded
Stop web server                                             succeeded
Start web server                                            succeeded
Update WPE deployment configuration                         succeeded
Disable line in httpd_server_app.conf: LoadModule php4_module succeeded
Disable line in httpd_server_app.conf: LoadModule php5_module succeeded
Disable line in httpd_server_app.conf: AddModule mod_php4.c succeeded
Disable line in httpd_server_app.conf: AddModule mod_php5.c succeeded
Disable line in httpd_server_app.conf: <IfModule mod_php4.c> succeeded
Disable line in httpd_server_app.conf: <IfModule mod_php5.c> succeeded
Disable line in httpd_server_app.conf: AddType application/x-httpd-php .php succeeded
Disable line in httpd_server_app.conf: AddType application/x-httpd-php-source .phps succeeded
Create FileMaker PHP configuration file                     succeeded
Add FMI config file to apache httpd.conf: /Library/FileMaker Server/Web Publishing/publishing-engine/php/mavericks/httpd.fmi.conf.php succeeded
Update FileMaker API PHP setting: : $__FM_CONFIG['locale'] = 'en'; succeeded
Restart web server                                          succeeded
Step 6: Configure Database server (DBS):
Set WPE Authorization Info                                  succeeded
Set XDBC AutoStart to yes                                   succeeded
Update XDBC deployment configuration                        succeeded
Update WPE deployment configuration                         succeeded
Start XDBC                                                  succeeded
Step 7: Configure AdminServer:
Save WPE deployment settings                                succeeded
Save web server deployment settings                         succeeded
Save DBS deployment settings                                succeeded
Restart WPE                                                 Stopping the WPE(wpe1) component failed: error code = 10007
Reindex log files                                           succeeded

Deployment completed at 2/17/14 1:12 PM
 

Share this post


Link to post
Share on other sites

The installation notes instruct you to first Uninstall the old version, then reboot, then do the installation.   Did you follow those steps?

 

Also, just rebooting the server at least once is probably a good idea.

Share this post


Link to post
Share on other sites

The installation notes instruct you to first Uninstall the old version, then reboot, then do the installation.   Did you follow those steps?

 

Also, just rebooting the server at least once is probably a good idea.

I did the uninstall first. I rebooted twice. 

Share this post


Link to post
Share on other sites

Hmm.   Are you running OS X plain or OSX Server?  I just did an upgrade/install from FM12v4 to 12v6 after upgrading 10.8.5 server to 10.9.1 server and it worked (after following the uninstall/reboot instructions).   This thread 

https://discussions.apple.com/thread/5142222

sounds as if FMS may get confused as to which apache configuration file it's editing?

Share this post


Link to post
Share on other sites

This was an upgrade from Snow Leopard Server to Mtn Lion Server. I'm not having any troubles with the Server app nor with web serving.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By igservices
      I'm running FMPA 16.02.205 and ScriptMaster 5.05 in MacOS 10.12.6.
      ScriptMaster doesn't retain the activation state from one start of the app to another. It's not totally consistent either.
      Any ideas why the activation of the plug-in isn't being retained between app restarts?
    • By MikeKD
      Hi Folks,
      I've had to wipe my laptop and re-install MacOS. I saved all the files, but Apple support said there was no point in saving the apps because they wouldn't work - I'd have to re-install them too.
      There's no download of FMP15 on the Filemaker website - does anyone know where it's hidden? Unfortunately, FM support doesn't work over the weekend.
      I have splashed the cash and tried to upgrade to FM16 using my old FM15 serial number, but it's not having it.
      Not very impressed with Filemaker "support" at the moment.. you guys are much better!
    • By 3rdparty
      I have been using the the scriptmaster plugin for sometime on a previous Mac, specifically for the Rotate Image function.  The instalation on the previous Mac would have been FMP12 advanced, Scriptmaster plugin from about Sept 2015, and Mac OS 10.11.xx    My solution used the function pasted into the startup script and although it wasn't fast, worked fine.
      I have now made a new installation of the Scriptmater Plugin, v5.05 on a new Mac running OS 10.12.5, FMP advanced 13, and there are a couple of strange things that appear to be assocaited with Java:
      1. When I launch FMP it does not come to the foreground.  Instead the foreground application is Java...
      2. When FMP is active, I see a Java application active in the dock.   This wasnt the case in my prevous installation of Scriptmaster where (if it was active), Java was not a foreground/visible process
      3. When I quit FMP, irrespective of whether the database that I was working on did or did not use a scriptmaster module or function, Java crashes and I get usual dialogue box "Java quit unexpectedly".  I have put a copy of the crash report here.
      Any ideas as to what is going wrong?
       
      Thanks in advance
       
       
    • By MikeKD
      Hi Folks,
      I've broken a pdf saving script which used to work. The filename itself hasn't changed so I don't think that's the problem (there are no /s for instance) - I'm pretty sure it's the file path and Mac OS re-organising itself to sync with iCloud.
      I'm trying to save PDFs to Dropbox and I think that the Dropbox folder on my my has changed location. According to info, the location is /Users/mikekentdavies/Dropbox/KJA Music Library.
      The calculation I'm using to set the location variable is below; can anyone see where I'm going wrong? (I've also tried various combinations of filemac: / file: / .. / : etc having read the FM creating file paths webpage.)
      "filemac:../Users/mikekentdavies/Dropbox/KJA Music Library/Set Lists/"  &  Gig::Gig Name & " - "  &  Gig::Version  &  " Set List.pdf"  
    • By LelandLong
      I read that the new 3.01 version does not require Java.
      When I run FMPAv16 on my Mac (10.11.6) and use the sample Email database it works just fine and I see nothing related to Java. I had the older v2.12 plugin installed on here and have just updated to v3.01 today.
      When I run FMPAv16 on a different Mac (10.11.6) and install the v3.01 plugin (never had the plugin installed on this machine before today) and run the sample database a Java App runs without any windows, Just visible in the lower right dock and its single menu is titled "Java"
      Any ideas as to this oddity?
       
      Leland Long
×

Important Information

By using this site, you agree to our Terms of Use.