we developed an asp.net mvc 4 application. in vs 2012 this work fine. we publish this web application and putting it on iis 7.5, but when we want to browse web application t
In my case the problem was with the Physical Path setting.
It was pointing to C:\inetpub\wwwroot\MySite
but the imported site was actually at C:\inetpub\wwwroot\MySite\Default Web Site\MySite
I changed the path in iis via MySite -> Edit Site -> Basic Settings and I was off to the races.
In my case Default Web Site was mapped to a different application. When I was trying to access my app inside Default Web Site I got the 403.14 error.
The solution was to remap Default Web Site to default C:\inetpub\wwwroot.
Open Elevated Command Prompt in Windows (Run command prompt as Administrator).
And run the command aspnet_regiis -i
at the .Net Framework and .Net Framework64 location. Just like below, Here parameter i
means install the ASP.NET version 4. The first command is for 32 bit and second is for installing the 64bit version.
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis -i
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i
The commands is used to register ASP.NET applications with Internet Information Services (IIS) server.
I would comment on @Seth's answer if I had 50 rep. It's not just a search and replace problem. There is a Refactor --> Rename Bug in Visual Studio 2012 that wrongly renamed the "id" inside the literal string value of the url parameter in my RouteConfig.cs. Of course, it's resolved as "won't fix", so be warned.
routes.MapRoute(
name: "Default",
url: "{controller}/{action}/{id}",
defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
);
was changed to
routes.MapRoute(
name: "Default",
url: "{controller}/{action}/{replaced_text}",
defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
);
I had the same error but none of the above solutions worked for me, it ended up that i had .Net 4.6 installed on my development machine, but the project was targeting .net 4.5. I couldn't understand the reason as to why this happened, but nonetheless this thing worked for me.
This happened to me because I mistakenly ran an unrelated search and replace that renamed the 'id' parameter (3rd line) in Global.asax.cs:
routes.MapRoute(
"Default", // Route name
"{controller}/{action}/{id}", // URL with parameters
new { controller = "Home", action = "Index", id = UrlParameter.Optional } // Parameter defaults
...to another name. I immediately started getting 403.14 locally and remotely. Changing it back to 'id' fixed it.