We upgraded our Windows Server running Windows Server 2003 R2 from FMS11 to 12 and PHP stopped working. All files with a.php extension yield a 404 error. We re-deployed several times.

According to KB6538, the deployment wizard...

• Adds a PHP filter in the ISAPI Filters tab.
  
  
• Adds the filename index.php to the list of default content pages in the Documents tab.
  
  
• Maps the .php filename extension to the newly installed PHP engine in the Application Extensions list. To see this setting, click the Home Directory tab, Configuration button, then the Mappings tab in the Application Configuration dialog box.
  
  
• Adds PHP to the Web Service Extensions list in Windows Server 2003 only. This setting is in the Internet Information Services (IIS) Manager under the Web Services Extensions node.
  

None of those settings appeared: no ISAPI filter, no index.php in Documents tab, no .php mapping, and no Web Service Extension. Yet the deployment log says those changes succeeded. (log below)

I did a little work to try to manually change those settings and decided I do not know IIS well enough.

I don't know how to overcome this deployment problem, nor does our IT manager. Any ideas?

Thanks.

Gary

Deployment log:

Deployment started at 11/3/12 4:15 PM

---------------------------------

SETUP: PRECONFIGURE WEB SERVER



Stop web server succeeded

Create PHP test page virtual directory succeeded

Restart web server succeeded

Start default web site succeeded

Update WPE deployment configuration succeeded

Test web server (http://128.117.97.210:80/fmi-test/test.xml) succeeded



UNDO EXISTING DEPLOYMENT



Step 1: Unconfigure Web Publishing Engine (WPE):

Stop WPE succeeded

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 , Attempting stop..., , Internet services successfully stopped, , Attempting start..., , Restart attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput:

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 succeeded

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 succeeded

Update WPE deployment configuration succeeded

Update mDNS service info succeeded

Step 5: Configure web server:

Stop web server succeeded

Back up IIS metabase succeeded

Create PHP test page virtual directory succeeded

Restart web server succeeded

Start default web site succeeded

Create worker properties file succeeded

Create Workers mount file succeeded

Install ISAPIRedirect web server extensions succeeded

Create isapi_redirect properties file succeeded

Create jakarta virtual directory succeeded

Install Isapi redirect filter succeeded

Update FileMaker API PHP setting: : $__FM_CONFIG['hostspec'] = 'http://128.117.97.210:80'; succeeded

Stop web server succeeded

Start web server , Attempting start..., , Start attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput:

Update WPE deployment configuration succeeded

Update FileMaker PHP ini file succeeded

Create PHP ini registry entries succeeded

Add PHP path to PATH environment variable succeeded

Create PHPRC environment variable succeeded

Uninstall FileMaker PHP Module succeeded

Backup fcgiext.ini succeeded

Add PHP extension to IIS succeeded

Set PHP instance max requests to 10000 succeeded

Set PHP activity timeout to 600 succeeded

Set PHP request timeout to 600 succeeded

Set PHP PHP_FCGI_MAX_REQUESTS to 10000 succeeded

Update FileMaker API PHP setting: : $__FM_CONFIG['locale'] = 'en'; succeeded

Restart web server , Attempting stop..., , Internet services successfully stopped, , Attempting start..., , Restart attempt failed., , IIS Admin Service or a service dependent on IIS Admin is not active. It most likely failed to start, which may mean that it's disabled., , ErrorInput:

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

Start WPE succeeded

Reindex log files succeeded



Deployment completed at 11/3/12 4:17 PM

• 
  
  

To solve this problem, we upgraded to Windows Server 2008 with IIS 7. We built a fresh install of the OS, ran the FMS 12 installer, and used the Deployment Assistant. It did install PHP, but PHP was still not working. Our IT guy had to do a lot of tweaks to get PHP running -- sorry, I don't know what he did. It was not as smooth as it should be, but at least we have CWP running again.

 

Filemaker's PHP install came in with error reporting set to E_ALL + Deprecated. My check-email function used eregi which was deprecated recently. IIS was just throwing a HTTP 500 error -- unknown error -- and not displaying the PHP info. It took us a while to figure that out.

 

Other files threw PHP errors because of the max-level reporting set in PHP.ini. The errors were our programming mistakes, but the HTTP500 error blocked the PHP error display and made it really difficult to learn what was going on. 

 

This install was way too complicated.