I have deployed an ASP.NET 2.0 application that is using neadvantage 7.1 for ASP.NET. Sometimes randomly, when a page that contains webdatechooser control is loaded, the following error occurs:
Normal 0 false false false EN-US X-NONE AR-SA MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:Arial; mso-bidi-theme-font:minor-bidi;}
Object reference not set to an instance of an object. Stack Trace: at Infragistics.WebUI.Shared.WebAgent.GetPageControl(Control control) at Infragistics.WebUI.Shared.WebAgent.get_EnableAppStylingResolved() at Infragistics.WebUI.WebSchedule.WebDateChooser.get_IsAppStyling() at Infragistics.WebUI.WebSchedule.WebDateChooser.OnPreRender(EventArgs e) 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.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)
The user can go further unless the IIS server is restarted. As you can see, all the method call that are involved in the error are from Infragistics and .net framework. Any clue on how to solve the problem?
Note: Sometimes the error appears for other infragistics control such as ultrawebgrid etc.
I've seen a very similar exception reported to Developer Support recently by another customer. It seems to affect a number of different controls (the other customer is using WebMenu, WebChart, and WebTab), and seems to require an IIS restart once it occurs. We're still looking into the matter ourselves with all due thoroughness.
If you haven't already done so, I suggest that you submit a support request. I recognize that this may be difficult to dependably reproduce in a sample project, but if you're able to create one, it would likely help us to resolve this issue much more quickly. Even if you can't reproduce the behavior, any additional information you can provide as to what seems to be the cause will be helpful.
has there been any resolution do this issue?
Not sure if this is a coquincedence or not, but we had added an IE 6 fix for png files when the problem started showing up (see below). Once I removed that the problem went away and we've been error free for at least one day now.
* html img,
* html .png {
position:relative;
behavior: BLOCKED EXPRESSION;
}
Part of my message got clipped. Trying again...
I am having the exact same issue... would love to hear if Infragistics has produced a fix or workaround.
robhudson2,
If you haven't already done so, I recommend that you submit a support request, as I mentioned earlier in the thread. I suggest this for two reasons.
First, if the cause of your issue is the same as what's already been reported, we can link your case to an existing development issue (21987) that was raised based on cases logged by others earlier in this thread. We've applied a fix for this issue internally, which we expect to be included in the next service release we publish, assuming that it passes our testing process.
Second, we can investigate to determine whether your issue is the same as what has already been reported. If it's a different issue, then this upcoming service release may not help you, and we'll need to research your issue in more detail to bring it to a resolution.
I'm experiencing the same issue and just submitted a ticket. Wow I hope they fix this soon I've had it happen in two different applications now.