I have an ASP.Net 4.0 application in which contains a web form containing a ScriptManager, UpdatePanel and some controls, including a WebDropDown. This form has been in production for some time now with no issues. The app is using 2010.3
I recently tried to add another field to the form (textbox), and after compiling and executing the code on my VS2010 PC when I attempt to post the page back I started getting this error:
"Microsoft.JScript" runtime error: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed."
I have tried removing my changes to the page, but the error still comes up. I even pulled from the production server the same web form in production (aspx, cs and designer files) and replaced the existing files of my project, but I still get the same error.
Testing other web forms in my application using AJAX, they work fine, so I assumed it must be a problem with the specific form.
So I stripped down my page and left only the WebDropDown and the button causing the postback and tested. The problem occurs with the WebDropDown and goes away without it. I went one step further and left the WebDropDown with no data, and the problem did not occur. Loading some dummy data manually in the code behind (as opposed to data from the db) also results in the problem not happening. So my next assumption was that this is a data related issue (hence why the problem did not happen in production).
To test my theory I downloaded the prod database and used it on my machine; the problem occured, so my theory is wrong.
I am running out of ideas, so please if you have ever encountered such an issue I would appreciate some help.
Hello pfendt,If you require I can create you a support ticket and link it to the development issue. This will automatically notify you when the development issue is resolved in new service release. As a temporary solution that i can suggest is to remove your recent Windows Updates.
i have the same issue using 2011.2 (newest service release). is there a way to be notified when there is a hotfix available for this?
Hello Chris,Infragistics are thankfull to you for all the information you have provided to us and all the research you have made. After full windows update I managed to reproduce the issue. I am starting procedure of logging a development issue. I have created a support ticket based on this forum thread with number CAS-81141-L5PNBG. I will update you with development issue number through it till the end of the day.
Nikifor
Were you able to confirm my findings? Have you narrowed down which of the updates is causing the issue? I have been able to re-install the following updates with no problem to the application:
KB2468871
KB2518870
KB2533523
KB2539636
The issue must be caused by either one or both of the other two updates I removed (I unfortunately have not recorded their names).
OK guys
I have uninstalled all Windows Updates pertaining to .Net Client (Framework 4.0) on my machine, downloaded on 4/1/2012 and the problem is solved.
I suggest you do the same as it appears that the problem is with the updates themselves. I don't know how Ig will deal with this issue; perhaps it must also be reported to MS?
I will wait for an update on this.