David
Sun Nov 09 22:40:32 CST 2003
You need to see the actual error code to know what to do. This is done in
two ways:
1. Disable IE's "Show Friendly HTTP Errors" so that you see the actual error
code
2. Look in the web logs for the error code that ASP records for that page
Once you determine the actual error code, then we can try to resolve that
issue. You should reset all the other configurations you've done (like
parent paths and buffering) back to the original setting because the
defaults values are more secure.
The right way to do all this is to get all information about the problem and
then do the minimum steps necessary to resolve the exact issue. Arbitrarily
tweaking settings "until something works" is a bad idea -- you may have gone
down the wrong path initially, either in security, functionality, or
reliability.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"spt" <anonymous@discussions.microsoft.com> wrote in message
news:088c01c3a5ff$9f2c4cf0$a401280a@phx.gbl...
I built a website use asp pages on my new 2003 server. I
enabled asp because by default it is disabled... What
else needs to be done to enable IIS 6 to serve the
pages. Currently I'm getting error 500 internal server
error. I also enabled parent paths and buffering.
If anyone has instructions on what needs to be turned on
to serve a website that is not static pages that would be
great!
Regards,
Scott