How to install and configure IIS7.0

Hi David,

I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe ran
OK... but it did complain about priviledges. So, I purchased Vista IIS7.0.
I'm not sure how to set it up to run asp and aspx files. When I run it out
of the box, I gives the following error message:

Server Error in Application "Default Web Site"



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/test_asp.asp

Physical Path: C:\inetpub\wwwroot\test_asp.asp

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.

Thanks,

King

Re: How to install and configure IIS7.0

Did you install asp component ?

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"King Coffee" wrote in message
news:%23Ln6UCuXIHA.5160@TK2MSFTNGP05.phx.gbl...
> Hi David,
>
> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe ran
> OK... but it did complain about priviledges. So, I purchased Vista IIS7.0.
> I'm not sure how to set it up to run asp and aspx files. When I run it out
> of the box, I gives the following error message:
>
> Server Error in Application "Default Web Site"
>
>
>
> 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/test_asp.asp
>
> Physical Path: C:\inetpub\wwwroot\test_asp.asp
>
> 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.
>
> Thanks,
>
> King
>
>
>
>

Re: How to install and configure IIS7.0

Hi Bernard,

My current installation consist of the IIS Web Management Tools: Console,
Scripts and Tools, and Service modules. But I don't know how to install or
configure IIS for asp and aspx file extensions.

King


"Bernard Cheah [MVP]" wrote in message
news:ejP%23dhvXIHA.5984@TK2MSFTNGP06.phx.gbl...
> Did you install asp component ?
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "King Coffee" wrote in message
> news:%23Ln6UCuXIHA.5160@TK2MSFTNGP05.phx.gbl...
>> Hi David,
>>
>> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe ran
>> OK... but it did complain about priviledges. So, I purchased Vista
>> IIS7.0. I'm not sure how to set it up to run asp and aspx files. When I
>> run it out of the box, I gives the following error message:
>>

Server Error in Application "Default Web Site"



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/test_asp.asp

Physical Path: C:\inetpub\wwwroot\test_asp.asp

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.

Re: How to install and configure IIS7.0

On Jan 24, 3:26=A0pm, "King Coffee" wrote:
> Hi David,
>
> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe ran
> OK... but it did complain about priviledges. So, I purchased Vista IIS7.0.=

> I'm not sure how to set it up to run asp and aspx files. When I run it out=

> of the box, I gives the following error message:
>
> Server Error in Application "Default Web Site"
>
> 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 i=
s
> not recognized, and is not allowed.
>
> Error Code: 0x80070032
>
> Notification: ExecuteRequestHandler
>
> Module: StaticFileModule
>
> Requested URL:http://localhost:80/test_asp.asp
>
> Physical Path: C:\inetpub\wwwroot\test_asp.asp
>
> 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=3D'string',mimeType=3D'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=3D'.xyz',mimeType=3D'text/plain']
>
> Warning: Ensure that this MIME mapping is needed for your Web server befor=
e
> adding it to the list. Configuration files such as .CONFIG or dynamic
> scripting pages such as .ASP or .ASPX, should not be downloaded directly a=
nd
> should always be processed through a handler. Other files such as database=

> files or those used to store configuration, like .XML or .MDF, are sometim=
es
> 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 type=
s
> using a handler. You should not allows direct downloads of dynamic scripti=
ng
> pages, database or configuration files.
>
> Server Version Information: Internet Information Services 7.0.
>
> Thanks,
>
> King



By default, IIS7 is not installed, and if you just install its
defaults, it only serves static pages and does not run ASP or ASP.Net

If you want to run ASP or ASP.Net, you must install those Features.
See my answer on this thread:
http://groups.google.com/group/microsoft.public.dotnet.frame work.aspnet/brow=
se_thread/thread/70b3ac0a2d7c2342/2c068d639896c134

FYI: The help page that you posted actually tells you exactly what you
need to do. We really tried with those error pages to help you
diagnose and fix your issue, but it seems that we have failed.

It listed three possible likely causes:
1. It is possible that a handler mapping is missing. By default, the
static file handler processes all content.
2. The feature you are trying to use may not be installed.
3. 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.)

It would be clear that #3 is not what you want to do, and #1 is highly
unlikely unless you have tweaked with the configuration by hand. Thus
process of elimination tells you that #2 is the issue -- which is
exactly what we are saying.

Can you help me understand what can be done better so that we can help
you resolve your own issue.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: How to install and configure IIS7.0

