Object reference not set to an instance of an object error.

[ngill]

Hi -- I was wondering if anyone could assist me with this error that I am receiving for a particular store.
http://kimarketplace.com

The error in the error log is as follows:
Message: An error has occured at http://www.kimarketplace.com/Default.aspx
Debug data: Exception of type 'System.Web.HttpUnhandledException' was thrown.; Object reference not set to an instance of an object.

When I actually pull up the app.log, the reoccurring error that appears is as follows:

Code: Select all

ERROR 2010-08-20 05:39:13,571 103344140ms Object                 a                  - An error has occured at http://www.kimarketplace.com/Default.aspx
System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at ConLib_BasketTotalSummary.Page_PreRender(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnPreRender(EventArgs e)
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   --- End of inner exception stack trace ---
   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.ProcessRequestWithNoAssert(HttpContext context)
   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)

Now, here is a little insight about this site. This is 1 of 4 stores created with all the same conlib and scriplet files. The following sites all use the same code base and share files, with an exception to the actual graphics and css files themselves.

http://kimarketplace.com (site with errors)
http://marketplace.cedarpoint.com
http://marketplace.dorneypark.com
http://marketplace.knotts.com

Granted, each site has their own categories and is tailored to their particular brand/park. What I can't figure out is why 1 of the 4 sites is having this issue. The three sites (cedarpoint, dorneypark, and knotts) were set up at a later date than the kimarketplace. CP, DP, and knotts are running version 7.0.4 of able commerce while kimarketplace is running version 7.0.3.

On the kimarketplace site (as well as the other stores) - a simple breakdown in the layout is as follows: Header, sidebar, main content, footer. All the pages (home, checkout, interior) share the same header, sidebar, and footer. The only difference from the home page to the interior pages is that the home scriptlet has static html for the "grid" as well as a reference to bring in the default "featured products" from the conlib. Since this error is only occurring on the "/Default.aspx", I am led to believe that home content is causing the problem. Nevertheless, even with all home content disabled, the error is still popping up in the error log every time someone loads the landing page.

In addition, I have customized the login.aspx (which is referenced in the top left corner) of the side bar. Even disabling that customization still will not prevent the error from occurring.

Also, the default.aspx is still in it's default state and has not been customized.

I have even ran a compare on all customized files to make sure that there were no difference in the customizations -- in which no differences were found.

Any suggestions from anyone? Could this be an issue between 7.0.4 and 7.0.3 ? Any help would be much appreciated.

Thanks,

Nick

[mikek]

Hi Nick,

What is the site configuration in IIS? Do you have separate application pool for each site or all sites are shearing the same AppPool? Also do you share any code between all sites or each site
is running under its own physical folder setup as separate application in IIS?

[ngill]

Michael,

All of these sites are hosted at a dedicated AbleCommerce host, awcs.net, and we do not have access to the server settings. However, if you think that is the issue we can put in a support ticket to the host to get more information or suggest a resolution on their end.

Nick

[ngill]

I hate to bump this post, but I have still not been able to find a solution to this issue and was wondering if anyone else had some advice on the issue?

Thanks in advance,

Nick

[foodsleuth]

I don't have any help but I'm not sure if this is related but we're getting tons of errors in the log file once we upgraded to 7.05 -- we never had any before. It is almost always bot activity.

[triplw]

I upgraded to 7.0.5 yesterday and everything looked great...until tonight. Then the site crashed and I'm getting the same error:
Exception of type 'System.Web.HttpUnhandledException' was thrown.; Object reference not set to an instance of an object.

I noticed that right before the crash some graphics were missing on the Admin panel. I also had 1 error message a few hours earlier about the ComponentArt.dll. I read somewhere on this forum where someone had display issues after they upgraded and they thought the problem was with the new ComponentArt.dll. They said they uploaded the old version and it fixed their problem.

So in desperation to get my site up I uploaded the ComponentArt.dll from the previous version. Now the site is running again. I'm holding my breath to see if the issue is resolved.

Anyone else have some insight on this?