PHP warning instead of 404 error

neejoe

Hello!

I have Windows 2000 Server with IIS 5.0 and PHP 4.3.1 installed (ISAPI).

The problem is when I try to browse a PHP page that doesn't exists on the server (eg. http://server/blah_blah_type_anything.php or any URL that ends with a .php extension) - instead of IIS 404 error, I get a PHP warning message:

Warning: Unknown(C:\www.php): failed to create stream: No such file or directory in Unknown on line 0
Warning: Unknown(): Failed opening 'C:\www.php' for inclusion (include_path='.;c:\php4\pear') in Unknown on line 0

How can I solve this? 😕 This isn't critical problem, but it's annoying me.

Is there any entry in php.ini that needs to be modified? Thanks in advance! 🙂

touchingvirus

seems to be an IIS problem..

it doesnt happen on my apache2

Nedly

I have the same problem, and I am running apache 2 myself. As far as I can tell, the problem is related to PHP 4.3+. I tried running PHP 4.3.2 and the error then provides a link to the manual at PHP.net.

I haven't figured out how to fix the problem (the manual doesn't give great instruction on this), but it has something to do with docref in httpd.conf(although with IIS I have no idea).

I do beleive that there is a way to prevent the error from showing without turning off all errors.

If anyone else can help please let me know

neejoe

I've updated PHP to 4.3.2 [ISAPI], but it doesn't help [still running W2K and IIS 5.0].

I noticed that, when I type anything that ends with .php extension I get warning message:

[...] failed to open stream: No such file or directory in Unknown on line 0,

but when I try to refresh the non existing page, the warning disappears and I get blank page.

Here are some similar bugs:
http://bugs.php.net/bug.php?id=14409
http://bugs.php.net/bug.php?id=16450

I guess that I'll have to setup PHP to execute as CGI, here is the quote from install.txt:

PHP 4 for Windows comes in two flavours - a CGI executable (php.exe), and several SAPI modules (for exapmle php4isapi.dll). The latter form is new to PHP 4, and provides significantly improved performance and some new functionality. However, please note that the SAPI modules are NOT yet considered to be production quality.

In particular, with the ISAPI module, you are likely to encounter serious reliability problems especially on platforms older than W2K - you may witness a lot of server 500 errors and suffer from other server modules such as ASP also failing. You have been warned!

The reason for this is that the PHP SAPI modules are using the thread-safe version of the PHP code, which is new to PHP 4, and has not yet been tested and pounded enough to be considered completely stable, and there are actually a few known bugs. On the other hand, some people have reported very good results with the SAPI modules, and there a few reports of problems with the Apache module version.

In short - your mileage may vary; If you need absolute stability, trade the performance of the SAPI modules with the stability of the CGI executable.

ISAPI version works just fine, except for this stupid annoyance...

piersk

Do you have your own server?

neejoe

Originally posted by piersk
Do you have your own server?

Yep, although it's not actually mine, it's rented 😉

drewhealey

I don't know if this will help but I am running IIS 5.1 on my test box (WinXP) with PHP 4.3.3.3 and I get the standard 404 error.

I'm not sure if this is because of the version of PHP or IIS but you may want to try updating PHP... if possible. My production box is running IIS 5 and I don't get the error on that box either. I'm not sure what version of PHP I am running on that box though.

I set up PHP in IIS manually so that too could be the reason. The only thing I set up in IIS was the following:

IIS > Web Sites > Properties > Home Directory > Configuration > Mappings > "Then add the following"

Executable: c:\php\php.exe -or- %phpdir%\php.exe
Extension: .php
Verbs: All Verbs (not sure if there are security impications)
Script Engine: "Checked"
Check that file exists: "Checked" (works if checked or not)

Hope some of this info helps. I'll try to check my production box tomorrow and post what I find.

Drew

neejoe

It's an IIS issue. The solution is to turn on "Check if file exists" for the PHP application mapping 🙂

When the file checking is enabled for PHP mapping, the 404 displays normally. If disabled, IIS tries to execute nonexisting PHP file and then outputs the PHP warning message instead of 404 error.

nasty_psycho

IIS 5.1 Window XP Pro + PHP 4.3.2 is working perfectly , but of course not as good as linux