Posted 1 year ago #
I don't get it. I've never seen a problem like this, and I guess this is why I know I'm still green. I set up my config file, and then I got this error before the installer ran:
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.
Can anyone tell me what this might be? Check me online at
http://www.carigblog.com/index.php
Posted 1 year ago #
It looks to be an issue with the (IIS) server your site is on, which is obviously running PHP in CGI mode. I would contact your host with the error.
Posted 1 year ago #
I checked just now with the server team - they said nothing seems to be wrong. I'll get them to check the IIS.
Is there anything else I can try?
(Interesting though... I installed a lot of these blogs - never had a problem!)
Posted 1 year ago #
Ok... We reset IIS, and still nothing. What Next? Sigh...
Posted 1 year ago #
This is not an issue of having to reset the server:
http://help.globalscape.com/help/purecms3/Error_Message__CGI_Error-The_specified_CGI_application_misbehaved_by_not_returning_a_complete_set_of_HTTP_headers.htm
http://bugs.php.net/bug.php?id=25863
For a quick check of PHP on the server, create a PHP document (say test.php) with just the following in it:
<?php
phpinfo();
?>Upload that doc to your server and access it through your web browser. If it generates the same error...
Seen this on a number of different hosts and the only thing I've been able to suggest is to consider changing over to a linux based host.
This happens on NT IIS servers running FastCGI. The phpinfo runs fine. 2.3.2 returns the CGI error, and 2.3.1 will display the initial installation screen (not properly formatted) asking for the blog/email info but after enter that information, it will return "HTTP Error 404 - File or directory not found. Internet Information Services (IIS)"
Here's an example phpinfo experienced recently:
------------------------------
PHP Version 5.1.4
System Windows NT D100 5.2 build 3790
Build Date May 4 2006 10:30:29
Configure Command cscript /nologo configure.js "--enable-snapshot-build" "--with-gd=shared"
Server API CGI/FastCGI
Virtual Directory Support enabled
Configuration File (php.ini) Path C:\WINDOWS\php.ini
PHP API 20041225
PHP Extension 20050922
Zend Extension 220051025
Debug Build no
Thread Safety enabled
Zend Memory Manager enabled
IPv6 Support enabled
Registered PHP Streams php, file, http, ftp, compress.zlib
Registered Stream Socket Transports tcp, udp
Registered Stream Filters convert.iconv.*, string.rot13, string.toupper, string.tolower, string.strip_tags, convert.*, consumed, zlib.*
Zend logo This program makes use of the Zend Scripting Language Engine:
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
with Zend Extension Manager v1.0.11, Copyright (c) 2003-2006, by Zend Technologies
with Zend Optimizer v3.2.2, Copyright (c) 1998-2006, by Zend Technologies
Posted 1 year ago #
I'm experiencing ( possibly related? ) problems with a similar setup ( http://wordpress.org/support/topic/150672 ).
Do you have available the result of phpinfo(INFO_MODULES); for a WIN/IIS6 system WITHOUT fastCGI that's known to work?
What I mean is, the previous post seemed to imply that it is FastCGI that's causing the headache -- is that a gut feeling, or do we know for sure?
TIA,
-dhbarr.
Posted 1 year ago #
I had a similar problem with my installation, but I resolved it by following the tip from CGI Error with pages.
@dhbarr -- didn't mean to imply it was FastCGI causing the problem but the 4 or 5 times I've checked the phpinfo on problem sites, FastCGI was in use.
Posted 1 year ago #
@MichaelH:
I'm going to give it a try today. I'll leave EVERYTHING else the same, except modify WordPress to not use FastCGI at all, but rather the default php handling method.
I have a hunch that there's a version issue somewhere in the php-mysql-fastcgi triangle, based on this post:
http://www.iis.net/articles/view.aspx/IIS7/Hosting-Web-Applications/PHP/PHP-Applications-on-IIS---WordPress
Today I'll try disabling FastCGI first, down-revving MySQL next, down-revving PHP after that, and finally walking backward through WordPress releases as a last resort. Hopefully ONE of these options will clear up the mystery.
Posted 1 year ago #
@MichaelH:
Change that "4 or 5 times I've checked the phpinfo on problem sites" to "5 or 6 times". :)
I changed IIS6 for that particular website to use php5isapi.dll instead of fcgiext.dll, and presto!
Some combinations of IIS6, PHP5, and FastCGI simply do not work -- apparently this is FastCGI's fault, which isn't entirely surprising since it's only a tech preview.
This fix is to use php5isapi.dll instead.
Thanks Again,
-dhbarr.
Thanks for that information dhbarr!!
So guess this is something a host would typically have to change for a user?
Posted 1 year ago #
Dunno if this helps this particular user, but it helped me personally...
I use Easy-CGI for my host provider and was running into this same error when I went to upgrade from 2.3.1 to 2.3.2. Easy-CGI allows you to use either PHP v4.4.4 or 5.2.4. Through their configuration menus, I discovered I was using 4.4.4 - once I changed it to 5.2.4, the error message went away. So something must be different between how Easy-CGI has 4.4.4 vs. 5.2.4 configured.
Here's an explanation for dhbarr about how he solved the problem (see above) Thanks David.
Under %systemroot%/inetserv/fcgiext.ini I snipped out the reference to this particular subsite. I then added the PHP ISAPI Web Services Extension to this particular subsite, and set php5isapi.dll as the .php handler instead of fcgiext.dll for this subsite only. See steps 3.1 and 3.2 from this link if you're not typically a Windows guy : http://www.peterguy.com/php/install_IIS6.html
Posted 1 year ago #
I fretted over this for about 2 days. I'm a "wannabe" tech guy, but can't quite follow all the technical jargon. Form what I understood, it's a compatibility issue anyhow and that my particulary configuration didn't work.
I'd installed WordPress many times on many servers and never encountered this problem.
What I did (and it worked) was simply install WordPress 2.3.1. I had to hunt around a bit to find that version, but Presto! it works.
Trying WordPress 2.3.1 has not worked, at least on the several hosts I've had a occasion to try...
While 2.3.1 may not display the CGI error, it will display the installation screen in an unproperly formatted mode, allow you to enter the Blog title and Your email fields, but when you click on the Install WordPress button, it will display an error page with the message "The page could not be found...(HTTP Error 404 - File or directory not found. Internet Information Services (IIS))"
Another comment here -- tried commenting out line 163 in wp-includes/wp-db.php and retried the installation. Doing that resolved the CGI error message display, but it displayed the installation screen in an unproperly formatted mode, allowed entry of the Blog title and Your email fields, but when clicking on the Install WordPress button, it displayed an error page with the message "The page could not be found...(HTTP Error 404 - File or directory not found. Internet Information Services (IIS))"
Posted 1 year ago #
Make sure your temp and sessions directory is writable by NETWORK.
Best way to cure it is to create C:\Inetpub\Temp and C:\Inetpub\Sessions and edit php session save path to the new sessions directory and temp to the new temp directory. Restart IIS to read the new config. This should stop the problem.
Another thng is make sure
cgi.force_redirect is set to 0 ,cgi.rfc2616_headers = 1, cgi.fix_pathinfo is set to 1.
Posted 1 year ago #
I can't change server side, so I fixed this problem simply rewrite the wp-include/db.php like suggested here.
But now the problem can be showed again on the next upgrade..
Saw recently with one host, http://www.hostnexus.com, that with their Plesk control panel, they allowed PHP, via a check box, to run as an ISAPI extension. WordPress 2.3.3 installed just fine.
Connecting the dots... http://trac.wordpress.org/ticket/5951
Posted 1 year ago #
What is unclear is why 2.3.3 is failing but earlier versions worked just fine. "Upgrading" to a Linux host isn't an option if you also run other non-Linux applications on the server.
On the same server 2.2.1 works correctly.
Posted 1 year ago #
I have encountered this issue as well on a Windows 2003 server. I operate the server (I am the host) and moving to Linux is not going to happen.
- I can run phpinfo - no problem - PHP is running fine.
- I have several (earlier version) instances of wordpress running on my server so I know WP is easy to install and use on Windows.
- I note that whatever code was posted at this location no longer exists, so it is unclear what that solution looked like.
- I have installed version 2.3.1 on this subject site and it worked just fine. Why does 2.3.3 have a problem, and does anyone have a definitive solution?
Thanks!
Posted 1 year ago #
I second @gbdg
http://wordpress.pastebin.ca/893007no longer has the code we need
can someone show us the code please?
Posted 1 year ago #
Ditto...I would also love to see the code we need.
Posted 1 year ago #
also, not only Installation of 2.3.3 will have this problem, but also 2.3.1 + permlink will have the same error msg
meaning I can install 2.3.1 and make wordpress up-n-running, but if I enable permlink, then visit a post using its permlink, I will hit the same error as OP
jsnielsen - can your host run PHP as an ISAPI extension?
Also, thanks to webdesigner and gary I've attached the 'purported to work wp_db.php code' at trac. Again, that code may or may not work.
Thank you for your persistence in this matter and we'll look forward to hearing your results.
Posted 1 year ago #
Michael, don't know if they can.
I'll see if I can get your code to work.
Posted 1 year ago #
Hey Michael,
unfortunately it didn't work. After I upload it, I get the error:
PHP Warning: require_once(D:\Domains\pipforhelvede.net\wwwroot\wp25/wp-includes/wp-db.php) [function.require-once]: failed to open stream: No such file or directory in D:\Domains\pipforhelvede.net\wwwroot\wp25\wp-settings.php on line 123 PHP Fatal error: require_once() [function.require]: Failed opening required 'D:\Domains\pipforhelvede.net\wwwroot\wp25/wp-includes/wp-db.php' (include_path='.;C:\php5\pear') in D:\Domains\pipforhelvede.net\wwwroot\wp25\wp-settings.php on line 123
Posted 1 year ago #
Ok, I guess what I'd really like to get answered right now is this:
- Is this error something the WP people is taking care of, or is this considered an IIS thing, with no subsequent responsibility for/from the WP people ?
- Is this an error being looked into for a fix ?
- If the WP people are working on a fix for this, what's the ETA ? (If anyone knows)
It's a bleeding shame, WP has all I need, but I need to move on to e.g. Joomla or something, if this issue isn't really being worked on, since I can't really change the way my host is running their software.
Then I have to change hosts too, and I then lose the ability to do asp.net and possibly Ruby soon.
This topic has been closed to new replies.
