Rick Strahl's Weblog
Rick Strahl's FoxPro and Web Connection Weblog
White Papers | Products | Message Board | News |

Web Connection on IIS 7 and Vista


39 comments
June 09, 2006 •

IIS 7 and Web Connection

 

I’ve been working with Vista and IIS 7 for the last week and a half and the good news is that Web Connection works just fine on Vista and IIS 7. Even automatic configuration works in most cases, when IIS 7 has been set up to include for IIS6 Metabase Compatibility:

 

 

 

Although IIS 7 seems to work without any big problems, here’s a guide to manually configuring IIS 7 with the important things required for Web Connection configurations.

 

The steps involved in this are pretty much the same as in IIS 5 and 6, but it’s a bit more complicated to find the right options as everything in the IIS Mangement UI has been moved and renamed. I suppose I’ll get used to this, but I was hunting around a long time for many options – there are  lot of settings that have similar names or names that could be construed for other things.

Enabling up the Application Extension

Like in IIS 6.0, IIS 7.0 is locked down and cannot execute arbitrary ISAPI or CGI extensions. Even ASP classic and ASP.NET are locked down by default and you have to enable them. To do this you need to explicitly enable the application extension:

 

 

Go to the machine root (this is a MACHINE wide setting, not a Web Site wide setting) and go to the IIS settings. Find ISAPI and CGI Restrictions and add a new mapping:

 

Creating a Virtual Directory – er, Application

The biggest change here is that you’ll want to create an Application, not a Virtual Directory. Previous versions of IIS had the concept of Applications vs. just Virtuals but pretty much when you created a Virtual through IIS it always created an Application. An Application in IIS’s sense is that it has its own copy of web.config that configures as a sub-application of the Web Site. This web.config then holds the Application settings for that virtual directory.

 

The good news here is: Web.config is a text file that you can edit and logically at that. Making a change to the file directly affects the configuration settings for the Application! This means for one that you can configure the virtual directory in the web.config file and then simply copy the web.config file with the application: Voila the application settings now are portable.

 

Other than the Application Pools and Virtual Directory Configuration itself (which is stored in a master ApplicationHost.config file in the IIS Configuration directory) you can make any directory level settings in a local web.config file and carry those configuration settings with your applications simply by copying the files. Yay. So setting up the right type of Authentication, setting up script maps (now called Handler Mappings), and anything else that relates to the virtual directory specifically can be set in web.config locally to the app.

Scriptmap or Handler Mapping Configuration

So one of the more important things that need to be done with Web Connection is to create Handler Mapping so that you can execute a .WCSX or .BLOG page using a custom extension. In IIS 7 you do this via Handler Mappings on a Virtual Directory or Web Root:

 

 

One change here is that you can give the extension a descriptive name which is what displays in the list as the name. In addition, you’ll also want to carefully look at the Request Restrictions:

 

 

By default the restrictions are mapped to a file, which means the request needs to find a file on disk or it will throw a 404 – Not Found error before it ever hits your code.

 

If you’re creating mappings to Web Control Framework Pages (WCSX pages for example) then using the File default is Ok, since you will always need a file present. However, if you create classic Web Connection applications that use Process methods and pure code, without a file present, you’ll want to create the handler and uncheck the box as shown above. If at any time you need to execute a request with this extension that doesn’t have a matching page use the unchecked option. I suggest always using this and letting Web Connection handle the file mapping.

 

Note though, that unless this box is checked, Windows Authentication against file system permissions will not work. So if you want to set file system permissions on files and retrieve authentication information from those files you need have this option checked.

 

That’s pretty much it. I’ve been going through running all of my existing Web Connection applications without any problems. Even nicer I didn’t have to recreate my script maps manually in the UI or even using the Web Connection ScriptMaps.prg utility which lets you quickly create scriptmaps by running a small application. Rather I created one map, then simply edited the local web.config file:

 

 

<?xml version="1.0" encoding="UTF-8" ?>

