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 ...DNN 4.3.4 and App Pool ProblemDNN 4.3.4 and App Pool Problem
Previous
 
Next
New Post
10/6/2006 2:11 PM
 
I have a couple of sites that are running 4.3.4 on a shared server service (crystaltech) that use shared app pools..... both sites go down every 2 days or so (go down definition:  front page seems to come up everytime but sub pages get the server error) ---- their support said the sites were drawing too much memory and thus the app pools are continuously having to be manually cycled.  Their support then moved these 2 sites to their own app pool for testing purposes and the same issue occurs.  They are saying its one of our modules causing the problem but i don't really have any non-core modules in use that are common across the 2 sites.  Can anyone help... our clients are getting pretty mad at us and are getting leary of DNN.   Thanks.
 
New Post
10/10/2006 12:23 AM
 
I just started trying to get 4.3.5 working for one of my clients at crystaltech as well. 

In my case the site dies after about several page loads on the administrator side.  If I hit refresh a couple times then it usually, but not always comes right back.  If that doesn't work, just going to the sites home page starts it over.

The error message that is being thrown is:
[SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]
System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) +0
System.Security.CodeAccessPermission.Demand() +59
System.IO.Path.GetFullPath(String path) +98
System.Web.Util.FileUtil.IsSuspiciousPhysicalPath(String physicalPath, Boolean& pathTooLong) +50
System.Web.Util.FileUtil.IsSuspiciousPhysicalPath(String physicalPath) +23
System.Web.CachedPathData.GetConfigPathData(String configPath) +465
System.Web.CachedPathData.GetConfigPathData(String configPath) +243
System.Web.CachedPathData.GetConfigPathData(String configPath) +243
System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath, Boolean permitPathsOutsideApp) +132
System.Web.HttpContext.GetFilePathData() +27
System.Web.HttpContext.GetConfigurationPathData() +26
System.Web.Configuration.HttpConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String configKey) +36
System.Configuration.ConfigurationManager.GetSection(String sectionName) +107
System.Configuration.ConfigurationManager.get_AppSettings() +29
System.Web.Configuration.WebConfigurationManager.get_AppSettings() +5
DotNetNuke.Common.Globals.GetDomainName(HttpRequest Request) +60
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +4051
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

(BTW, I can recreate the above error message just by going to the Host Settings page and clicking update)

I've also noticed that the site permissions aren't sticking.   If I use CrystalTech's control panel to reset the file permissions, then the site starts working again.  I've turned off caching, upgrade checks, etc.

Honestly, I've already turned one new client away from using DNN because of this garbage; but I have to get this client working.
 
New Post
10/10/2006 4:41 AM
 
"our clients are getting pretty mad at us and are getting leary of DNN. "

Honestly, I hear this a lot, and I've experienced it with my own sites. I have ongoing problems with DNN, but DNN is not really any more trouble than say designing your OWN portal software and maintaining it (and I have). After following my 3 rules, my problems have at least stabilized to where I can reliably deploy DNN sites to paying clients. I have a DNN site that has not had any crashes or downtime for 8 months now (other than a couple Windows Updates reboots).

1. Run DNN in its own app pool - I've seen server errors when I share app pools, so I don't share them! Easy fix!
2. Use a dedicated server (not shared, not virtual) - so you can troubleshoot DNN sites
3. One DNN install per client - DNN has a tendency to "mess up" especially when upgrading to new versions. I probably have a dozen unanswered posts on here

If you can't follow these rules then you shouldn't really be using DNN for paying clients, IMO. This is just my experience lately (as in this past year). Shared hosting has been great for HTML and small ASP/ASP.NET web apps, but I just think DNN requires too much resources to be effective on shared hosting.

You really need to see the server's app errors to see what's going on. You might check to see if your Schedules are running ok. File Synch and Logs will do a number on DNN websites. Modules CAN cause your DNN site to too.

Sorry for the long mumblings but I got up too early this morning and decided to post to wake my brain up ;)

Jason Honingford - Web & Software Developer
www.PortVista.com
 
New Post
10/10/2006 5:02 AM
 
Jason - can you clarify your recommendation about One DNN install per client and Run DNN in its own app pool? If you have multiple DNN installs (i.e. multiple sites in IIS) do you give each one a separate app pool containing only that one DNN install, or do you share an app pool between several DNN installs? Not sure when you say Run DNN in its own app pool if you mean don't put other ASP.NET apps in the pool with DNN, or don't put more than one DNN in one pool.
 
New Post
10/10/2006 5:31 AM
 
Each IIS website gets its own app pool. I use default app pool settings and haven't seen any problems. I'm not sure why you'd want to share the app pool anyway, unless you're trying to make money by cramming a bunch of websites on one server. You can fit quite a few separate DNN installs on their own app pool on one server with only 1GB memory, I'd say at least 50 websites easily, with SQL Server on the same server.

Jason Honingford - Web & Software Developer
www.PortVista.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 4.3.4 and App Pool ProblemDNN 4.3.4 and App Pool Problem


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