Hi Fred,
I agree with Bob. The error logs will be very useful for the
trouble-shooting.
Besides, if we create a simple ASP website and deploy it on this IIS, does
it have the same issue? This can eliminate the possibility that legacy ASP
website is causing problem.
I look forward to receiving your test results.
Best Regards,
Thomas Sun
Microsoft Online Partner Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
With newsgroups, MSDN subscribers enjoy unlimited, free support as opposed
to the limited number of phone-based technical support incidents. Complex
issues or server-down situations are not recommended for the newsgroups.
Issues of this nature are best handled working with a Microsoft Support
Engineer using one of your phone-based incidents.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
|
| Fred Chateau wrote:
| > I have one legacy ASP page on my Web site, which has been returning
| > an HTTP 500 status code. I have debug turned on in IIS, but all I get
| > is a blank page. I substituted an older backup of the page, but the
| > same thing happens.
| > Does anyone know of any upgrades in Windows Server 2003 recently,
| > that would make ASP stop running?
|
| You will never figure out how to fix this without discovering the real
error
| message. See:
|
http://www.aspfaq.com/show.asp?id=2109
|
| --
| Microsoft MVP - ASP/ASP.NET - 2004-2007
| Please reply to the newsgroup. This email account is my spam trap so I
| don't check it very often. If you must reply off-line, then remove the
| "NO SPAM"
|
|
|