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://es.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?
The 2126 contains that fix. Higher versions will contain that fix too.
I cannot seem to find the download for the 2126 hot fix in my 2009v2 download page. I can only see service releases. What do I need to do to get the 2126 version of 2009v2?
The November service release did not include the ASP.NET controls for NetAdvantage for .NET 2009 Volume 2. As Viktor mentions eariler in this thread, the first service release for this version is scheduled for December.
This service release did include the ASP.NET controls for NetAdvantage for .NET 2009 Volume 1 (build 9.1.20091.2126), which includes this fix.
You can keep posted to the Service Relases page of our website for updates to the expected publication dates of our upcoming service releases.
If you're using NetAdvantage for .NET 2009 Volume 2, are encountering this issue, and cannot wait for the December service release, then plase submit a support request to ask for an untested build containing this fix. Mention development issue 24316 so we know which issue you mean; you can also provide a link to this forum thread.
crdl said:Sorry, the confusion on my part stemmed from Viktor's response to Chris:
Viktor's comment is accurate for our NetAdvantage for .NET 2009 Volume 1 ASP.NET controls - builds 9.1.20091.2126 and up include this fix. The "and up" part of this statement does not necessarily include our 2009 Volume 2 controls. This is because build 9.1.20091.2126 was built after the volume release build of 2009 Volume 2 (9.2.20092.1003).
The fix is in place in internal builds, and those internal builds have not yet gone through complete quality testing. That's why we can offer the fix as an "untested build," before it's scheduled for publication in December.
This type of disconnect between the service releases of different volumes only occurs shortly after we publish a new release. If we hadn't published 2009 Volume 2 just a few weeks earlier, we'd have included a service release for this volume as well.
crdl said:Does Infragistics use 2009v2 WebEditors on its website, or do you not use the current version of your own product?
Sorry, the confusion on my part stemmed from Viktor's response to Chris:
"Hi Chris, The 2126 contains that fix. Higher versions will contain that fix too."
Since Chris wrote "..updated our site to Infragistics 2009v2", I inherently thought that Viktor's comment to Chris was in some way related to his problem with 2009v2, but I guess it wasn't...
At this point, we will either be rolling back our code or changing over to Telerik (10+ developer licenses). As either the Infragistic's 'never adequately tested 2009v2' or the 'it can wait until December' approach has just really left us with an unprofessional feeling.
Does Infragistics use 2009v2 WebEditors on its website, or do you not use the current version of your own product? If you are using it, how are you dealing with the multiple IIS resets that the rest of us are having to do on a daily basis?