<configuration>

    <system.webServer>

        <handlers>

            <clear />

            <add name="Web Connection Demo" path="*.wwd" verb="*" modules="IsapiModule" scriptProcessor="c:\westwind\wconnect\wc.dll" resourceType="Unspecified" requireAccess="Script" />

            <add name="Web Connection WebLog" path="*.blog" verb="*" modules="IsapiModule" scriptProcessor="c:\westwind\wconnect\wc.dll" resourceType="File" requireAccess="Script" />

            <add name="West Wind Web Control Framework" path="*.wcsx" verb="*" type="" modules="IsapiModule" scriptProcessor="C:\Westwind\wconnect\wc.dll" resourceType="File" requireAccess="Script" preCondition="" />

            <add name="West Wind Admin" path="*.wst" verb="*" modules="IsapiModule" scriptProcessor="c:\westwind\wconnect\wc.dll" resourceType="Unspecified" requireAccess="Script" />

            <add name="West Wind Soap" path="*.wwsoap" verb="*" modules="IsapiModule" scriptProcessor="c:\westwind\wconnect\wc.dll" resourceType="Unspecified" requireAccess="Script" />

            <add name="ASPClassic" path="*.asp" verb="GET,HEAD,POST" type="" modules="IsapiModule" scriptProcessor="C:\Windows\system32\inetsrv\asp.dll" resourceType="File" requireAccess="Script" preCondition="" />

            <add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" type="" modules="ProtocolSupportModule" scriptProcessor="" resourceType="Unspecified" requireAccess="None" preCondition="" />

            <add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Either" requireAccess="Read" preCondition="" />

        </handlers>

    </system.webServer>

</configuration>

 

Unfortunately, it looks like some settings must be made at the ApplicationHost.config level, such as the authentication settings. ApplicationHost.config lives in the <windows>\system32\inetsvr directory and the section in there looks like this:

 

    <location path="Default Web Site/wconnect">

        <system.webServer>

            <security>

                <authentication>

                    <basicAuthentication enabled="true" />

                    <windowsAuthentication enabled="true" />

                </authentication>

            </security>

        </system.webServer>

    </location>

 

I haven’t played around with all the settings to see how this breaks out, but I suspect any truly low level settings need to be applied at the ‘server’ level in ApplicationHost.config. For Web Connection the Authentication is likely to be the only one. <shrug>

 

So the news is good so far with compatibility. I’m looking to build true IIS 7 support using the new WMI providers so hopefully I’ll be able to create the same setup experience as before. I just hope that the process of finding the documentation for this stuff will be a little easier than it was with IIS 6. I seem to remember trying to figure out how to create an Application Pool and set the Script Extension registration was a bitch to figure out without any documentation on the subject.

 

 

Posted in:

Feedback for this Weblog Entry


Re: Web Connection on IIS 7 and Vista



Joost
August 16, 2006

Can you tell me if the IIS7 on Vista has the same restrictions as IIS on Windows-XP: Only 1 webserver can be running?

Re: Web Connection on IIS 7 and Vista



Rick Strahl
August 16, 2006

No you can run multiple Web sites with IIS 7 on Vista. The 10 connection hard-limit is also gone, although IIS still has a governor that will slow it down after more than 10 connections, but no more hard failures on that at least.

Re: Web Connection on IIS 7 and Vista



bill staples
October 27, 2006

Hey Rick - you probably already figured this out, but you can store any <system.webServer> section in web.config. All you need to do is unlock it. you can do that in the UI under 'feature delegation', or in the applicationhost.config file itself by moving the section inside the

<location path="" overrideMode="Allow">

path.

Re: Web Connection on IIS 7 and Vista



Rick Strahl
October 27, 2006

Bill, yeah I know you can remove the override restrictions, but since this is a third party product installing on a server, I can't really change that setting as part of my setup . That would really piss administrators off.

The good news is that right now with IIS 6 metabase compatibility, IIS will still configure correctly so if I set Authentication on the virtual/application it will properly update the applicationhost.config setting. IOW, metabase support does the right thing for both web.config and applicationhost.config which is great.

The biggest install issues I'm left with are the account switching issues (not an IIS problem). Install requires Admin privileges so Vista swtiches to an Admin account, but I also need to install some 'user' specific files (Controls for the VS.NET Toolbox) and I can't figure out how to get them installed into the user's directory since that user isn't actually active when the setup runs (the admin is)...

I'll have to rethink where I place these files I suppose.

Re: Web Connection on IIS 7 and Vista



Nat
December 12, 2006

Hi Rick, Thank you very much for the article. I have enjoyed reading this article as well as many others written by you. I would appreciate if you could provide any help for me with the following problem. I am working on setting up my existing web application that currently runs on IIS 6.0 and Windows XP to run on Windows Vista IIS 7.0. I have got everything working except for httpHandlers. The application’s pool is ASP .NET 1.1 and it is written using VS 2003 and .NET Framework 1.1. I have a dll file that handles processing a number of file extensions. However, calling a file with any of these extensions does not call any methods in the dll to process the request. I have played around with web.config but so far with no success. How should my web.config look like to execute my HttpHandler.
Thank you, Nat

