Try our conversational search powered by Generative AI!

'HTTP Error 404.3 - Not Found'-Error after migrating site from IIS6 to IIS7.5

I migrated a website from IIS 6 to IIS 7 on another web server.
I set up a new application pool for ASP.NET 4 and installed a new site. I fixed web.config to solve the subsequent errors due to that IIS 7 has some handlers
per default in the web.config (duplicate errors).

ASP.NET is installed for IIS.

When I browse the website I for some reason get to a page saying: 'Only CoreFiles installed".
Maybe it is because that showing default.aspx doesn't work.

I get the following error when browsing the file default.aspx (set to the default-page of the website).

Server Error in Application "LEVANGER" Internet Information Services 7.5 Error Summary 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. Detailed Error Information Module StaticFileModule Notification ExecuteRequestHandler Handler StaticFileHandler Error Code 0x80070032 Requested URL http://localhost:5090/default.aspx Physical Path D:\EPiServer\Sites\inter.levanger.noCMS6\default.aspx Logon Method Anonymous Logon User Anonymous 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.) If ASP.NET is not installed. Things you can try: In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra 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. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\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": 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. Install ASP.NET. 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. Links and 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 s


Jan 10, 2013 14:37

Addition of information: I have converted the web.config-files to IIS7.

Jan 10, 2013 15:11

It seems you are missing a proper registration for the page handler / .aspx extension since it selects the static file handler to deliver the file. I suggest you install a demo site on the same IIS7 and compare the handlers and modules sections under system.webServer of that site to those of your converted site.

Jan 10, 2013 16:01
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.