I still need to run classic ASP pages at home from time to time. Me having migrated every single machine at home to Windows Vista presents a slight problem as getting classic ASP pages running under IIS 7.0 is far from obvious.
Right off the bat you'll need to enable error messages on IIS. IIS 7.0 introduces a concept which reminds me of friendly HTTP errors in Internet Explorer. basically you need to turn this off to see the actual error message. I was lucky enough to find a person called Mike Plate who encountered the same issue and wrote a post about it.
Also if you need to use the OLEDB provider to do database access to Access (heh) you need to check out this knowledge base article: Error message when you request an ASP page that connects to an Access database in IIS 7.0: "Microsoft JET Database Engine error '80004005'".
Mr. Legacy strikes again!
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.