Null Reference Exception at BuildItemWithCurrentContext(Object obj)


We are using WCSF (February 2008) in our ASP.net Application. After deploying to the production server and test server, Sometimes a page in the application throws a Null Reference Exception.
and when this error comes once then ,every page is throwing the same exception. After restarting the IIS (IISRESET) everything works fine.
Environment: Windows Server 2008 R2, IIS7
Note: We use windows authentication to log into the application. Also we are using Impersonation with the help of DLLImport["Kernal32.dll"].
The exception is like

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.]
Microsoft.Practices.CompositeWeb.WebClientApplication.BuildItemWithCurrentContext(Object obj) +247
Microsoft.Practices.CompositeWeb.Web.UI.Page.OnPreInit(EventArgs e) +62
System.Web.UI.Page.PerformPreInit() +41
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1255
We found an application exception just before this behavior of out application.
The log was
Log Name: Application
Source: Application Error
Date: 4/27/2010 1:43:55 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <computername>
Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e03238, faulting module kernel32.dll, version 6.0.6002.18005, time stamp 0x49e041d1, exception code 0xe053534f, fault offset 0x00000000000176fd, process id 0x%9, application start time 0x%10.
Please anybody tell us what could be the actual cause of this behavior.
Thanks ,


vipinlal wrote May 10, 2010 at 5:11 AM


I'm facing same problem, why there is no reply for this issue ?


wrote Feb 22, 2013 at 12:02 AM