Jan K. van Dalen
|
| Posted: 08/06/2007, 7:25 AM |
|
Ok, first time running 3.2 & Vista & .Net
I created a simple 1 list 1 update forms and compilation goes thru but with
1 warning:
*************************************************************************
Generating "Footer"
Generating "Header"
Generating "Insured_list"
Generating "Insured_maint"
Generating Common Files
Running
C:\PROGRA~1\CODECH~1\CCResGen.exe \compile
d:\temp\~Test\App_GlobalResources\strings.txt
=======================================
Read in 103 resources from 'd:\temp\~Test\App_GlobalResources\strings.txt'
Writing resource file... Done.
=======================================
Build finished
Warning:Error occurred when creating Virtual Directory in IIS: IIS is not
running, or unable to find the Default Web Site in IIS.
Publishing to "C:\Inetpub\wwwroot\Test"
Publish Project - 0 critical error(s), 0 error(s), 1 warning(s)
*************************************************************************
IIS is running and the directory is created and defined in IIS.
When I try to run Insured_List.aspx this is the error I get:
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/Insured_list.aspx
Physical Path: C:\inetpub\wwwroot\Test\Insured_list.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.
|
|
|
 |
Jan K. van Dalen
|
| Posted: 08/06/2007, 12:40 PM |
|
Ok, found the problem ... .Net and ASP are not installed by default 
"Jan K. van Dalen" <vandj@windmilltechnology.com> wrote in message
news:f97b0i$t3s$1@news.codecharge.com...
> Ok, first time running 3.2 & Vista & .Net
>
> I created a simple 1 list 1 update forms and compilation goes thru but
> with 1 warning:
>
> *************************************************************************
> Generating "Footer"
> Generating "Header"
> Generating "Insured_list"
> Generating "Insured_maint"
> Generating Common Files
> Running
> C:\PROGRA~1\CODECH~1\CCResGen.exe \compile
> d:\temp\~Test\App_GlobalResources\strings.txt
> =======================================
> Read in 103 resources from 'd:\temp\~Test\App_GlobalResources\strings.txt'
> Writing resource file... Done.
>
> =======================================
> Build finished
> Warning:Error occurred when creating Virtual Directory in IIS: IIS is not
> running, or unable to find the Default Web Site in IIS.
> Publishing to "C:\Inetpub\wwwroot\Test"
> Publish Project - 0 critical error(s), 0 error(s), 1 warning(s)
>
> *************************************************************************
> IIS is running and the directory is created and defined in IIS.
>
> When I try to run Insured_List.aspx this is the error I get:
>
> 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/Insured_list.aspx
>
> Physical Path: C:\inetpub\wwwroot\Test\Insured_list.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.
|
|
|
|
|
