• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 800
  • Last Modified:

asp.net getting HTTP Error 404.15 - Not Found

When running a web application from the root directory of the web server, everything works well. When trying to publish the web site to a virtual directory I get the HTTP Error 404.15 - Not Found.HTTP-Error-404.15.png
0
Edwin Bowles
Asked:
Edwin Bowles
  • 3
1 Solution
 
Edwin BowlesAuthor Commented:
When the attached is published to the root directory of a web server, everything works fine. When it is published to a virtual directory I get the error screen displayed earlier.
Default.aspx
Default.aspx.cs
LogOn.aspx
LogOn.aspx.cs
Web.config
0
 
Manoj PatilSr. Software EngineerCommented:
Hey check below steps

    Excluded all the items under the "Account" folder except Login.aspx
    Excluded IdentityConfig and Startup.Auth under the "App_Start" folder
    Excluded IdentityModels under the "Models" folder
    Excluded "Startup" under the "root" folder of the application
    Commented out all the code under "Page_Load" and "LogIn" inside the Login.aspx code file
    Commented out code with "OpenAuthProviders" in the Login.aspx markup

    Added the following key to the "appSettings" section inside the web.config file

    < add key="owin:AutomaticAppStartup" value="false" />

Reference URL : http://stackoverflow.com/questions/24495585/http-error-404-15-the-request-filtering-module-is-configured-to-deny-a-request-w
0
 
Edwin BowlesAuthor Commented:
I was able to resolve the problem in the original code by replacing all redirects with the FormsAuthentication.RedirectFromLoginPage(sys_user_session.userName, true); statement. After this change everything started working fine.
0
 
Edwin BowlesAuthor Commented:
The person that originally wrote the code tried to take control of the Authentication process. This seemed to work OK when the user published the Authentication code into the root directory. As soon as you published to a different folder and a web folder , converted to a web application, it would no longer work. I replaced the Response.Redirects in the Master page and the content pages to FormsAuthentication.RedirectFromLoginPage(sys_user_session.userName, true);. Everything seemed to start working.
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now