This topic is locked
[SOLVED]

 IIS7 Page cannot be found

9/17/2009 11:50:55 AM
ASPRunnerPro General questions
L
leonkrn author

Has anybody experienced problem running the page after it has been built?

The page builds successfully via the wizard, Virtual directory is created, but when I try to run the project in browser I am getting page cannot be displayed error. I see that request is being redirected from index.htm to the correct page, but that's where it dies.
I verified that IIS7 is in fact working by removing all the code from the .asp page and replacing it with something like this:
<%

response.write "testing..."

responce.end

%>

C
clig 9/17/2009



Has anybody experienced problem running the page after it has been built?

The page builds successfully via the wizard, Virtual directory is created, but when I try to run the project in browser I am getting page cannot be displayed error. I see that request is being redirected from index.htm to the correct page, but that's where it dies.
I verified that IIS7 is in fact working by removing all the code from the .asp page and replacing it with something like this:
<%

response.write "testing..."

responce.end

%>


Good article running ASP on IIS 7: http://www.alexthissen.nl/blogs/main/archive/2008/02/18/running-classic-asp-on-iis-7.aspx

L
leonkrn author 9/17/2009

I just figured this out by having to create a simple page connecting to database and running it under IIS.
Apparently, windows authentication was the issue. When connecting to SQL Server have to use SQL Authentication, not Windows authentication.

There are ways to go around it, but it's not recommend from the security perspective.
http://www.experts-exchange.com/Databases/Q_20800659.html



Has anybody experienced problem running the page after it has been built?

The page builds successfully via the wizard, Virtual directory is created, but when I try to run the project in browser I am getting page cannot be displayed error. I see that request is being redirected from index.htm to the correct page, but that's where it dies.
I verified that IIS7 is in fact working by removing all the code from the .asp page and replacing it with something like this:
<%

response.write "testing..."

responce.end

%>