Quantcast
Channel: Classic ASP
Viewing all articles
Browse latest Browse all 488

ASP unresponsive and not reporting a meaningful error

$
0
0

We have a combination of ASPX and classic ASP on a site we have been maintaining for years.

A few days ago after tweaking web.config and restarting IIS, my development site has stopped responding to ASP pages and I am unable to locate meaningful errors indicating what is wrong.

Login is thru an ASPX page but when it transfers to a feature on a ASP page, network traffic shows the POST with state Pending.  After several minutes it stops waiting and shows status Aborted, and the page shows: This page can't be displayed, while the event log shows that the app pool worker process was recycled "because the worker process reached its allowed processing time limit."

Event log for IIS-Configuration shows a number of warnings and errors for C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\web.config

  • Warning: Unable to find schema for config section 'system.serviceModel/serviceHostingEnvironment'. This section will be ignored.
  • Warning: Unable to find schema for config section 'system.xaml.hosting/httpHandlers'. This section will be ignored.
  • Error: An error has occured: Unrecognized element 'providerOption'

and a bunch of others.  Will this be causing ASP processing to fail?

Where is the best guide for tracing what is going on, or can I enable detailed logging for IIS or ASP?


Viewing all articles
Browse latest Browse all 488

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>