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.
The service releases for versions 8.3 and 9.1 with that fix are already available for few days. The 9.1 should be have build 9.1.20091.2126 (or higher). The schedule for updates can be found athttps://ko.infragistics.com/support
I am a bit confused because you stated that the fix for the exceptioning issue was added to the build after the 2126 service release. Is this the case or does 2126 contain the fix?
Hi,
We have used 2009.2 in one of our live projects and we are getting the same error.
I am wondering if Infragistics technical team can indicate, when a patch will available to overcome this problem.
Looking forward to a early response
thanks
ayrus said:I am wondering if Infragistics technical team can indicate, when a patch will available to overcome this problem.
A fix for this issue for NetAdvantage for .NET 2009 Volume 2 is coming in the December service release. See the Service Releases page for information on timing.
If you are unable to wait for the service release and are willing to take an untested build, please see this post for more information on how to request one.
We have a very large government customer who experienced this issue. We are going to upgrade the the fixed version. However I have been asked to verify it in the code. The Problem and the Fix. Can you tell me what caused the problem and show me what the fix is.
Thanks Gary
Hi Viktor,
I have the same problem and wanted to know if you can send the files you mention and to replace or if you have other solution, because i have reset IIS every day or two day max. My e-mail is ivmh2005@gmail.com, ivmh_2002@hotmail.com.
Thought it was a mistake in my code, but reading about the subject I can see is an error of Infragistics, you can help me ASAP on this problem.
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).
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.
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
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.