Re: Web Connection on IIS 7 and Vista



Rick Strahl
December 12, 2006

Nat, make sure your application pool is not using integrated pipeline (actually it probably isn't because I think you'd get an error from IIS). In non-integrated Web applications, HttpHandlers work exactly the same as they always have and are pulled in through the standard section in web.config.

Re: Web Connection on IIS 7 and Vista



Nat
December 13, 2006

Rick, I am still not able to get the HttpHandler to process my extension in the large web app. So I decided to create a simple very small web app and get this to work.

Hi,

My small web app is running on IIS 7.0 and Windows Vista. This web app has a reference to NewHandler.dll assembly .

NewHandler assembly contains a class that implements IHttpHandler to process reqests that come from pages with *.15seconds extenstion.

web app is currently running using .NET Integrated Application pool andd the web.config has a section that maps the handler to process *.15seconds pages.

<system.webServer> </system.webServer>

This setup works ok and I get the right output on a page that has .15seconds extension.

Then I change the application pool to Classic .Net App Pool (.Net Framework 2.0) which should pick up this section from web.config for handling requests

<system.web> </system.web>

but instead of correctly processing mypage.15seconds page I get this error:

===================== Server Error in Application "Default Web Site/natapp" HTTP Error 500.0 - Internal Server Error

Description: Handler "15SecondsHandler" has a bad module "ManagedPipelineHandler" in its module list

Error Code: 0x8007000d

Notification: ExecuteRequestHandler

Module: IIS Web Core

Requested URL: http://localhost:80/natapp/mypage.15seconds

Physical Path: D:\Learning\natapp\natapp\mypage.15seconds

Logon User: Anonymous

Logon Method: Anonymous

Failed Request Tracing Log Directory: C:\inetpub\logs\FailedReqLogFiles

Handler: 15SecondsHandler

Most likely causes:

* A module is referenced in configuration, but the module has not been installed or the name of the module is misspelled.
* IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
* IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
* IIS was not able to process configuration for the Web site or application.
* The authenticated user does not have permission to use this DLL.

What you can try:

* Verify that the module is installed. The error description may contain additional information to help you determine which module is causing the error.
* If the module is installed, verify that the module name is not misspelled in the configuration/system.webServer/handlers config section.
* Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
* Check the event logs to see if any additional information was logged.
* Verify the permissions for the DLL.
* Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

More Information... This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

Microsoft Knowledge Base Articles:

*

Server Version Information: Internet Information Services 7.0.

I would appreciate any help you may provide

Nat.

Re: Web Connection on IIS 7 and Vista



Nat
December 14, 2006

Hi Rick,

I have finally found a solution to this problem by posting the same question on iis.net forum. The problem was missing entries in application web.config file. There should be entries in both system.webserver and system.web for handlers. For system.webserver entries there also should be preconditions that state application pool. I only had the correct entry in system.web section.

Nat.

Re: Web Connection on IIS 7 and Vista



Rick Strahl
December 14, 2006

Only if you're running in Integrated mode. If you're running in ISAPI pipeline mode the <system.webserver> section is not required.

Re: Web Connection on IIS 7 and Vista



Makeda
January 18, 2007

I really like your article it helps a lot. Here is my problem.

I installed Vista with IIS 7 and when I try my existing .asp file with database connection am facing the following problem. Can you please help me with it.

HTTP Error 405.0 - Method Not Allowed Description: The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.

Error Code: 0x80070001

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/wwwroot/adcdev/backoffice/loginchk.asp

Physical Path: E:\wwwroot\adcdev\backoffice\loginchk.asp

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

Most likely causes:

The request sent to the Web server used an HTTP verb that is not allowed by the module configured to handle the request. A request was sent to the server that contained an invalid HTTP verb. The request is for static content and contains an HTTP verb other than GET or HEAD. A request was sent to a virtual directory using the HTTP verb POST and the default document is a static file that does not support HTTP verbs other than GET or HEAD.

Re: Web Connection on IIS 7 and Vista



Ueslei
January 29, 2007

I'm with same problem... can someone help us ?

hsh Ueslei

Re: Web Connection on IIS 7 and Vista



