Recently, I was working with a colleague in a SharePoint 2013 On-Primesis environment to troubleshoot an issue when attempting to use the SQL Report View Web Part and a Content By Search or Search Results Web Part on the same page. To our surprise, the report viewer web part would not work with both web parts on the page.
The page made use of the query string to pass additional context for the Search Results Web Part and the SQL Report Viewer Web Part. When the SQL Report Viewer Web Part was placed on the page by itself, everything worked correctly. However, when either of the search web parts were placed on the page and configured, the report would stop loading. Upon opening developer tools for IE10, the following error was displayed:
SCRIPT5022: 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 ‘ebPartEditing|false|<script type=’text/j’.
This appears to be related to the ASP.Net Update Panel. After a little digging in the web part configuration, we found a way to correct the issue.
Begin by opening the search web part and click on configure query.
The Build Your Query dialog will appear. Go to the Settings page and change the loading behavior to async.
After this change was made, the sql report viewer web part began working properly again.