Go to turn on/off windows feature. look at IIS section - find asp/aspx

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"King Coffee" wrote in message
news:OPQYt1wXIHA.6044@TK2MSFTNGP05.phx.gbl...
> Hi Bernard,
>
> My current installation consist of the IIS Web Management Tools: Console,
> Scripts and Tools, and Service modules. But I don't know how to install or
> configure IIS for asp and aspx file extensions.
>
> King
>
>
> "Bernard Cheah [MVP]" wrote in message
> news:ejP%23dhvXIHA.5984@TK2MSFTNGP06.phx.gbl...
>> Did you install asp component ?
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis.net/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "King Coffee" wrote in message
>> news:%23Ln6UCuXIHA.5160@TK2MSFTNGP05.phx.gbl...
>>> Hi David,
>>>
>>> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe
>>> ran OK... but it did complain about priviledges. So, I purchased Vista
>>> IIS7.0. I'm not sure how to set it up to run asp and aspx files. When I
>>> run it out of the box, I gives the following error message:
>>>
>
> Server Error in Application "Default Web Site"
>
>
>
> 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/test_asp.asp
>
> Physical Path: C:\inetpub\wwwroot\test_asp.asp
>
> 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.
>
>

Re: How to install and configure IIS7.0

Thanks, the help page got the job done. The problem with the error help
message is: newbie's don't know where to look, especially for none top level
installation options. I've didn't think to look under WWW Services, since,
it wasn't there in previous versions. I'm learning to first checkout ALL the
options, whether ambiguous or not.

Thank you,
King

"David Wang" wrote in message
news:82b53497-be3a-402c-b656-de929a55ddf1@e10g2000prf.google groups.com...
On Jan 24, 3:26 pm, "King Coffee" wrote:
> Hi David,
>
> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe ran
> OK... but it did complain about priviledges. So, I purchased Vista IIS7.0.
> I'm not sure how to set it up to run asp and aspx files. When I run it out
> of the box, I gives the following error message:
>
> Server Error in Application "Default Web Site"
>
> 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/test_asp.asp
>
> Physical Path: C:\inetpub\wwwroot\test_asp.asp
>
> 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.
>
> Thanks,
>
> King



By default, IIS7 is not installed, and if you just install its
defaults, it only serves static pages and does not run ASP or ASP.Net

If you want to run ASP or ASP.Net, you must install those Features.
See my answer on this thread:
http://groups.google.com/group/microsoft.public.dotnet.frame work.aspnet/browse_thread/thread/70b3ac0a2d7c2342/2c068d6398 96c134

FYI: The help page that you posted actually tells you exactly what you
need to do. We really tried with those error pages to help you
diagnose and fix your issue, but it seems that we have failed.

It listed three possible likely causes:
1. It is possible that a handler mapping is missing. By default, the
static file handler processes all content.
2. The feature you are trying to use may not be installed.
3. 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.)

It would be clear that #3 is not what you want to do, and #1 is highly
unlikely unless you have tweaked with the configuration by hand. Thus
process of elimination tells you that #2 is the issue -- which is
exactly what we are saying.

Can you help me understand what can be done better so that we can help
you resolve your own issue.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: How to install and configure IIS7.0

Thanks, I found the asp and aspx installation features. It's working now.

King


"Bernard Cheah [MVP]" wrote in message
news:%23szeBmxXIHA.536@TK2MSFTNGP06.phx.gbl...
> Go to turn on/off windows feature. look at IIS section - find asp/aspx
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://msmvps.com/blogs/bernard/
>
>
> "King Coffee" wrote in message
> news:OPQYt1wXIHA.6044@TK2MSFTNGP05.phx.gbl...
>> Hi Bernard,
>>
>> My current installation consist of the IIS Web Management Tools: Console,
>> Scripts and Tools, and Service modules. But I don't know how to install
>> or configure IIS for asp and aspx file extensions.
>>
>> King
>>
>>
>> "Bernard Cheah [MVP]" wrote in message
>> news:ejP%23dhvXIHA.5984@TK2MSFTNGP06.phx.gbl...
>>> Did you install asp component ?
>>>
>>> --
>>> Regards,
>>> Bernard Cheah
>>> http://www.iis.net/
>>> http://msmvps.com/blogs/bernard/
>>>
>>>
>>> "King Coffee" wrote in message
>>> news:%23Ln6UCuXIHA.5160@TK2MSFTNGP05.phx.gbl...
>>>> Hi David,
>>>>
>>>> I gave up on the IIS5.1, I think I had a bad OS, because msconfig.exe
>>>> ran OK... but it did complain about priviledges. So, I purchased Vista
>>>> IIS7.0. I'm not sure how to set it up to run asp and aspx files. When I
>>>> run it out of the box, I gives the following error message:
>>>>
>>
>> Server Error in Application "Default Web Site"
>>
>>
>>
>> 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/test_asp.asp
>>
>> Physical Path: C:\inetpub\wwwroot\test_asp.asp
>>
>> 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.
>>
>>
>
>