Gandor
March 17, 2007

[AllowVerbs]

; ; The verbs (aka HTTP methods) listed here are those commonly ; processed by a typical IIS server. ; ; Note that these entries are effective if "UseAllowVerbs=1" ; is set in the [Options] section above. ;

GET HEAD POST DEBUG

Re: Web Connection on IIS 7 and Vista



rsurve
April 05, 2007

i had same issue (HTTP Error 405.0 - Method Not Allowed) , it resolved by installing the all the isapi (by deafult they are not loaded and CGI and ISAPI restriction icon was also not visible), which can be done from control panel->program->windows feature on-off

select all the entries under IIS section (specialy www service section under IIS), once done you will notice asp, cgi and other option available

You may require admin acces to do this

Re: Web Connection on IIS 7 and Vista



Rosh
April 12, 2007

Hi Rick,

My question is :

I have an appln, under IIS I have created it as both an application and as a Virtual Dir .. I went under M/c root - ISAPI and CGI Restrictions and have added the ISAPI and CGI path as "Myappln.aspx" and gave the description as "ASP.NET v2.0.50727" and then I try to browse it tells me


Service Unavailable

HTTP Error 503. The service is unavailable.


I checked under services and IIS service is Running ..

Any light on how I should proceed ?

Thanx, Rosh

Re: Web Connection on IIS 7 and Vista



Amit
April 22, 2007

Hi,

I Just intalled IIS 7 and now when I go to IIS manager - I don't see the default web site. Do I need to create a default web site manually? to see if my IIS has installed correctly or not, I typed http://localhost in the browser and I get page cannot be displayed". Diagnosis says "localhost is not set up to establish a connection on port "http" on this computer

Thanks Amit

Re: Web Connection on IIS 7 and Vista



Web Design Glasgow
May 14, 2007

I've installed vista, and have just tried to set up a virtual directory in IIS to test an ASP web application. I get the error included below. I tried installing all the components, including windows authentication which I then enabled, but continue to receive the error message. Can anyone provide an explanation of how to set up a virtual directory in IIS 7?

HTTP Error 500.0 - Internal Server Error

Description: The page cannot be displayed because an internal server error has occurred.

Error Code: 0x80070005

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost:80/HandMadeCards

Physical Path: C:\Users\Iain\Documents\intraspin.com\Projects\Hand Made Cards

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: Not yet determined

Re: Web Connection on IIS 7 and Vista



Andrey Petrosyan
May 18, 2007

If you are getting the 405.0 - Method Not Allowed error, you most probably skipped that part of Rick’s article, which discussed web.config file. You could have skipped it for one or two valid reasons:

  1. You did not know where to look for web.config that Rick is talking about, or
  2. Your application does not use file extensions.

Here is what you need to do:

  • Navigate to Handler Mapping feature of your virtual directory, and click on Add Script Map…
  • Put “wc.dll” into “Request Path” field
  • Put a physical path to wc.dll into “Executable” field
  • Click OK
  • Enjoy!

Re: Web Connection on IIS 7 and Vista



Miss Hyder
May 23, 2007

hi Rick,

when i try to build my web application then its gives error of HTTP 404.2 ...can u pls help me to resolve this issue ...i knw that its becuse of lockdown system of web service extension but i dont know how to enable web service extension ...pls help me as soon as possible

Re: Web Connection on IIS 7 and Vista



hugh welford
August 27, 2007

been using connection string cst = "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data Source=c:/access/brits/dating/daters.mdb" to connect to data via IIS6 and win xp pro

This doesnt work on Vista. Can you tell me what has changed please.

Thasnks Hugh

Re: Web Connection on IIS 7 and Vista



Mike Tennor
October 14, 2007

Rick,

I am trying to add script maps for Cold Fusion Pages and Cold Fusion Components. However, after I enter the information in the Add Script Map dialog box and click the OK button, another dialog box appears that says, "Would you like to enable this ISAPI extension? If yes, we will add your extensions as an Allowed entry in the ISAPI and CGI Restrictions list. If the extensions already exist we will allow it." No matter what I do from here, I am not able to save the script map. Please tell me what I should do to get these values accepted into the Handler Mappings.

Thank you,

Mike Tennor Mike.Tennor@Comcast.net

Re: Web Connection on IIS 7 and Vista



Mike Tennor
October 14, 2007

Rick,

Please disregard my previous posting as I figured out the answer myself.

