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 ...Urgent Help Please - ASP.NET not working (Deadlock?)Urgent Help Please - ASP.NET not working (Deadlock?)
Previous
 
Next
New Post
5/24/2008 1:06 AM
 

This just happened last night and I'm running in circles trying to fix it.

It seems everything is working on the server except DNN/ASP.NET.  Websites all completely down that use this (others/static work though).

I am using Windows Server 2003, IIS6 and ASP.NET 1, 2 & 3.5.

The only errors I've been able to see in the Event log are:

Application Warning

Source: W3SVC-WP
Description: ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

System Warning

Source: W3SVC-WP
Description: A process serving application pool 'DefaultAppPool' exceeded time limits during shut down. The process id was '2712'.

 

I've seen http://support.microsoft.com/kb/821268 and applied the recommendations - but it's made no obvious difference.

Starting to tear my hair out on this.  Any help at all would be great.

Thanks

 
New Post
5/24/2008 1:21 AM
 

Sounds like you have a module or process that isn't running properly and using up all of your threads. 

The first thing I would do is check your task items in the DNN Scheduler.  Disable the scheduler then look at the history for each item.  If you see an item that is constantly failing or taking too long to run, that could be the problem.  Also check the DNN Event Log for any errors.  I would imagine you should see some errors there as well.

If that doesn't help, then I would start moving sites to separate app pools to try and isolate the problem.


Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
5/24/2008 2:12 AM
 

Thanks for replying so quickly Will.

The problem is it isn't running at all. I don't get any error screen... websites just sit and wait to load.  So I can't get into the Scheduler - let alone anything much at all (within DNN itself).

I've just managed to get the webmail working now, which uses ASP.NET 1... so I suppose that's a start.

So you can see what "isn't" happening - one domain is www.hnicholsons.co.uk

Thanks

 
New Post
5/24/2008 2:37 AM
 

In that case, I would probably open IIS Manager and stop all websites.  Then restart IIS.  This will bring IIS backup and then allow you turn each site back on one at a time.

Start one site and try to access it.  If you can get to it, look for the items that I mentioned before.  If everything looks good then move on to the next site. 

If you still can't get to the sites then you probably need to completely disable the scheduler.  Restart IIS again.  Then bring the sites backup.  You can disable the scheduler from the web.config.  Find the schedule provider section and add enabled=false to the following line...

 add name="DNNScheduler" type="DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler, DotNetNuke.DNNScheduler" providerPath="~\Providers\SchedulingProviders\DNNScheduler\" debug="false" maxThreads="1" enabled="false"

 

 

 If you are still having problems getting into the sites after you try the above, then I would create a new AppPool and trying adding one site at a time.

I have also seen instances where the metabase has become corrupt which would cause the site to never respond.  Any easy fix for that problem is to just create a new site under IIS.

 


Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
New Post
5/24/2008 3:13 AM
 

Hi Will

I've tried all of that. I hadn't done the schedule disable before but I did it and had no luck there either.

I've restarted IIS, also DNS - first things I could think of. Also restarted the server but no good either.

I've moved websites around in the AppPools, Disabled them (only have 3 - 2 x DNN Instances and 1 x static) and tested... deleted them and added them again. Just not having any luck at all.  5 hrs going through every thing I can and the best I've done is get the webmail running again (ASP.NET 1).

Is there possibly a way to test ASP.NET aside from the websites themselves?  Running out of ideas.

Thanks

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Urgent Help Please - ASP.NET not working (Deadlock?)Urgent Help Please - ASP.NET not working (Deadlock?)


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