Products

Solutions

Resources

Partners

Community

About

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 ...DNN 6.2.6 Site Won't Come UpDNN 6.2.6 Site Won't Come Up
Previous
 
Next
New Post
1/27/2013 1:53 AM
 

A DNN 6.2.6 site running on .NET 4.

The site consistently times out. I had been slow before when it was running under .net 3.5, then I upgraded and now it times out most oftern.

The performance settings are:
Page State Persistance: Page
Module Cache Provider: File
Cache setting: Moderate
Authenticated Cacheability: NoCache

The site is not pinging the server CPU.
Its in its own App Pool in IIS 6.0

It is rather large and has been upgraded from 5.6.3 as DNN upgraded.

Any suggestions on how to get the site moving would be apprecitated.

Thanks

 
New Post
1/27/2013 2:21 AM
 
Stan,

what happens exactly? Are there any errors logged (also in the Windows event viewer)? Do you have to do something (eg. restart or recycle the AppPool) before it is online again, or does it come back by itself?

You're running Windoes 2003 - 32 or 64bit? Is it a virtual machine? How much RAM is in the machine? Is the SQL Server running on the same machine?

Best wishes
Michael

Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
1/27/2013 4:09 PM
 

Michael,

This is on a virtual 32 bit webserver, Windows2003, with 2 GB Ram. This is one of 30+ DNN sites running on both .net 3.5 and .net 4.
The SQL 2005 is on its own dedicated server. This is the only site in the App Pool and recycling it doesn't seem to make much difference.

Other sites, pre DNN 6.2.6 run much better.

The servers event log reports :
Event Type: Warning
Event Source: ASP.NET 4.0.30319.0
Event Category: Web Event
Event ID: 1309
Date:  1/27/2013
Time:  12:45:27 AM
User:  N/A
Computer: ABC-WEB-VM
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 1/27/2013 12:45:27 AM
Event time (UTC): 1/27/2013 6:45:27 AM
Event ID: 209da8780b0c423ea273e34af3e0b87d
Event sequence: 18
Event occurrence: 4
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/58456976/Root-1-130037418812788750
    Trust level: Full
    Application Virtual Path: /
    Application Path: C:\clients\MySite\
    Machine name: ABC-WEB-VM  
Process information:
    Process ID: 5976
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE  
Exception information:
    Exception type: HttpException
    Exception message: Request timed out.  
Request information:
    Request URL: http://mysitecom/Default.aspx
    Request path: /Default.aspx
    User host address: 64.171.22.99
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 7
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace: 
 

The sites Event Log: I wasn't able to log into the site, but queried the eventlog table:

System.Threading.ThreadAbortException: Thread was being aborted.     at Microsoft.Win32.Win32Native.GetFileAttributesEx(String name, Int32 fileInfoLevel, WIN32_FILE_ATTRIBUTE_DATA& lpFileInformation)     at System.IO.File.FillAttributeInfo(String path, WIN32_FILE_ATTRIBUTE_DATA& data, Boolean tryagain, Boolean returnErrorOnNotFound)     at System.IO.File.InternalExists(String path)     at System.IO.File.Exists(String path)     at DotNetNuke.Web.UI.Utilities.ApplySkin(Control telerikControl, String fallBackEmbeddedSkinName, String controlName, String webControlSkinSubFolderName)

Thanks for your help.    
 
New Post
1/28/2013 2:19 AM
 

Stan,

as newer DNN versions need more resources, it could be that 2 GB of RAM is a bit too less - did you check if there are same tasks/services causing a high processor or memory load (TaskManager, RessourceMonitor)?

Recycling an AppPool is a bit different from stopping and starting it. Did you try this, does it make a difference (at least for a while?

How responsiive is the SQL Server on the other machine? Didi you do any performance tests there?

I guess you have access to the database server, so you could have a look how much records the eventlog table holds. If this is very much, try to truncate it. If there is only one portal for this database, you can use

TRUNCATE TABLE {databaseOwner}{objectQualifier}EventLog

by replacing {databaseOwner} and {objectQualifier} by it's appropriate values, eg. dnn62.dnn_EventLog or dbo.EventLog.

If there are more Portals and you wish to keep the eventlog entries from the other tables, you should use

DELETE FROM {databaseOwner}{objectQualifier}EventLog
WHERE LogPortalID = portalID

Replace as above, and portalID by the actual PortalID.

Best wishes
Michael


Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
1/28/2013 8:19 AM
 

Michael,

I believe it's the need by DNN to use more resources and 2 GB is just not enough.

Looking at Task Manager its always application pools that are bring the CPU to 100%. I do recycle, not stop.start, when that occurs. I have the app pools set to recycle after 120 minutes or if they use 800 mb of memory. In most cases I have multiple websites in a single app pool.

The SQL server seems very responsive and there have been no errors in its event log.

Thanks

Stan

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.2.6 Site Won't Come UpDNN 6.2.6 Site Won't Come Up


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