Mike

Re: Web Connection on IIS 7 and Vista



Jayanth
October 16, 2007

Hi All,

i have created web application & if i run it from D:\Test it will open a page called default.aspx. then i opened my IIS & created Virtual Directory calld Test, then i clicked browse for default.aspx & then i got

HTTP Error 404.3 - Not Found Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/Upload/Upload/Upload.aspx

Physical Path: E:\Work_Jayanth\Upload\Upload\Upload.aspx

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

Most likely causes:

It is possible that a handler mapping is missing. By default, the static file handler processes all content. The feature you are trying to use may not be installed. The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.) What you can try:

In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay careful attention to preconditions (e.g. runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay careful attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. Open a command prompt and change directory to %windir%\system32\inetsrv. To set a MIME type, use the following syntax: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz", type the following at the command prompt, and then press Enter: appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. More Information... This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.


Server Version Information: Internet Information Services 7.0.

Please hlp me. i's urjent

Re: Web Connection on IIS 7 and Vista



Samuel
October 28, 2007

Hi.

Your general description seems to be good, or at least it seems to work for most people. Unfortunately not for me, though. I've enabled ASP (since classic ASP is what I want to be able to run - got a helluva lot of development going on using that, unfortunately, or something), but the server just continues to provide me weird error messages, when it isn't trying to force me to download the file. I've even enabled the option "allow unspecified CGI's and ISAPI's to run", but, alas, to no useful result.

As far as I'm concerned IIS7 sucks. Big time.

It is easier for me to install VMware, a second operating system, and going through all that con figuration, than it is to make IIS7 work the way I want. Brilliant, huh? Not really.

Well. Thank you anyway. Obviously your text helps a lot of people, and that is great, too bad I'm not one of them...

Best wishes /Samuel

Re: Web Connection on IIS 7 and Vista



Samuel
October 28, 2007

Ok. So I solved things. In an awkward way, but still...

I installed VMware Server on Vista. Added W2K as a virtual OS inside VMware. Shared the folder in question from Vista. Set the folder as the base for the web site in my virtual W2K. Browsed it from Vista, and did all the editing in Vista as well.

Quite an awkward way of doing things, but considering the fact that I've been trying approximately 3-4 hours/day for a week to get Classic ASP to work under Vista, and this ad hoc solution took... well, an hour perhaps - including installation and configuration of W2K - I must say that I really can't justify the use of IIS7...

Anyway. Just thought that some frustrated person might find this solution useful, and that it therefore might be reason to share it... ??

Best wishes /Samuel

Re: Web Connection on IIS 7 and Vista



George
December 04, 2007

Samuel

All I had to do to get classic ASP running under Vista and IIS 7 was installing the ASP component together with the default IIS settings.

http://blogs.iis.net/bills/archive/2007/05/21/tips-for-classic-asp-developers-on-iis7.aspx

Re: Web Connection on IIS 7 and Vista



pour
January 01, 2008

hi thanks for your article its very useful, i use php and i set iis properly to allow to run it but when i want to upload a file i receive error i have properly set php.ini.

Re: Web Connection on IIS 7 and Vista



David Jones
March 19, 2008

I am getting error 404.4. thjis error indicates that "The resource you are looking for does not have a handler associated with it." How do I associated a handler with this? In the "things you can try it states, "If the file extension does not have a handler associated with it, add a handler mapping for the extension." however, it doesn't explain how to do this. Any help on this would be greatly appreciated. My e-mail (no Spam please) is davidjones022@gmail.com. Thanks in advance.

re: Web Connection on IIS 7 and Vista



SK_RE
June 09, 2009

Hi Rick, i am actually trying to connect to a II7 (64b) pool from a remote machine, using VFP8. The command i was used to use on an old Win2000 server is:

IISPool = GetObject('IIS://srv-r8/W3SVC/AppPools/poolname')

This command seems to do not work on the new server and it give me a "OLE ERROR CODE 0x800401ea".

Maybe i'm missing something, it seem to me that its a permissions problem but i really dont know where to look at now.

Do you have any magic idea to get rid of this error?

Thank you.

re: Web Connection on IIS 7 and Vista



Rick Strahl
June 22, 2009

If it's a permission error you need to fix the permissions. Basically the account that you're using on the client needs to be able to authenticate on the remote machine and has to be an administrative account.

re: Web Connection on IIS 7 and Vista



Meher
July 08, 2009

Hi,

I am getting error 404.4. It says "The resource you are looking for does not have a handler associated with it." In the "things you can try, it states, "If the file extension does not have a handler associated with it, add a handler mapping for the extension." However, it doesn't explain how to do this. Config of System:

OS: Windows Vista Home Edition. Browser: IE 7.0 The system has Visual Studio 2008 installed on it. So the application runs on local host. But it does not have an IIS server installed.

This error cropped up after I tried to run Spike Proxy (Web Application Security Testing tool) on my system, for which I had to change my browser settings. But after using it I changed the settings back to wht they were. But I am still getting the error. Please help me with this…..

Thanks

re: Web Connection on IIS 7 and Vista



Srikanth
October 08, 2009

thanks that worked!!!!

re: Web Connection on IIS 7 and Vista



Keith
March 09, 2010

Thanks for the tip about NOT using Integrated, Rick! It solved the problem I was having with virtual ASPX page links.

Using Code Charger - HTTP Error 404.3 - Not Found



Gunnar Weisskamp
March 25, 2010

Hi I am using Code Charge to create a simple first "Hello World" ASP application. My operating system is Windows Seven Professional. Now when I try to view page in browser I am getting "HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

Now I have tried the following

1 - Checked to make sure that certain settings in the "Turn Windows Features On / Off" for IIS are checked

2 - When I did this I followed you above instructions and made sure that the "IIS Metabase and IIS 6 configuration compatibility" is set.

3 - I even turned the "virtual directory" that I had created in IIS into an “application” directory.

4 – I then explored the “MIME Types” area and added a “.asp” extension. This did get rid of the above initial error “HTTP Error 404.3” but then when I tried to view the page a dialog box “File Download – Security Warning” came up saying “Do you want to open or save this file”. You can click on “open”, “save” or “cancel”. Whichever one you chose does not matter as this is not the expected result in the first place as the page should have just opened up in the browser. 5 – I also made sure that in IIS the page being requested was set as the default page to display

Any help you may have would be great. Kind regards Gunnar

re: Web Connection on IIS 7 and Vista



Simon
April 21, 2010

Hi Rick, I really need to run FoxIsapi.dll on IIS7, but following the above for adding the CGI and ISAPI restrictions, when ever I try to run the following url: localhost/scripts/foxisapi.dll/status? I get the 500.0 - Internal Server Error, is it possible to get FoxIsapi.dll working under IIS7, if so what is the correct procedure to get this working, Thanks Simon

re: Web Connection on IIS 7 and Vista



Rick Strahl
April 21, 2010

I don't know... haven't looked at FoxISAPI in ages. IIS 7 has restrictions against using .dll links directly. you might try using script map links instead.

re: Web Connection on IIS 7 and Vista



Nick
June 03, 2010

I'm trying to install on IIS 7 & Windows Server 2008, and I keep getting a 404.0 error. It's trying to find a file with the extension that I've mapped, and of course it does not exists. Any suggestions?

re: Web Connection on IIS 7 and Vista



Rick Strahl
June 03, 2010

There's a checkbox when you create a script map. It's under the handler mappings and Request Restrictions.

Also make sure that if you're mapping to an ISAPI extension you set the ISAPI/CGI restriction to allow access to the DLL.

re: Web Connection on IIS 7 and Vista



charlie arehart
February 02, 2011

Just a minor correction to your otherwise helpful article (as always). You point out that:

"ApplicationHost.config lives in the <windows>\system32\inetsvr directory"

In case someone may (as I did) try to copy paste that to find it, it should instead be:

<windows>\system32\inetsrv\config

And Rick, in case you may consider changing it in the original entry, note that it's not just adding the \config, but also changing intsvr to inetsrv.

Apache Web Server



Rodolfo Bravo
March 08, 2011

Would you help me for resolving this error? The message error on my notebook is: PS C:\Users\Administrador\downloads\MoodleWindowsInstaller-latest-19\server\apache\bin> .\httpd.exe -k install Installing the Apache2.2 service The Apache2.2 service is successfully installed. Testing httpd.conf.... Errors reported here must be corrected before the service can be started. (OS 10013)Intento de acceso a un socket no permitido por sus permisos de acceso. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs PS C:\Users\Administrador\downloads\MoodleWindowsInstaller-latest-19\server\apache\bin>

Thanks a lot for your help!

 
© Rick Strahl, West Wind Technologies, 2003 - 2022