Install WP on IIS – problem with php-cgi.exe
-
Good Day WP Experts,
I am in the process of installing WP on a 2012 R2 Standard server using the supplied instructions from wordpress.org.
I complete all steps for the “Easy 5 Minute WordPress Installation on Windows” https://codex.wordpress.org/Installing_WordPress#Easy_5_Minute_WordPress_Installation_on_Windows
However after step 4, I get a “php-cgi.exe – The FastCGI process exited unexpectedly” HTTP Error 500.0 – Internal Server Error.
None of the steps outline any pre-requisite steps regarding php-cgi.exe.
I’ve tried base installs of Windows 2012 R2 server and fully patched version of 2012R2. All flavors of the OS result in the same error when installing WordPress via MS Web Platform Installer.
Seems there is an undocumented step we are missing. Does anyone have a resolution to this install issue?
Thank you all for your help.
-
Does anyone from WordPress monitor this forum? I mean, if one can’t get past the install with the instructions provided by WordPress.org, then what?
There is clearly a step missing from this process that breaks FastCGI.
WordPress.org’s “5 Minute WordPress Installation on Windows” has turned into 3 days of lost productivity.
https://codex.wordpress.org/Installing_WordPress#Easy_5_Minute_WordPress_Installation_on_Windows
Please, anyone been through this nonsense before? I’m getting very frustrated with the lack complete documentation outlining step by step instructions for a WP on IIS. Web Platform installer is not working as outlined by WordPress.org.
Well, these forums are just about useless. We submitted a pretty concise issue related to the “5 minute Windows Install”, that clearly does not take into account FASTCGI or how to remediate the failed install because of this broken component.
There are no prerequisites outlining FastCGI as it pertains to WordPress.
Not real impressed with anything WordPress.org has to offer at the moment. Certainly customer support is missing. I mean, one of the most important steps in software evaluation is installation!.
I’ve been quite surprised by the real lack of effort to support WordPress.
At least I know the DotNetNuke install works beautifully.
Time to switch gears I guess. I’ll leave WordPress to those devs that have no background in systems and prefer to subscribe to IaaS through a third party vendor sharing their STACK and hardware amongst a pool of users.
We tried WPEngine during or dev cycle which turned out to be a complete dog, and as such was going to move these WordPress sites in-house on our enterprise network. However, because of the complete lack of documentation of WordPress on IIS aside from the “web Installer Platform” which does not work with Windows Server 2012 R2 Standard. This “5”minute install has turned into 5 days of lost time and effort.
As a result of this lost time I cannot in good conscience recommend WordPress for anyone other than the small businesses that does not have infrastructure to support web hosting. In this case go pony-up for a shared WPENGINE or WordPress.com site. Good luck to you, my experience with WPENGINE has been a joke.
I’m sorry you’re having a rough time of it. Installing WordPress is pretty straightforward provided your host meets these requirements.
https://wordpress.org/about/requirements/
Here’s where you went astray.
However after step 4, I get a “php-cgi.exe – The FastCGI process exited unexpectedly” HTTP Error 500.0 – Internal Server Error.
None of the steps outline any pre-requisite steps regarding php-cgi.exe.
I’ve added emphasis to your quote. The problem is with your
php-cgi.exetossing 500 errors. Do you have access to the event log saying what and where the problem is?Keep in mind: most enterprise organizations do not always use Windows servers for critical web apps. And installing WordPress on Windows has always been, frankly, a crap shoot.
If you still want support then we’ll need some tangible information to help you with your problem.
Does anyone from WordPress monitor this forum? I mean, if one can’t get past the install with the instructions provided by WordPress.org, then what?
The only people on these support forums are people just like yourself: unpaid volunteers. WordPress isn’t a commercial product. Yes, there are commercial support organization but not one of them has anything to do with these forums. They’re paid support and these volunteer forums are not for that.
Time to switch gears I guess. I’ll leave WordPress to those devs that have no background in systems and prefer to subscribe to IaaS through a third party vendor sharing their STACK and hardware amongst a pool of users.
I’m not going to get into it with you about that statement. If you don’t want free support then you’re fine. I get your upset but that’s not going to get anyone to take you seriously.
Please keep it factual and avoid anymore attacks, OK? If you need support then I and other’s will try.
Good Day Jan,
I thank you for taking the time to respond to my tirade.
I took a look at the provided link https://wordpress.org/about/requirements/
Which supposedly outlines the requirements.
Curiously enough there is no mention of FastCGI in the requirements you so kindly offered. If it is not required why would the supplied installer from WordPress install FastCGI. Keep in mind the Microsoft Web Platform installer should install and configure all components unless otherwise noted. Why would WordPress.org assemble a distribution on the Windows Web Platform Installer and not supply a working installation or at the very lest full set of instructions so that one could manually install all required components.
The notion that it is a crap shoot to make it work on IIS is ridiculous. If this is the case they should not offer the solution at all. Is that the technical answer for WordPress on IIS a “crap shoot”. That response in itself is pretty telling.
Event Viewer Log:
Faulting application name: php-cgi.exe, version: 5.5.34.0, time stamp: 0x56fc3025
Faulting module name: MSVCR110.dll, version: 6.3.9600.18194, time stamp: 0x569515fc
Exception code: 0xc0000135
Fault offset: 0x0009d3c2
Faulting process id: 0x110
Faulting application start time: 0x01d1a64b9ce0f180
Faulting application path: C:\Program Files (x86)\PHP\v5.5\php-cgi.exe
Faulting module path: MSVCR110.dll
Report Id: da8fdde5-123e-11e6-80b8-00155d009207
Faulting package full name:
Faulting package-relative application ID:Just to clarify before looking at the problem:
Curiously enough there is no mention of FastCGI in the requirements you so kindly offered. If it is not required why would the supplied installer from WordPress install FastCGI.
There’s no mention of
mod_php,php5-fpm,nginx,Apacheeither. They really are high level requirements and that works for the majority of users. That also applies to the “Famous 5 Minute” install but as you’re finding out, that’s not always the case.The notion that it is a crap shoot to make it work on IIS is ridiculous. If this is the case they should not offer the solution at all. Is that the technical answer for WordPress on IIS a “crap shoot”. That response in itself is pretty telling.
I really get that you’re upset but honestly, for most users it really does just work.
*Looks at error messages*
This is a problem.
Faulting application name: php-cgi.exe, version: 5.5.34.0, time stamp: 0x56fc3025
The minimum requirements for PHP is 5.6. You are running 5.5.34. Even if it didn’t crash with a 500 error it’s not going to work long or at all.
*Looks more*
This site https://php.iis.net/ eventually leads me to Microsoft’s site for PHP 5.3 which is even less helpful.
I’ll ping some people and ask them. If you can get PHP up to 5.6 at least and mysql 5.6 on your system in a supportable way then you should be all set to run WordPress on your IIS server.
Well, what we have installed is what the web Platform installer installed as part of the WordPress package.
Are you saying that WordPress’ installer is using out of date distros. Two thoughts with that. First, if this version of WordPress does not support PHP 5.5.34 then why does the installer install the wrong version. As far as I know this is the latest and greatest Web Platform Installer available. Secondly if the PHP version is too old I’d expect the WordPress version to match the PHP version it is installed on. Meaning there is no excuse for a non working install.
The Web Installer for WordPress installed the following components.
IIS Rewrite Module 2
Microsoft Web Deploy 3.5
Microsoft Web Platform Installer 5.0
MySQL Connector Net 6.9.7
MySQL Server 5.1
Windows Cache Extension 1.3 for PHP
Quick Look at the Handler Mappings Enabled PHP55_via_FastCGI path*.php – Enabled -File or Folder Handler(fastCGi Module)
Quick Look at the Handler Mappings Disabled
CGI-exe path *.exe State disabled Handler CGI Mogule.Keep in mind all these items are configured by Web Platform Installer 5. There should be no additional requirements from my end, if there are they are undocumented steps.
Trust me, I get I can drop IIS and go with a LAMP or WAMP stack, but this is not my goal. I have other resources that use IIS and from a technical perspective this should be doable. Something is just hosed in this new installer that isn’t either setting a permission or a path correctly. I’ve configure WP using an older web platform installer in the past on my 2008r2 host, albeit several versions old, but I had 0 problem with the deployment, which is why I am so frustrated at the moment. I’m getting paid a lot of money to troubleshoot an installer problem. Hey, I am happy– I would think that my customer is second thinking WordPress though. At some point the expense of standing up the solution gets outweighed by another product. DNN is my next go to. I works like a charm, however requires a bit more experience as a developer to take advantage of the full feature set.
If we can’t get past this hurdle I’ll have to redirect them to another solution. My customer refuse to pay for hosting as we have more than enough resources available in-house to include two datacenters. If you already have the equipment and licenses in hand, why would you subscribe to software as a service or switch to a LAMP stack just for WordPress?
My opinion is WordPress has gotten to cozy with hosting providers and the business model is to avoid support for roll your own solutions.
This is incredibly frustrating… Another day wasted on WordPress, this is a total of 4 days now. I’d consider paid for support for WordPress, but not for installation issues. If you can’t get past step one why consider paying for step two. LOL.
It’s been quite a few days.
Are you saying that WordPress’ installer is using out of date distros.
I’m not saying that at all: WordPress.ORG does not distribute any installer for any platform. That site is a Microsoft site, not WordPress.
The requirements for WordPress is to have PHP and MySQL operational on your server before installing WordPress.
WordPress is a PHP framework that needs those requirements to be met first. Then you can install WordPress on top of that. That true for all platforms, Linux or otherwise.
Try this. For PHP visit this link.
http://windows.php.net/download
I recommend that you download and read up on the PHP 5.6 (5.6.21) in the middle of the page. WordPress works fine on PHP 7.0.6 (I run that on my server) but I think playing it safe is the way to go. While WordPress works fine with PHP 7 some plugins will work better with PHP 5.6 for now.
If your MySQL is 5.6.x then you should be fine. But if not then consider installing from this site.
http://dev.mysql.com/downloads/installer/
That has 5.7.12 and that will work fine.
Be aware that the site says “Note: MySQL Installer is 32 bit, but will install both 32 bit and 64 bit binaries.” so don’t be concerned if you have a 64 bit OS with a 32 bit installer.
Once you have PHP and MySQL installed and working on your IIS server then you should be good to go using these instructions.
I’ve never installed PHP on IIS so if you do use that link please read up on the installation first. The PHP link should have installation instructions.
Hey Jan,
Thanks for your thoughtful email You have no idea how much I appreciate the attempt, even if we don’t make it.
However, I think with these instructions I could just ditch the Web Platform installer.
I’d already made up my mind if we can’t get WordPress over IIS sorted this morning, I’ll go with a WAMP stack temporarily and work on the IIS issues on my time.
Thanks again!!
You’re welcome. 😉 I hope you get the IIS portion sorted out sometime.
- The topic ‘Install WP on IIS – problem with php-cgi.exe’ is closed to new replies.