We have been using Infragistics 2006v1 for a few years without any issues. We recently renewed and updated our site to Infragistics 2009v2. After a day or so of uptime on our production server we start getting random exceptions with the infragistics controls. The exact exception that start it off is below. The only way to fix this is to do an IIS reset and then it will be stable for a day or so.
** Exception : Object reference not set to an instance of an object.
** Stack Trace : at
Infragistics.WebUI.Shared.GlobalCssHelper.GetPageContainer(Page page, Boolean create)
at Infragistics.WebUI.Shared.GlobalCssHelper.OnInit(WebControl
control, Page page)
at Infragistics.WebUI.WebDataInput.WebTextEdit.OnPreRender(EventArgs
e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Hi Chris,
Thank you for a report.That issue was introduced around 7-8 months ago due to work around memory leaks on server which occurred in some specific applications. Around 2 months ago, that was reviewed and current version uses different logic. Particularly the GlobalCssHelper class which was used in earlier versions before AppStyling, was deprecated and removed from logic.
Please get latest service release, it should not have that issue.
I checked source codes and found that that fix did not go to the RELEASE build yet. I hope, that will be available in coming service releases.
Hi Viktor
Thanks for your detailed response. However, since we have the source code could you point to the area that actually fixed the problem?
Gary
Viktor,
Can you please verify that this was fixed in version?
Version=9.2.20092.2099
We also can't reproduce in test in order to validate, but are having the issue in prod. Thanks.
Hi,
The fix for that issue was done on 10/13/2009 and it was applied for all versions. So, it was available in any built released after November/December of 2009. The history in tfs shows that the version 9.2.20092.2099 was built on 04/13/2010, so that contains fix.
When you say all version, does 2008 Vol 2 (8.2.20082.2204) also have the fix?
I have a client with that version who is experiencing the problem.
Erik
Hi Eric,
Thanks for question.I checked history of files used to build 2008 Vol 2 and found that last service release was built few weeks before that fix. So, it does not contain that.
Versions 2008.3, 2009.x and 2010.x are fixed.
The version 8.2.20082.2177 and earlier do not have change which triggered that IIS issue. So, you may consider to upgrade to 8.3 and up or return to 8.2.20082.2177.
Thanks for the quick reponse.
We will probably take the opportunity to just upgrade to 2010 Vol 2. (maybe just downgrade temporarily to create a quick patch).