After SSRS2012 migration - reports get parsing error from time to time RRS feed

  • Question

  • Hi,

    After migration of ~2K reports from 2008 to 2012 (SQL+Web) I am getting this errors from time time on various reports.
    Any idea what can cause it?


    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 '<!DOCTYPE HTML PUBLI'.

    Sunday, April 17, 2016 9:15 AM

All replies

  • Hi Ruth,

    Please follow the below thread


    Please Dont forget to mark as answer and Helpful Post. It helps others to find relevant posts to the same question. Milan Das

    Sunday, April 17, 2016 11:06 AM
  • Thank you for a quick answer.
    web.config and 
    rsreportserver.config were updated per article.

    Users still get this err after the change and rs service recycle.          <o:p></o:p>

    The fix was set in web.config under:
    D:\Program Files\Microsoft SQL Server\MSRS11.SQL01\Reporting Services\ReportManager<o:p></o:p>

    - Need other web.config be set? <o:p></o:p>

    - Can this error pop with no connection to ms11-100 patch?<o:p></o:p>

    - I see no corresponding error in event viewer at the time of the fail (under Application) - any idea where to look for log?

    -Its a virtual machine, w2k8r2 16G mem. 



    Monday, April 18, 2016 6:26 AM
  • And a new understanding: the ie client gets the error, but it doesnt exists when he opens another ie\chrome session. It shift the issue from server to client, isn't it? 
    Monday, April 18, 2016 6:56 AM
  • Hi Ruth,

    Thank you for your question.  

    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.  

    Thank you for your understanding and support. 

    Xi jin.

    Wednesday, April 27, 2016 8:38 AM
  • As you get no issues shown up when open that report in another browser, it indicates that there is nothing wrong with that report or your report server. How about you delete IE history/session and close all IE tab and try again?


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, April 27, 2016 9:16 AM