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

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Upgrade failure - 6.2RC Server errorUpgrade failure - 6.2RC Server error
Previous
 
Next
New Post
5/24/2012 7:49 AM
 
Brief Description of Issue - (fresh install vs. upgrade, browsers specific, user role, etc):
On upgrading a dnn 6.1.5 copy of a live site on LocalHost to 6.2RC I get the following error: (The upgrade reports succesfully completion but on the same page as "Upgrade Complete Click Here To Access Your Site" is the following)

Server Error in '/dotnetnuke' Application.

Session state has created a session id, but cannot save it because the response was already flushed by the application.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Session state has created a session id, but cannot save it because the response was already flushed by the application.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Session state has created a session id, but cannot save it because the response was already flushed by the application.] System.Web.SessionState.SessionIDManager.SaveSessionID(HttpContext context, String id, Boolean& redirected, Boolean& cookieAdded) +3691295 System.Web.SessionState.SessionStateModule.DelayedGetSessionId() +199 System.Web.SessionState.SessionStateModule.ReleaseStateGetSessionID() +25 System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +874 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80



If I access the site it appears without any CSS formatting.

i have tried restoring the site and three or four attempts to upgrade all have failed.

What have i missed.

Thanks

Paul

 
New Post
5/24/2012 7:59 AM
 
we dont use session's anywhere in core code, but asp.net will create a session cookie by default - if a response.flush occurs after this is created this error can occur. We typically only do flush's when an exception has occurred to output an error message - you could try disabling sessions altogether to see if that shows an exception (http://support.microsoft.com/kb/306996) - i would also recommend setting log4net to ALL to see if that captures any issues -http://www.dotnetnuke.com/Resources/Wiki/Page/log4net-In-DotNetNuke.aspx

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/25/2012 8:20 PM
 
Thanks for the reply Cathal.
I have I think turned off Session state. and changed to ALL in the log file.
While i no longer recieve the session state error, on accssing the site I still have no CSS and can not long on as the popup sign up does not appear.
I am using Nukeville skin Morpheus and am beginning to wonder if there is a clash here.
Paul
 
New Post
5/25/2012 8:37 PM
 

I should have added

The log file shows warnings fora number of entries similar to: (these are menu items)

Dotnetnuke.Localization.provider - missing localization key.//occassional voices .... threadculture:en-AU userlan:

These are the only errors that I can see.

 

Paul

 
New Post
5/25/2012 8:42 PM
 
thanks for the update - dont worry about the localization issues, if a localization key is missing it defaults to the text with minimal overhead (we fix these in the core, but enabling ALL can reveal them in skins/modules). As to the issue, I dont know morpheus - you could try deleting it from relevant portal skins folder (check the bin folder as well in case it has an assembly) - the site will fall back to the default skin defined in dotnetnuke.config's skinningdefaults node, which by default is darkknight - if you dont have darkknight installed, change it to one that you did

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Upgrade failure - 6.2RC Server errorUpgrade failure - 6.2RC Server error


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