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

Home All Forums

1
2
3
4
5

Adding module to child portal causes .NET error

1/9/2009 4:26 PM

ETM Penning

Joined: 5/15/2004

Posts: 62

Adding module to child portal causes .NET error Modified By ETM Penning on 1/9/2009 4:27:50 PM

I am running DNN 4.8.1 and added the store module to a child portal and added the module to a page, now I get the following error:

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:

The source code that generated this unhandled exception can only be 
shown when compiled in debug mode. To enable this, please follow one of the 
below steps, then request the URL:

1. Add a "Debug=true" directive at the 
top of the file that generated the error. Example:

  <%@ Page 
Language="C#" Debug="true" %>

or:

2) Add the following section 
to the configuration file of your 
application:

<configuration>
   <system.web>
       <compilation 
debug="true"/>
   </system.web>
</configuration>

Note 
that this second technique will cause all files within a given application to be 
compiled in debug mode. The first technique will cause only that particular file 
to be compiled in debug mode.

Important: Running applications in debug 
mode does incur a memory/performance overhead. You should make sure that an 
application has debugging disabled before deploying into production 
scenario.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Modules.Store.WebControls.Account.Page_Load(Object sender, EventArgs e) +166

[ModuleLoadException: Store settings are not defined.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) +481
   DotNetNuke.Modules.Store.WebControls.Account.Page_Load(Object sender, EventArgs e) +441
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

[PageLoadException: Store settings are not defined.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +376
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +481
   System.Web.UI.TemplateControl.OnError(EventArgs e) +2085460
   System.Web.UI.Page.HandleError(Exception e) +71
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7341
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
   System.Web.UI.Page.ProcessRequest() +86
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

All the other child portals work just fine. What can I do to remove the module from this particular portal to restore it to a working state?

1/13/2009 2:21 PM

ETM Penning

Joined: 5/15/2004

Posts: 62

Re: Adding module to child portal causes .NET error Modified By ETM Penning on 1/13/2009 2:46:48 PM

I removed the module in question from this portal via SQL. This allows the child portal to return to functionality.

1/14/2009 10:21 AM

Gilles Le Pigocher

Joined: 10/11/2003

Posts: 1966

Re: Adding module to child portal causes .NET error Modified By Gilles Le Pigocher on 1/14/2009 10:23:09 AM

Hi,

The Store module version 02.01.00 DO NOT work well on child portal! Please install it on a standard portal or try the last beta 02.01.09!

Please follow the chapter 3 only (PREPARE your Store) in this post to install the Store module. In the next version the exception message has been replaced. Moreover, I think your web.config is not well defined. This is why you receive the big yellow exception screen instead a simple error message in the module. May be you use the debug mode?

Gilles

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.

Page 1 of 1

Adding module to child portal causes .NET 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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

About

New Community Website

Server Error in '/' Application.

Object reference not set to an instance of an object.

ESW Operations, LLC