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 ...Upgrade Error 8.0.4Upgrade Error 8.0.4
Previous
 
Next
New Post
1/30/2017 12:44 PM
 
Any update on this? i just got the same error when upgrading from 7 to 9.0.1.142. The upgrade had NO errors.


Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

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:


[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Web.Mvc.MvcHttpModule.SuppressXFrameOptionsHeaderIfPresentInConfig() +248
DotNetNuke.Web.Mvc.MvcHttpModule.Init(HttpApplication context) +12
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +534
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +339
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +296

[HttpException (0x80004005): Object reference not set to an instance of an object.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9946132
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +90
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +261

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1087.0
 
New Post
1/30/2017 4:49 PM
 
Take a look at the second post on this thread. It may help with your issue.  I haven't diagnosed the underlying problem so it's not really a fix.
 
New Post
1/30/2017 9:09 PM
 
Just took a look at the defect and it's been closed due to unable to duplicate. I can duplicate the issue with 8.0.4 and 9.0.0. Currently stuck on 8.0.3 and cannot go anywhere. Even tried adding the below from the defect notes:


<dependentAssembly>
<assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="0.0.0.0-5.1.0.0" newVersion="5.1.0.0" />

</dependentAssembly>

 

Made no difference, Updated a local instance to 9.0 without issue. Would be nice to know the cause as I have few more sites but don't want to attempt to update if it's just going to fail. Like the originally poster if I replace the DLL from 8.0.3 work fine.



 
New Post
1/30/2017 9:48 PM
 
I think I found the fix. At least I did for my one site that I was having issues with.

Looking at the source code for the module. (MvcHttpModule.cs) found the reference code.

private static void SuppressXFrameOptionsHeaderIfPresentInConfig()
{
var xmlConfig = Config.Load();
var xmlCustomHeaders =
xmlConfig.SelectSingleNode("configuration/system.webServer/httpProtocol/customHeaders") ??
xmlConfig.SelectSingleNode("configuration/location/system.webServer/httpProtocol/customHeaders");

Looked in my Web.config file customHeaders and the below:

 

<httpProtocol>
    <customHeaders>
   <clear />
   </customHeaders>
</httpProtocol>

 

Compared to a Local instance and noted it was different:

 <httpProtocol>
      <customHeaders>
        <remove name="X-Powered-By" />
      </customHeaders>
</httpProtocol>   

I proceed to change my web.config to remove the  <clear />which is a valid setting:

 

<httpProtocol>
    <customHeaders>
    </customHeaders>
</httpProtocol>

 

Attempted my upgrade to 8.0.4.266 without issue. It would be nice if someone else could confirm the this fixes their issue also. Along with DNNMonster, or Sebastian can you update the defect notes? I do not have access to.


 
New Post
1/30/2017 10:18 PM
 
Just confirmed on another instance that was failing. Remove the "Clear" option worked.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Upgrade Error 8.0.4Upgrade Error 8.0.4


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