IIS MVC web app gets 404.0 error when opening first view page

Question

IIS MVC web app gets 404.0 error when opening first view page

Jay Gunderson 0

I built an MVC web application (about a dozen view pages) that is working fine when run from the VS.net 2019 designer IIS Express, but when I deploy the app to local IIS and run it, I get error...

HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

After weeks of checking every issue I can find, I have to ask for help form the folks here - what am I missing? Here are the steps my app uses to get its first web page to be reached...

I have index.html at the myApp home directory which invokes the first view page...

var host = window.location.host;

var protocol = window.location.protocol; 

var url = protocol + "//" + host + "/myAppLogin/Login"; 

//alert("url: " + url); 

window.location.replace(url);

Here is my RouteConfig.cs...

namespace myApp

{

public class RouteConfig 

{ 

    public static void RegisterRoutes(RouteCollection routes) 

    { 

        routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); 

        routes.IgnoreRoute("");  



        routes.MapRoute( 



            name: "Default",  

            url: "{controller}/{action}/{id}",                

            defaults: new { controller = "myAppLogin", action = "Login", id = UrlParameter.Optional } 

        ); 

    } 

}

}

The myApp properties in VS.net designer shows start action specific page with index.html shown.

I copy the entire project over to C:/inetput/wwwroot

In inetMgr I startup myApp and check bindings and settings, all looks ok on port 80 (default Web Site shut down)

Next I issue this in my web browser - http://localhost/myApp/index.html which gives error...

HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

the 404.0 error page shows RouteConfig.cs did its job correctly...

Requested URL http://localhost:80/myAppLogin/Login

Physical Path C:\inetpub\wwwroot\myApp\myAppLogin\Login Logon

Method Anonymous

Logon User Anonymous

Some other settings that might be appropriate...

Windows 11 pro IIS version 10.0.26100.1 DefaultAppPool .net CLR version v4.0 identity is NetworkService

myApp .net CLR version is v4.0 and identity is NetworkService

myApp web site has physical path C:\inetpub\wwwroot\myApp defaultAppPool and pass-through authentication.

Thanks for any help.

Jay

AgaveJoe 31,361 Reputation points

2025-02-14T19:05:18.6033333+00:00

First, debug the IIS configuration. Place a basic index.html file in the root. Nothing fancy just "Hello World". In IIS, select the application by clicking the application in the connections panel (left). Click the Browse link in the Action panel on the right. If the index.html page renders then we know the IIS application can render static content and is probably working correctly. Take note of the URL in the browser.

If the index.html is not displayed and you receive an error then there is something wrong with the IIS configuration. You'll need to investigate the IIS configuration.

Next debug a basic MVC application deployment. Create a new MVC application and don't change a thing. Simply deploy the MVC application. I assume this is a web application and you are deploying the bin folder with static assets and not copying the source files. Use IIS to browse the application like above. Depending on what happens determines the next troubleshooting steps.
SurferOnWww 6,021 Reputation points

2025-02-14T20:37:08.67+00:00

What is the target framework of your MVC app? .NET Framework 4.8.1? .NET 8.0?

2 answers

Your answer

AgaveJoe 31,361 Reputation points

2025-02-14T19:05:18.6033333+00:00

First, debug the IIS configuration. Place a basic index.html file in the root. Nothing fancy just "Hello World". In IIS, select the application by clicking the application in the connections panel (left). Click the Browse link in the Action panel on the right. If the index.html page renders then we know the IIS application can render static content and is probably working correctly. Take note of the URL in the browser.

If the index.html is not displayed and you receive an error then there is something wrong with the IIS configuration. You'll need to investigate the IIS configuration.

Next debug a basic MVC application deployment. Create a new MVC application and don't change a thing. Simply deploy the MVC application. I assume this is a web application and you are deploying the bin folder with static assets and not copying the source files. Use IIS to browse the application like above. Depending on what happens determines the next troubleshooting steps.
SurferOnWww 6,021 Reputation points

2025-02-14T20:37:08.67+00:00

What is the target framework of your MVC app? .NET Framework 4.8.1? .NET 8.0?

Answer 1

Danny Nguyen (WICLOUD CORPORATION) 7,425 Microsoft External Staff Moderator

Hi Jay,

Based on your description and the responses you've received, the issue is that your MVC application is deployed as a sub-application under IIS (at /myApp/) rather than as the root site, but your routing and JavaScript aren't accounting for this application path.

Your JavaScript is constructing URLs that don't include the application directory path (/myApp/). When you access http://localhost/myApp/index.html, your JavaScript redirects to http://localhost/myAppLogin/Login, but it should redirect to http://localhost/myApp/myAppLogin/Login.

Here's how you can fix this:

Option 1: Fix the JavaScript

Update your JavaScript to include the application path:

var host = window.location.host;
var protocol = window.location.protocol;
var pathname = window.location.pathname;

// Extract the application path (e.g., "/myApp")
var appPath = pathname.substring(0, pathname.lastIndexOf('/'));

var url = protocol + "//" + host + appPath + "/myAppLogin/Login";
window.location.replace(url);

Option 2: Use Base Href

Add a base href to your index.html:

<head>
    <base href="/myApp/" />
    <!-- other head content -->
</head>

Then simplify your JavaScript:

window.location.replace("/myAppLogin/Login");

Option 3: Deploy as Root Site

Instead of deploying to C:\inetpub\wwwroot\myApp, deploy directly to C:\inetpub\wwwroot and configure your site as the root site rather than a sub-application.

Hope this helps.

Danny Nguyen (WICLOUD CORPORATION) 7,425 Reputation points Microsoft External Staff Moderator

2025-07-21T09:00:08.08+00:00

hi just checking in to see if you need any help
Danny Nguyen (WICLOUD CORPORATION) 7,425 Reputation points Microsoft External Staff Moderator

2025-08-12T03:12:17.28+00:00

Just checking in — I haven’t heard back from you for a while,

I hope everything works out as you expected. I understand things can get busy or priorities may shift. If you’re still experiencing the issue or need further support, feel free to jump back in at any time — I will always be here and happy to help.

Wishing you all the best with your work!

Answer 2

Bruce (SqlWork.com) 84,671

You appear to configured you website as an application directory rather than root site. If the url to the index is:

http://localhost/myApp/index.html

then the login route is:

http://localhost/myApp/myapplogin/login

Your JavaScript needs to add the application directory name part of the path. A common approach is to set the base href in document.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base

Then in JavaScript do:

window.location.replace(“/myapplogin/login”);

0 comments