404.4 error accessing install.php ??? 404.4 error accessing install.php ???
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

404.4 error accessing install.php ???

Started by jtzako, June 17, 2006, 09:00:25 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jtzako

Im trying to get coppermine working on my windows IIS7 server.

I followed the instructions in http://forums.iis.net/thread/1314574.aspx to get PHP enabled in my IIS.

The problem is that it doesnt seem to be working..  I get the error page below if I try to access a php file that is within my wwwroot folder.  Any ideas why this is?
According to the directions I've found for IIS7 I have given php permissions to run... so I must be missing something else.  FYI if I put an HTML file in the coppermine folder I can open that..

Here is the error page I get when I try to access  <mysite>\coppermine\install.php

Server Error in 'JTStuff' Application.
HTTP Error 404.4 - Not Found

Description: The resource you are looking for does not have a module or handler associated with it. It cannot be handled and served.

Error Code: 0x00000000

Notification: ExecuteRequestHandler

Module: IIS Web Core

Requested URL: http://home2:80/coppermine/install.php

Physical Path: C:\inetpub\wwwroot\coppermine\install.php

Logon User: Anonymous

Logon Method: Anonymous

Handler: PHP

Causes:

    * The file extension for the requested URL does not have a module or handler configured to execute the request on the IIS server.

Solution:

    * If you determine that the file extension being denied is required by the Web server, add the appropriate handler for the file extension by following these steps:
         1. From the IISWeb Management tool, open a connection to the web site.
         2. Double click the Handlers Management feature.
         3. Click New Server Module Handler in the Tasks pane.
         4. Complete the Wizard pages to add the handler information, and then click Finish to add the handler to the list.
         5. Go back to the list of management features and double-click the ISAPI and CGI Restrictions Management feature.
         6. Click New Restriction in the Tasks pane.
         7. Complete information for the new extension, check Allow extension path to execute, and then click OK.
   8.
    * Set up a new Failed Request Trace rule for this HTTP status code.
         1. Use the IIS Web Management tool to open a connection to the Web server where the problem is occurring.
         2. In the tree view, navigate to the Web site, and then click to select it.
         3. In the Tasks pane, click Failed Request Tracing.
         4. Check Enable Logging for this Site, specify a logging folder or use the default log folder, and then click OK
         5. Open the Failed Request Tracing Rules feature and click New Rule in the Tasks pane.
         6. Specify the content type to monitor and then click Next.
         7. Check the Status Codes checkbox, type 404.3 in the Edit box, and then click Next.
         8. In the Providers area, make sure that the WWW Server is checked and highlighted, and that in Provider Properties, the Verbosity level is set to Verbose.
         9. Click FinishRequest the page that generated the 404.3 error and then look at the tracing file that was created for the request. This file is located in the logging folder you specified in Step 4.

More Information...
This error means that the IIS server does not recognize the file extension of the requested resource. A module handler is not configured on the Web server for this extension. If the file extension being denied is required by the Web server, add the appropriate handler for the file extension.

Microsoft Knowledge Base Articles:

Server Version Information:
Internet Information Services 7.0.

kegobeer

I would ask for help on the IIS forum where you found your instructions.  We really aren't a server setup support group.  Once you get PHP running, we will be glad to help with any Coppermine specific problems.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Vargha

#2
i suggest you to start using 'APACHE WEBSERVER' its much better, faster, and easier to use, if you want more info pm me, and ill give you a link to setup php, mysql, and the webserver in 1 go  :D pm me because this is not a IIS support forum, do not discuss any further
Haalaa Boro Ye Chayi Vasam Dorost Kon Ta Man Ye Fekri Be Halet Bokonam ;) Ye Hendooneye Shotoriham Biyar Bizahmat :)
Visit My Site www.Rangarang.co.nr
Check Out My Gallery
www.Rangarang.co.nr/buddies
(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fimg157.imageshack.us%2Fimg157%2F838%2Frangarang4xn.jpg&hash=48b4c3087515cafe09fc6d3f7ee19dce86328d8e)

jtzako

I managd to get past that error.... now I have a new one "PHP does not have MySQL support enabled" but I have uncommented ALL the SQL ini files in php.ini but no luck.  Still working on this one. >:(

Sami

This is not PHP/IIS forum  ::)
you should ask these Question under PHP or IIS forum
- create a test.php file and put phpinfo() on it to see what Extension install not properly (put this to your file)
<?php
phpinfo
();
?>

- check your "extension_dir" value under php.ini , is it set properly?
‍I don't answer to PM with support question
Please post your issue to related board

Joachim Müller

This is an IIS setup issue, not a specific Coppermine issue. As kegobeer already suggested, this board is not the proper place to look for support on getting your server running in the first place. I understand that both Vargha and bmossavari are both trying to be helpful, but this simply doesn't cover "our" scope here. After all, we don't recommend self-hosting for very good and valid reasons, and I wouldn't want to give others the impression that we are willing or able to support them in webserver basics. We are not. Get decent webhosting, or find a support board that is dedicated to webserver setup - this one isn't. Period.