(setting up on the ISAPI tab causes the site to not work at all, but it IS
listed under the "Home Directory tab" / Configuration button). Navigating
to the virtual server, we get the text of the iisstart.asp file. (The site
documents are set for default.html and index.html - no mention of
iisstart.asp.) Navigating to a user created asp page (which we know works
fine) causes either the same type of behaviour, or "HTTP 403.1 Forbidden:
Execute Access Forbidden" - and we have checked all the security settings,
reset the permissions, and ensured Script and Execute access was turned
on... This is a weird one, I'm almost tempted to rip out IIS and put in
Apache, but I'd get shot for that.....
Thanks for the tip. Any others?
Shawn
-----Original Message-----
From: McGill, Eric [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 9:50 AM
To: CF-Talk
Subject: RE: IIS not rendering ASP?
First thing I would do is go into IIS control panel and confirm that the
extension *.asp is mapped to asp.dll under the properties for that
particular website. I'm sorry not to be able to tell you which tab it is -
I'm not near a box with IIS running - but I think it is under the
Configuration button, then one of the tabs that is in the next form. If
you're lucky enough for this to be the problem, just add the mapping
there... (Hit Add > Enter ASP in the extension field > Browse to ASP.DLL)
Good luck,
Eric
-----Original Message-----
From: Shawn Grover [mailto:[EMAIL PROTECTED]
A request for an ASP file results in the text of the file being passed to
the client, with no server
side processing.
_____
[ Todays Threads
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
