I have a DNN install that, for the most part, has been very stable.  However, lately I am getting constant errors which cause DNN's application pool to crash, which brings down the entire website.  This has now become a dire problem as my whole everything is now unstable.  Here is what my Event Viewer has logged (3 entries per crash)

FIRST ENTRY:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{73B25FFD-F501-437B-8B11-7F0DE383964F}
 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20).  This security permission can be modified using the Component Services administrative tool.

SECOND ENTRY (0 seconds later):

Application popup: JIT Debugging : JIT Debugging failed with the following error: Access is denied.
JIT Debugging was initiated by the user account 'NT AUTHORITY\NETWORK SERVICE'.

THIRD ENTRY (few seconds later):

A process serving application pool 'Autonuke.com' terminated unexpectedly. The process id was '3356'. The process exit code was '0x1'.

Some things I have checked:

All my permissions with NETWORK SERVICE are set correctly.  My website usually runs fine for an hour, then it dies out.  There are no filesystem errors, I did a intense scan.  I am running DNN 3.2.0.

Any ideas please?  I very much appreciate your help!!!

I've asked around with some people here at work and concensus seems to be that IIS 6.0 sucks.  :) 

From what I can tell the real problem is the third error

A process serving application pool 'Autonuke.com' terminated unexpectedly. The process id was '3356'. The process exit code was '0x1'.
 Unfortunatly it's a very very generic error.  I've kind of tracked it down to two things though.  If you are running the IIS server on a box that is also a domain controler the permissions need to be changed for Network service user.  But in that case I don't think it would ever have worked.  The second is more interesting to me!  All the other times it seems to have something to do with database access, either drivers or or other database issues. 

So what I'm thinking is that you are having SQL problems that are interfering with the dnn application and causing it to die unexpectedly.  This error gets thrown while the web app dies and then the network services user tries to open the JIT debugger but can't.  Get rid of the application dying problem and you won't have the JIT and permission errors. :)

So looks like we need to figure out the SQL server problem first and hope that fixes the IIS problem also. 

You are running IIS and SQL Server on different systems right?

I was just looking at a couple of other threads I've been reading.  I'm kind of wondering if you are not getting bitten by the datacache.getcache bug.  There are also a few fixes that you are missing between 3.2.0 and the current release 3.2.2.[/quote]

Hook me up with those fixes please!  What files need to be modded and what should I change? 

:)