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 ...IIS7 & Application Pools - Feels Like Something is Missing...IIS7 & Application Pools - Feels Like Something is Missing...
Previous
 
Next
New Post
7/21/2010 4:12 PM
 
Please look at the attached screenshot... I have .NET 1.1, 2.0, 3.5 and soon 4.0 - why is it that in the pulldown menu for the application pool the only .net framework I can select is 2.0?

Also in the Managed Pipeline column I see that the sites are going between classic and intergrated... what does this mean? does it make a difference? I do not know how to change these items.

Shouldn't all my sites running 5.4+ be using .NET 3.5? Anyone knwo why this is doign this? Any insight sould be greatly appreciated. This is all in an effrot to figure out my email issue with 5.4.4... thank you for the assistance.

 
New Post
7/21/2010 4:57 PM
 

I think it’s rather confusing to refer to the .NET Runtime version, which for .Net 3.5 framework is still Runtime version 2.0.

Let me explain my findings...

 

You can Google for explanations for this but here’s the jist…

 

·         .Net 2.0 Framework -- .Net 2.0 Runtime

·         .Net 3.0 Framework -- .Net 2.0 Runtime

·         .Net 3.5 Framework -- .Net 2.0 Runtime

·         .Net 3.5 Sp1 -- .Net 2.0 Runtime

·         .Net 4.0 Framework -- .Net 4.0 Runtime

 

.NET 3.0 and .NET 3.5 are additions to .NET 2.0, the core runtime is still the same, so you will not see 3.5 in the application pool settings.

 

Since .NET 3.0 and 3.5 built on top of .NET 2.0, so there was no need for those choices. .NET 4.0 is out, it does include an entry for ASP.NET 4.0 as it includes a new runtime.

 

As such, your choices for the application pool in IIS7 include:

 

·         1.1.4322 (.NET 1.1)

·         2.0.50727 (.NET 2.0, 3.0, 3.5)
·         4.0.30319 (.NET 4.0)

I am still confussed about the Managed Pipeline options..... any ideas on why some sites are integrated and otehrs classic?

 
New Post
7/21/2010 5:37 PM
 
integrated (pipeline) mode is a new feature in IIS 7 and later, where ASP.Net processing is built into IIS. this allows much better web site performance, however some old extensions may have difficulties. As a consequence: try to run your site on integrated app pool mode if possible for best performance, switch to classic mode, if you experience issues with components.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/22/2010 3:15 PM
 

Wow… this has been one hack of a week.

 

After applying the .NET 4.0 Framework to all of My DNN 5.4.4 sites… I had no errors that I knew of… but know I am getting a dymanic forms error:

 

 

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: System.Web.UI.HtmlControls.HtmlTableCellCollection must have items of type 'System.Web.UI.HtmlControls.HtmlTableCell'. 'asp:Literal' is of type 'System.Web.UI.WebControls.Literal'. ---> System.Web.HttpParseException: System.Web.UI.HtmlControls.HtmlTableCellCollection must have items of type 'System.Web.UI.HtmlControls.HtmlTableCell'. 'asp:Literal' is of type 'System.Web.UI.WebControls.Literal'. ---> System.Web.HttpParseException: System.Web.UI.HtmlControls.HtmlTableCellCollection must have items of type 'System.Web.UI.HtmlControls.HtmlTableCell'. 'asp:Literal' is of type 'System.Web.UI.WebControls.Literal'. ---> System.Web.HttpException: System.Web.UI.HtmlControls.HtmlTableCellCollection must have items of type 'System.Web.UI.HtmlControls.HtmlTableCell'. 'asp:Literal' is of type 'System.Web.UI.WebControls.Literal'. at System.Web.UI.CollectionBuilder.GetChildControlType(String tagName, IDictionary attribs) at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& childType, Boolean defaultProperty) at System.Web.UI.ControlBuilder.CreateChildBuilder(String filter, String tagName, IDictionary attribs, TemplateParser parser, ControlBuilder parentBuilder, String id, Int32 line, VirtualPath virtualPath, Type& childType, Boolean defaultProperty) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---


 

This is unrelated to the email issues and CPU spikes we have been discussing on these forums... but...

 

The bigger issue is now this – when I applied the .NET 4.0 Application Pool (Integrated) The sites seems to be working fine… after seeing the error above I proceded to switch the Appl;ication Pool back to using 3.5 SP1… that now results in a server error:

 

Server Error in '/' Application.


Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

 

 

   

       

   

 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

 

 

   

       

   

 

 

 


If I turn on error reporting for this – I get the following…

 

Server Error

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

 

If I switch everything back to running the .NET 4.0 Framework and take away the that was added to the web.config file… The site comes right back up no issues.

 

What’s even more strange is that this symptom of the site going down when switching the frameworks is that is only happens if I have a DNN Instance that has 2 or more portals.

 

This is on a Win 2008 Server running IIS7… All patches/hot fixes have been applied… with the exception of KB982519 – this should not affect anything like this…

 

Any ideas? What is your thoughts on the recompile of the DotNetNuke.dll file? See here:

 

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/postid/377864/scope/posts/Default.aspx#377864

Besides the email issue, the CPU issue is causing havoc as well. In your mind - do any of the following make sense?

 

1.       Our Setup is wrong… I don’t believe this as every version of DNN before 5.4.4 was working just fine… Not a problem at all. No changes in IIS7 were made since the upgrades either... everything was smooth running.

2.       It is a bug in DNN… even thought they have not recognized it as one.

3.       It is a bug in .NET 3.5 or 4.0 that is being exploited by DNN 5.4.4 and Microsoft will have to fix?

 

There seems to be no clear answer here?

 
New Post
7/22/2010 5:41 PM
 
Hi James... I am not really sure what the issue is here but I think its affecting other modules as well... For example, a quick search on the error shows it only happens with 4.0 framework and also happens with other modules. For example: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/199/threadid/377019/scope/posts/Default.aspx So far you are the 2nd customer to inform us that after upgrading the framework to 4.0 they receive this error with Dynamic Forms, we also have another customer using Opt In Email and they also have problem. Not sure yet why, I think this will need more research. -Chad
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...IIS7 & Application Pools - Feels Like Something is Missing...IIS7 & Application Pools - Feels Like Something is Missing...


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