We are using NetAdvantage Version 2009.2.
Recently the page with the webmaskedit controls started showing error as per below. When I reset the IIS on the server it goes away but after a while it comes back.
Can anyone help?
Here is the error message that comes up on the web page:
Server Error in '/bkonline' 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.]
Infragistics.WebUI.Shared.GlobalCssHelper.GetPageContainer(Page page, Boolean create) +383
Infragistics.WebUI.Shared.GlobalCssHelper.OnInit(WebControl control, Page page) +82
Infragistics.WebUI.WebDataInput.WebTextEdit.OnPreRender(EventArgs e) +92
System.Web.UI.Control.PreRenderRecursiveInternal() +80
System.Web.UI.Control.PreRenderRecursiveInternal() +171
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +842
Version Information: Microsoft .NET Framework Version:2.0.50727.4206; ASP.NET Version:2.0.50727.4209
Hello rbhavsar ,
I recommend you installing the latest service release.
Please refer to the below forum threads describing the fix of this issue.
http://news.infragistics.com/forums/p/34249/186321.aspx#186321
http://news.infragistics.com/forums/p/45695/250260.aspx#250260
Let me know if you still experience the behavior after installing the latest SR
If I upgrade to NetAdvantage Select 2010 Vol. 2, will it fix this issue?
Thanks
Raj
Hello Raj,
If your application uses version 10.1/10.2, then those errors should not happen.