Windows 7 / IIS 7 / Classic ASP not working

I have some old classic asp scripts. They used to work on my 2003/IIS 6 server. But on my Vista/IIS 7 and now Windows 7 Ultimate/IIS 7 server the asp pages don't work.

I did what they said here: Deploying a Classic ASP Server (IIS 7) (Microsoft TechNet).

I enabled those 3 features in IIS 7 but that just went from getting 404 to 500 error.

From serverfault $pageUsers[$entry.posts[0].author].name

• Here are a couple of links which include how to run classic asp on IIS7.

  Tips for Classic ASP developers on IIS7

  Running classic ASP on IIS 7

  Hope this helps you some.

  Chris : I don't have access to an IIS7 server at the moment, but on IIS6, a site will have an earth icon, and then you should have your folder icons underneath those. An icon of a cog is an application. ASP applications do not need to be an 'application' per say. Its just folder based since it does not need to be precomplied and run in the asp.net app pool. Go through your IIS manager and review what you have. You may just need to remove the folders and start over from the begining. Good luck!
  From Chris

• Lucenut - just wondering have you got a fix for the above yet? Exact same is happening me and I'm banging my head trying to get it sorted! So much for upgrading to Win 7 eh? :/

  Not a happy developer in Ireland

  splattne : yes, I'm following all the answers and updates. I just checked my virtual Windows 7 machine. Works on my machine. check your app pool setting (classic pipeline mode). btw: the order of the answers is randomized. please try to comment the answers instead of adding new answers to the question.
  From $pageUsers[$post.author].name

• A question: does a simple asp script run or did you try existing pages with includes?

  <% Response.Write "Hello, world!" %>
  

  Since you're getting a 500 server error now, could be a sign that something is wrong with your script. Maybe you forgot to enable the Windows Feature (WWW / Application Development Features) "Server-Side Includes"?

  ---

  It could be a security issue of the application pool account as well. I found this article: loadUserProfile and IIS7 - understanding temporary directory failures. It could be a similar problem.

  From splattne

• thats the exact code I tried on a test page called index.asp splattne

  Then i removed all the asp code from it (leaving it essentially just html but still with a .asp extension - and it still would not run the page at all

  It runs .html .htm etc pages ok - just not ASP

  and I have installed the ASP components into IIS7.5 and all of the other tips given in those articles

  very frustrated...

  From $pageUsers[$post.author].name

• If you've followed all the guides in the answers, and there's nothing of use in the application or system log, and you are still stuck, you might want to turn on failed request tracing.

  From jlupolt

• ive tried that also jlubolt but to no avail - it doesn't seem to write a report to the failed requests folder even when I turn on the facility on the particular web folder in inetput :(

  still scratching moi head

  From $pageUsers[$post.author].name

• Hi guys! Any update on this. I just got Windows 7 and installed visual interdev and I keep getting "unable to contact web server http://localhost"

  I already enabled asp in IIS Manager and tried to follow the two links above but still to no avail. Would greatly appreciate if you could share your solution/s.

  Thanks

  From caloy

• Hi Caloy we have the same issue

  i got this from: forums.iis.net/t/1167295.aspx

  "It is recommended that you install Visual InterDev on a Windows platform it supports (Windows XP and so on). VID is no longer supported by Microsoft, so running it on Windows 7 can be problematic.

  http://support.microsoft.com/lifecycle/?p1=3022

  Install it and develop on an old versions of Windows, and then deploy your site to IIS 7. That's a better approach, as classic ASP is still supported by new versions of Windows/IIS. "

  From ydreys