Rectangle 27 0

Does ASP.NET MVC have to be installed on the deployment target machine?


404 - Not found. 404.0 - (None) File or directory not found. 404.1 - Web site not accessible on the requested port. 404.2 - Web service extension lockdown policy prevents this request. 404.3 - MIME map policy prevents this request. For the solution Check this link here. I found that link very useful. I hope it will also help you. :)

Yes you dont need to install asp.net mvc3 on the server. The server I'm using don't have Visual Studio on it. You just need a proper server configuration. Apparently there are several reasons that results to 403 and 404 error. 403 - Forbidden 403.1 - Execute access forbidden. 403.2 - Read access forbidden. 403.3 - Write access forbidden. 403.4 - SSL required. 403.5 - SSL 128 required. 403.6 - IP address rejected. 403.7 - Client certificate required. 403.8 - Site access denied. 403.9 - Too many users. 403.10 - Invalid configuration. 403.11 - Password change. 403.12 - Mapper denied access. 403.13 - Client certificate revoked. 403.14 - Directory listing denied. 403.15 - Client Access Licenses exceeded. 403.16 - Client certificate is untrusted or invalid. 403.17 - Client certificate has expired or is not yet valid. 403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0. 403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0. 403.20 - Passport logon failed. This error code is specific to IIS 6.0.

Note
Rectangle 27 0

Does ASP.NET MVC have to be installed on the deployment target machine?


404 - Not found. 404.0 - (None) File or directory not found. 404.1 - Web site not accessible on the requested port. 404.2 - Web service extension lockdown policy prevents this request. 404.3 - MIME map policy prevents this request. For the solution Check this link here. I found that link very useful. I hope it will also help you. :)

Yes you dont need to install asp.net mvc3 on the server. The server I'm using don't have Visual Studio on it. You just need a proper server configuration. Apparently there are several reasons that results to 403 and 404 error. 403 - Forbidden 403.1 - Execute access forbidden. 403.2 - Read access forbidden. 403.3 - Write access forbidden. 403.4 - SSL required. 403.5 - SSL 128 required. 403.6 - IP address rejected. 403.7 - Client certificate required. 403.8 - Site access denied. 403.9 - Too many users. 403.10 - Invalid configuration. 403.11 - Password change. 403.12 - Mapper denied access. 403.13 - Client certificate revoked. 403.14 - Directory listing denied. 403.15 - Client Access Licenses exceeded. 403.16 - Client certificate is untrusted or invalid. 403.17 - Client certificate has expired or is not yet valid. 403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0. 403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0. 403.20 - Passport logon failed. This error code is specific to IIS 6.0.

Note
Rectangle 27 0

Does ASP.NET MVC have to be installed on the deployment target machine?


As bertl said, if you deploy the web app with the binaries, it would work (assuming the correct .NET version is already installed and web site / application pool is configured properly.)

Thanks, Mennan Kara. That was extremely useful. I took option 1 out of the 4 options outlined in that article. I am now getting a 404.

Windows Server 2003 R2 ships with IIS 6. See this about routing: Deploying ASP.NET MVC to IIS 6

Note