Hi,
We're having problems with the WebTextEdit on version 8.2.20082.2187, specifically:
Exception information:
Exception type: NullReferenceException
Exception message: 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)
We searched a bit and seems this is a well documented error, but the problem is there doesn't seem to be a service release for 2008.2 where this has been fixed, so our only option seems to upgrade to 2012 since we don't have access 2008.3 or later versions, other than 2012.
Is there an easy way to upgrade from 2008 to 2012? It seems some of the control names or methods have changed.
Please advice us on how we can proceed to overcome this issue.
Thanks.
Best regards,
Alan
Hi Alan,
the latest service release for 8.2 is 2204. I could provide you link for download for it or for any other version that you have purchased. Just let me know what exactly you need.
Thank you
Hi Hristo,
Indeed it is, but i've read 2204 doesn't include the required fix. Could you confirm that for me just in case ?
Thanks,
Please, we need a rather urgent answer on this matter. Asking our customer to restart the AppPool a couple of times a week is not a very elegant solution and users are complaining about it.
Alan,
can you point me where do you find information about this documented error. Do you know what is the bug number? Are you able to isolate this in a small sample, so I could test this with different builds to check if the issue persists. I have opened new support ticket: CAS-92564-TTD2JM .We will continue our discussion through it. Also you could attach a sample to it.
Thanks
Here is a post where they talk extensively about the subject, apparently the only solution is to rollback to an older version (8.2.20082.2177) or upgrade to 8.3 (which we don't have).
http://blogs.infragistics.com/forums/t/34249.aspx
It's not something that happens always, so i don't think testing for the bug will be easy. Imho, you shouldn't need check all the versions, since the guys talking on that post seem to have a clear idea on which versions are corrected and which not.
I'm not happy about downgrading but unless we are granted access to 8.3 there doesn't seem to be another option around.
Please tell us what we can do to fix this problem and not create new ones with the fix.