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

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedError installing DNN moduleError installing DNN module
Previous
 
Next
New Post
4/14/2014 2:08 PM
 

Hello,

I've created a DNN module which compiles in release mode generating the installation and source zip files.

But when I come to install it, I get an 'Object reference not set to an instance of an object.' error, please see details below. This occurs on clicking the Next button immediately after the zip file has been selected in the Extensions wizard.

Can anyone please offer any suggestions on the best approach to resolve this issue?

Best Regards,

Steve

 

Server Error in '/' Application.

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.Entities.Urls.AdvancedUrlRewriter.Handle404OrException(FriendlyUrlSettings settings, HttpContext context, Exception ex, UrlAction result, Boolean transfer, Boolean showDebug) +45
   DotNetNuke.Entities.Urls.AdvancedUrlRewriter.RewriteUrl(Object sender, EventArgs e) +295
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +136
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69



Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446

 

 
New Post
4/15/2014 12:57 PM
 

I've made a discovery which I think could be relevant to this problem.

When I attempt to access the file management system via the following url:

http://dnnstage.me/Host/File-Manageme...

I get the error message below.

From the message, I don't understand why this file is being accessed:

c:\inetpub\wwwroot\dnn_07_01_02\DesktopModules\DigitalAssets\View.ascx

In IIS I created a virtual directory dnn_07_02_02 and a binding for dnnstage.me to point to that directory.

So why would it access dnn_07_01_02? I do have dnn_07_01_02 as a virtual directory as well.

But how would the dnn installation accessed via dnnstage.me even know that 07_01_02 existed?

I created the installations separately both from the dnn installation from codeplex. I've checked my IIS configuration, so I'm mystified.

Can anyone give me a pointer for what to check?



Best Regards,

Steve

Error: File Management is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: c:\inetpub\wwwroot\dnn_07_01_02\DesktopModules\DigitalAssets\View.ascx(269): error CS0246: The type or namespace name 'FileSizeFormatProvider' could not be found (are you missing a using directive or an assembly reference?) ---> System.Web.HttpCompileException: c:\inetpub\wwwroot\dnn_07_01_02\DesktopModules\DigitalAssets\View.ascx(269): error CS0246: The type or namespace name 'FileSizeFormatProvider' could not be found (are you missing a using directive or an assembly reference?) 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.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

 

 
New Post
4/16/2014 7:29 AM
 
Hello,

To the first issue of the failed installation, I found the problem.

I had forgotten to delete a directory containing images of around 135Mb which made the installation file rather large :-)

Installs perfectly now :-)

Not sure about the second part though.

Steve
 
New Post
4/16/2014 8:08 AM
 
Sometimes the bindings in IIS can cause this. Something similar happened to me a few nights ago.

I would make sure your test site uses port 80 and remove the other virtual directory if you don't need it and see if that helps.

Mark
 
New Post
4/28/2014 1:35 PM
 

Hi Mark,

Thank you for your reply.

Both virtual directories use port 80. I would like to have both as I want a dev and staging environment.

Best Regards,

Steve

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedError installing DNN moduleError installing DNN module


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