Previous Next

Thread: HTTP 404, when trying to reach ASP.net 2.0 in IIS v6

Last post 08-27-2008 6:04 AM by steve schofield. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 08-26-2008, 3:55 PM

    • Nina9
    • Not Ranked
    • Joined on 08-26-2008, 7:21 PM
    • Posts 1

    HTTP 404, when trying to reach ASP.net 2.0 in IIS v6

    I have installed a Live chat application which requires Asp.net 2.0 ( I am going to host it in house) and since all of my other websites use Asp.net 1.0, I upgraded .NET framework 1.0 to 2.0; but when I installed the chat software I am not able to reach its default page. I realize that in IIS 6.0 It is necessary that for each version of .net framework use a separate Application Pool so I created a new application pool for this Livechat website in IIS and assigned the website to it. I also made sure that in IIS Web Service Extensions, Asp.net 2.0 and 1.0 are allowed. I made sure that there is no app.offline.htm file exists in the file directory... This is the error that I get when I try to reach live chat default page: " The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /default.aspx " Please advise me...

  • 08-27-2008, 6:04 AM In reply to

    Re: HTTP 404, when trying to reach ASP.net 2.0 in IIS v6

    Do you see anything in the Application Event log?  Asp.net 2.0 applications will record unhandled exceptions in the app event log.   I would verify the IIS site / vdir is pointing to the correct location.   A 404 either means the page is not found (obviously), something is mis-configured in the application.  Or you are running something  like URLScan that is blocking the requests and sending back a 404 status code.  I would also check the IIS Logs to see if anything stands out.   Also, check with the vendor if there is some special configuration for their application.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield

    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
Page 1 of 1 (2 items)
Page view counter