Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke 4.8.1 crashing the IIS?DotNetNuke 4.8.1 crashing the IIS?
Previous
 
Next
New Post
4/25/2008 8:09 AM
 

Hi all

We are having 20 installations of DotNetNuke 4.8.1 on a Windows2003 machine and sometimes the IIS crasches ...not often but soemtimes and the eventviewer doesn't say anything else but it was a .Net 2.0.50727.832 problem .... where should I fault seek first ... this happens rarely but I'd like to sort it out beforehand .... is this a problem that could be casued by a DNN module compiled for .Net 1.1 but running in .Net 2 application pool ? But shouldn't the IIS crash emediately then?

/Johan

 
New Post
4/25/2008 9:36 AM
 

Do you have 20 different physical installations (20 DB's)?  Or 20 portals using a common DB?

If you have 20 unique installations, does each have it's own application pool?

Please elaborate on how you have the (IIS) server configured.



 
New Post
4/25/2008 10:10 AM
 

Thanks for your quick reply ... We have 20 different DB's and 20 different DotNetnuke folders 4.8.1 but they are all connected to the sam application pool .Net2.0

/Johan

 
New Post
4/25/2008 2:48 PM
 

Each instance should have its own application pool. I recommend creating new application pools (preferably using unique identities) for each one of your DNN instances as well as any other web apps you have running. At the very least, this way you'll be able to isolate which application is causing you the issue. Furthermore, this is just a good security practice.

HTH



 
New Post
4/26/2008 4:07 PM
 

Definitely split application pools.  And make sure you have resources for all your installations, RAM, etc.  Depending on the IIS version you can use IISDebug or the Crash/Hang tool.  Or in IIS 7 you can use failed request tracing.  Check www.iis.net for help with IIS.

Jeff

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke 4.8.1 crashing the IIS?DotNetNuke 4.8.1 crashing the IIS?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out