New IIS Web Server Problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ccountey
    New Member
    • Mar 2008
    • 8

    New IIS Web Server Problem

    Hello,

    We are in the process of moving our company's Intranet onto a dedicated server that was just configured for that sole purpose. The pages are written in asp.net and the server is running .NET 2.0. The web site is running and the Intranet was functional on another IIS server, but when you attempt to navigate to any of the aspx pages, it says that it cannot find the requested page.

    The entire site is located in the inetpub/wwwroot folder of this server, as it was on the previous box. The asp.net page is using AD authentication, is written in VB.net, and the web.config is the same as it was in the previous location.

    Any ideas?

    Thanks!

    Chris
  • kenobewan
    Recognized Expert Specialist
    • Dec 2006
    • 4871

    #2
    Ensure document types has default aspx page, site location is set up the same in IIS, .net framework is installed and create a simple test page. HTH.

    Comment

    • deric
      New Member
      • Dec 2007
      • 92

      #3
      Make sure that the website is already an "Applicatio n".. the option "Scripts and executables" is selected, and that it is using ASP 2.0 (in the ASP tab).
      You can find these three in the property page of the website on the IIS manager.

      Comment

      • ccountey
        New Member
        • Mar 2008
        • 8

        #4
        Originally posted by kenobewan
        Ensure document types has default aspx page, site location is set up the same in IIS, .net framework is installed and create a simple test page. HTH.
        Thanks for your reply. After reviewing the old server I discovered two things that were causing my issue:

        The first was the fact that my IIS was using .NET 1 instead of 2, and the application is written for version 2. For whatever reason, after all updates, I had to install version 2 manually in order to allow it.

        The second issue was that the temp folder in the .NET windows folder did not have the ASPNET account listed as an admin user.

        Thanks again for your reply.

        Comment

        Working...