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 ...Site no longer works right after 4.0.5.5 installSite no longer works right after 4.0.5.5 install
Previous
 
Next
New Post
8/1/2007 5:12 PM
 

When a user changes the Link Type on the accouncements module to Page the page will refresh but when it returns the value is still NONE.  The same issue occurs when I goto Host settings and change the icon bar to or from classic/iconbar.  When I add a new page it says object reference not set to an instance of an object. Adding a new module just refreshes the page without any errors.   Trying to update textresults in no changes, basically any action does not save. 

I can restart IIS and occasionally it will work for a few minutes but then everything comes to a halt again.    I upgraded to the latest version on July 26th and it was an upgrade from 4.5.3  Everything seemed to go fine and the site worked after that upgrade but now this is happening. 

After looking through the event log it shows that my attempt to update the host settings page resulted in another object no set to an instance of an object.  It pointed to two files, one site settings in the admin portal folder then host settings in the admin host folder.  After referencing the vb file it seems to be pointing to the line that retrieves the settings hash table.  The below code is in C# but i have not altered any core files, the  original is still in Visual Basic

Hashtable settings = DotNetNuke.Entities.Portals.PortalSettings.GetSiteSettings(0);

I tried running this line of code from within another page and it seems to return a list of data which included 18 items.That makes me believe that the function and the sql side of things seems to be working. 

 Additionally I added some code that would return the portal ID that was used when I click update.  It shows 0 which is correct. 

I'm totally stumped, if anyone can help me i'd greatly appreciate it.

 
New Post
8/1/2007 5:25 PM
 

Here's a common event in my event log file, maybe this will make it easier to track down this info.

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/1/2007 10:19:12 AM
Event time (UTC): 8/1/2007 5:19:12 PM
Event ID: 1234
Event sequence: 2436
Event occurrence: 12
Event detail code: 0
Application information:
Application domain: xxxx
Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\DotNetNuke\
Machine name: COMPUTERNAME
Process information:
Process ID: ccc
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: HttpException
Exception message: Cannot redirect after HTTP headers have been sent.
Request information:
Request URL: http://www.wsysa.com/Default.aspx?TabId=103
Request path: /Default.aspx
User host address: xxx.xxx.xxx.xxx
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: at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)
at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL)
at System.Web.UI.TemplateControl.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.default_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 
New Post
8/6/2007 7:33 PM
 

This problem is still going strong, am i the only one?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site no longer works right after 4.0.5.5 installSite no longer works right after 4.0.5.5 install


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