Portal Engine
Version 3.x > Portal Engine > Ajax Sys.WebForms.PageRequestManagerParserErrorException View modes: 
User avatar
Member
Member
boodapotamus - 5/1/2008 10:54:18 AM
   
Ajax Sys.WebForms.PageRequestManagerParserErrorException
I am using an ajax tabcontainer control with several tabpanels that contain cms repeater controls to list content articles. The non-active tabpanels are loaded "on demand" when the user clicks on the tab to keep the page load size down.

Works great in Firefox, but IE 7 throws the following cllient side error.

Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.
Details: Error parsing near' 1468|updatePanel|plcRoot_'.

There is a lot out there about correcting/avoiding this issue. My question is the correct way to resolve this with Kentico CMS.

Most references seem to always come back to this page.

http://weblogs.asp.net/leftslipper/archive/2007/02/26/sys-webforms-pagerequestmanagerparsererrorexception-what-it-is-and-how-to-avoid-it.aspx

I might also add that the "on demand" loading is triggered by a hidden button within an update panel in the tabpanel. If I move the button outside of the update panel, I do not receive the error, but it causes a full postback which ruins the point of using ajax.

Any thoughts or suggestions?

User avatar
Member
Member
boodapotamus - 5/1/2008 2:41:03 PM
   
RE:Ajax Sys.WebForms.PageRequestManagerParserErrorException
Looking further into this, I tried loading the webpart onto another Kentico site that created and did not receive the error in IE 7.

I have compared the web.config's and even uploaded the dll's from the working site.

Am I correct in thinking this may be a server issue? I believe they are on different servers at my hosting company.

User avatar
Member
Member
boodapotamus - 6/6/2008 1:56:50 PM
   
RE:Ajax Sys.WebForms.PageRequestManagerParserErrorException
Finally solved this after many frustrating weeks and trying everything under the sun. I finally solved it by removing the ~/ from a link I had in a repeater transformation.

However, I now see after reading the 3.1 version history, it was a bug with 3.0. So, another fix would now be upgrading to 3.1.

General: Resolving URL filter damaged AJAX response if the response contained URLs starting with ~/.