• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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