In the provided code files we have noticed that you actually utilize the ConfigurationManager to extract the new connection string:
String newConn = ConfigurationManager.ConnectionStrings[
Thus our recommendation is to use the reporting build-in support for resolving application configuration (web.config) connection strings. Just set the SqlDataSource ConnectionString to the used connection string name as you have already done
. do you experience any issues if you don't use the ReportConnectionStringManager?
In the provided code files we have noticed that you have put part of the code in a try catch block:
var uriReportSource = (UriReportSource)sourceReportSource;
uriReportSource.Uri = path + uriReportSource.Uri;
var reportInstance = DeserializeReport(uriReportSource);
Do you try to suppress any exceptions?
Up to the error this error may be caused due to the IE add ons issue. Check out the "Internet Explorer has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
MS thread on the topic. Another reason could be just some IE troubles in rendering too big pages. How big is the report you try to render? Have you tried to run the report in Chrome or Firefox?
Additionally we have noticed that you set the reportsource parameters through the report viewer, instead our recommendation is to set the parameters directly to the report source as shown in the following code snippet:
var URI =
URI.Uri = report_key +
var sourceReportSource = URI;
var connectionStringHandler =
var reportSource = connectionStringHandler.UpdateReportSource(sourceReportSource);
.rptViewer.ReportSource = reportSource;
DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.