Friday, June 22, 2012

Interprise Suite Ecommerce: System.ArgumentNullException: Value cannot be null

Version: Interprise Suite 6.x


The following error is generated when viewing a page in ISE.

Server Error in 'xxx' Application.
Value cannot be null.
Parameter name: child
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.ArgumentNullException: Value cannot be null.
Parameter name: child

Source Error:

Line 260:                    this.Controls.Clear();
Line 261:                    // set the template user control to be owned by this page:
Line 262:                    this.Controls.Add(m_Template);
Line 263:
Line 264:                    //register the ScriptManager before loading controls or the ComponentArt menu won't work with AJAX pages

Source File: d:\Program Files (x86)\Interprise Solutions\HipsAndCurves\ISE\Web\App_Code\SkinBase.cs    Line: 262

Stack Trace:

[ArgumentNullException: Value cannot be null.
Parameter name: child]
   System.Web.UI.ControlCollection.Add(Control child) +8828139
   InterpriseSuiteEcommerce.SkinBase.OnPreInit(EventArgs e) in d:\Program Files (x86)\Interprise Solutions\HipsAndCurves\ISE\Web\App_Code\SkinBase.cs:262
   System.Web.UI.Page.PerformPreInit() +31
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +328

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


Typically, it points to a problem with the skin template file e.g. template.ascx.  Run the page with a default (out-of-the-box) template.  Typically, the page will load which confirms that it’s a problem with the customized template file.  Look for functionality on the template file that is missing e.g. missing custom supporting file in the bin folder.

It can also be caused by a user control on the template page that has a compilation (or other error).  Look for user controls in the template file with a squiggly line.

No comments:

Post a Comment