Sys.WebForms.PageRequestManagerParserErrorException problem after hosting

Posted by Gopal_nivas under ASP.NET on 11/7/2011 | Points: 10 | Views : 2422 | Status : [Member] | Replies : 2
hi ..

i am using adrotator i order to display images one by one.
for adrotator concept i am using update panel and timer control.

after hosting this i received the alert message like below.

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 'ZE5hbWU9NjUmSUQ9Mjcm'.


then i comment the update panel means it works fine for me. so how to handle this issue.
need ur suggestions with examples

regards
gopal.s




Responses

Posted by: Umeshdwivedi on: 11/8/2011 [Member] Starter | Points: 25

Up
0
Down
Hallo
you can check your ajax dll
and no more issue
this type error always happen on sever
coze configuration is deffer
so i suggest you that ajax application not working on server
you can ask to your web provider


Latest Technology Trainer
And Part time software consultant

Gopal_nivas, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Umeshdwivedi on: 11/8/2011 [Member] Starter | Points: 25

Up
0
Down
What's a PageRequestManagerParserErrorException?


The UpdatePanel control uses asynchronous postbacks to control which parts of the page get rendered. It does this using a whole bunch of JavaScript on the client and a whole bunch of C# on the server. Asynchronous postbacks are exactly the same as regular postbacks except for one important thing: the rendering. Asynchronous postbacks go through the same life cycles events as regular pages (this is a question I get asked often). Only at the render phase do things get different. We capture the rendering of only the UpdatePanels that we care about and send it down to the client using a special format. In addition, we send out some other pieces of information, such as the page title, hidden form values, the form action URL, and lists of scripts.

As I mentioned, this is rendered out using a special format that the JavaScript on the client can understand. If you mess with the format by rendering things outside of the render phase of the page, the format will be messed up. Perhaps the most common way to do this is to call Response.Write() during Page's Load event, which is something that page developers often do for debugging purposes.

The client ends up receiving a blob of data that it can't parse, so it gives up and shows you a PageRequestManagerParserErrorException. Here's an example of what the message contains:
---------------------------
Microsoft Internet Explorer
---------------------------
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 'Hello, World!106|upd'.
---------------------------
OK
---------------------------

If you ask me, this error message is not all that bad. After all, I'm the one that made it :) The details indicate what was being parsed when it decided to give up. You can see the part of the text from my Response.Write(), and immediately after that is part of the special format I keep mentioning.


Latest Technology Trainer
And Part time software consultant

Gopal_nivas, if this helps please login to Mark As Answer. | Alert Moderator

Login to post response