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 ...Worker process deadlockingWorker process deadlocking
Previous
 
Next
New Post
1/15/2008 6:14 PM
 

 
This has happened to me three times today:
 
I am running 4.07 on IIS 6 and my users have been experiencing service unavailable errors. The short fast way to get the site up is to reset IIS but the event logs are telling me:
 
Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error: 0x80070005
 
and
 
A process serving application pool 'DNN' exceeded time limits during shut down. The process id was '6080'.
 
DNN is running in its own application pool and the settings are the defaults. I have a limited audience of roughly 2000 users.
 
The following schedules are being run:
 
DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE
 
DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE
 
DotNetNuke.Services.Log.EventLog.PurgeLogBuffer, DOTNETNUKE
 
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
 
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
 
DotNetNuke.Modules.Events.EventNotification, DotNetNuke.Modules.Events
 
And the DNN Event viewer shows nothing but successful logins for the hour proceeding.

Any ideas on how to fix this?

 
New Post
1/15/2008 8:12 PM
 

A few items:

  1. What are the specs of the server this instance of DNN is running on?
  2. Can you upgrade to the latest version (4.8.0)?
  3. When did this start happening? Any changes to the server or DNN app recently?

Regards,

Christopher Koeber


Regards,
Christopher Koeber
 
New Post
1/16/2008 9:43 AM
 

In your host settings, are you writing the event log directly to disk or is it writing to memory then to the database or file?  I had trouble with this because I wasn't writing the log to memory but I had the scheduled PurgeLogBuffer scheduled.  For some reason it didn't like that and you can other topics regarding an issue with the scheduled events causing problems with the portal from 4.7 and up.  If I can find those links I will post them for you.

To fix my issue, my settings are to write log directly to database, and to disable the scheduled PurgeLogBuffer.  I also switched my Scheduled Events to fire off from HTTP-Request to the TImer-Method.  This appeared to help my situation. 

Hope this helps.

Jerry

 

 
New Post
1/16/2008 1:44 PM
 

Christopher wrote

A few items:

  1. What are the specs of the server this instance of DNN is running on?
  2. Can you upgrade to the latest version (4.8.0)?
  3. When did this start happening? Any changes to the server or DNN app recently?

Regards,

Christopher Koeber

it is a Dell PowerEdge 2600, 4 - 2.8Ghz processors, 1GB memory.

I can't use 4.8 because I need AD to work.

No changes were made except in response to this error.  But then the site has only been up since 31 December. 

 
New Post
1/16/2008 1:51 PM
 

Purge your EventLog table. Also take a look at your scheduler and see if the search engine indexer is running too frequently. I have an intranet site and I only re-index once per 24hrs.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Worker process deadlockingWorker process deadlocking


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