• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

ASP .NET 2.0 Application Pools Crashing after 1 or 2 pageloads

K

Kila@

Guest
I have bee working with a site using Dotnetnuke for a couple weeks.

For no apparent reason, the Application Pool containing this site (ASP .NET 2.0) just stops running after one or two pageloads.

I tried turning off the default 'stop the application pool after 5 errors' in IIS, yet the error still occurs.

Can this be something Plesk related? I am desperate, already lost 2 days of work because of this.
 
I had the same problem and had to manually move the websites to a different pool in IIS. Then enable the option in Plesk to create a new pool for each website. It will allow you to track errors more efficiently.
 
Thanks for that. The 2 DNN 4.3.4 sites I had we're each in their own pool.

Anyhow, I gave up after losing 2 days of work trying to solve this and just went to an earlier DB backup, and this solved it.

I suspect the guilty party was a DNN site keep-alive module I bought.. seemed like a pretty hacky method to improve performance. Somehow I believe it screwed things up royally.
 
Back
Top