[Local Mode RDLC][VS 2017] New versions of ReportViewer and Report Designer.

Question

In November, 30 2016 it was released the new Report Viewer for VS 2017 :

https://blogs.msdn.microsoft.com/sqlrsteamblog/2016/11/30/report-viewer-2016-control-update-now-available/

In February, 28 2017 it was released the Report Designer for VS 2017 that gives the ability to edit the rdlc files, something that was not possible:

https://marketplace.visualstudio.com/items?itemName=SqlReportingServices.MicrosoftRdlcReportDesignerforVisualStudio-18001

Until I updated the Report Viewer to the last version available from Nuget I could run the report in my website and edit it in VS 2017.

My test website is using iisexpress at Localhost:43556 and has a simple default.aspx with a reportviewer loading a local rdlc.

After the update to the last version of the reportviewer I started to get this error :

Server Error in '/' Application.No connection could be made because the target machine actively refused it 127.0.0.1:80Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:80Source Error:An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:[SocketException (0x274d): No connection could be made because the target machine actively refused it 127.0.0.1:80] System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +185 System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) +506[WebException: Unable to connect to the remote server] Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods() +192 Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname) +51 Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ValidateConnection() +85 Microsoft.Reporting.WebForms.SoapReportExecutionService.GetServerVersion() +41 Microsoft.Reporting.WebForms.ServerReport.GetServerVersion() +54 Microsoft.Reporting.WebForms.ReportViewerClientScript.SetViewerInfo(ReportViewer viewer, String reportAreaId, String promptAreaRowId, String docMapAreaId, String fixedTableId, String topLevelUpdatePanelId, String docMapUpdatePanelId, String promptSplitterId, String docMapSplitterId, String docMapHeaderOverflowId, String directionCacheId, String browserModeCacheId, ClientPrintInfo clientPrintInfo) +1926 Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e) +2746 System.Web.UI.Control.PreRenderRecursiveInternal() +88 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4775

I can understand that this should be some kind of callback that is beeing made and not finding the endpoint so I changed the IISexpress port to port 80 to see if there is something badly hard coded in the reportviewer. I receive this error now :

Server Error in '/' Application.The request failed with HTTP status 404: Not Found.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Net.WebException: The request failed with HTTP status 404: Not Found.Source Error:An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:[WebException: The request failed with HTTP status 404: Not Found.] Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods() +192 Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname) +51 Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ValidateConnection() +39[MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.] Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.MissingEndpointException.ThrowIfEndpointMissing(WebException e) +92 Microsoft.Reporting.WebForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ValidateConnection() +80 Microsoft.Reporting.WebForms.SoapReportExecutionService.GetServerVersion() +41 Microsoft.Reporting.WebForms.ServerReport.GetServerVersion() +54 Microsoft.Reporting.WebForms.ReportViewerClientScript.SetViewerInfo(ReportViewer viewer, String reportAreaId, String promptAreaRowId, String docMapAreaId, String fixedTableId, String topLevelUpdatePanelId, String docMapUpdatePanelId, String promptSplitterId, String docMapSplitterId, String docMapHeaderOverflowId, String directionCacheId, String browserModeCacheId, ClientPrintInfo clientPrintInfo) +1926 Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e) +2746 System.Web.UI.Control.PreRenderRecursiveInternal() +88 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Control.PreRenderRecursiveInternal() +160 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4775

Can anyone use the last versions of ReportViewer and Report Designer in VS 2017 with success ?

Thanks

Pedro Ruivo

---

Portugal

Answer 1

Hi Pedro, can you share a sample of the .aspx file where you are using the Report Viewer Control?

Answer 2

This is just a guess, but the error indicates there is a problem connecting to the report server. Double check if you are using a local or server mode report. If it's server mode, then ensure you have permissions to access the server from your client (if using windows auth, ensure you aren't trying to NTLM double-hop without Kerberos). Also that you're report server is SQL 2008 or later.

---

Microsoft SQL Server Reporting Services

Answer 3

Hi Pedro, can you share a sample of the .aspx file where you are using the Report Viewer Control?

If you want I can send the whole project for you to test it.. it's a POC I made in an Azure VM with the VS2017 RC Template. It's a nice contained project with objectDatasource instead of DB connections...

Send-me a private message with an email and I'll send it to you.

Thank's for the reply.

Answer 4

This is just a guess, but the error indicates there is a problem connecting to the report server. Double check if you are using a local or server mode report. If it's server mode, then ensure you have permissions to access the server from your client (if using windows auth, ensure you aren't trying to NTLM double-hop without Kerberos). Also that you're report server is SQL 2008 or later.

---

Microsoft SQL Server Reporting Services

I'm using Local mode only, and I don't even connecting to DB, I'm using ObjectDataSource feeded with a dummy List<T> of a model I created. The dumbest of the examples :) . The same code just runs if I downgrade the Reportviewer to the previous RC version from Nuget...

Answer 5

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="RDLC.Sample.Default" %>
<%@ Register assembly="Microsoft.ReportViewer.WebForms, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" namespace="Microsoft.Reporting.WebForms" tagprefix="rsweb" %>
 
<!DOCTYPE html>
 
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title></title>
</head>
<body>
    <form id="form1" runat="server">
        <div>
            <asp:scriptmanager runat="server"></asp:scriptmanager>
            <asp:ObjectDataSource ID="EntityDataSource1" runat="server" TypeName="RDLC.Sample.Models.Person" SelectMethod="GetDummyData"></asp:ObjectDataSource>
             <rsweb:ReportViewer ID="ReportViewer1" runat="server" ProcessingMode="Local" AsyncRendering="true" SizeToReportContent="true">
                <LocalReport ReportPath="Sample.rdlc" EnableHyperlinks="true">
                    <DataSources>
                        <rsweb:ReportDataSource DataSourceId="EntityDataSource1" Name="SampleDataset" />
                    </DataSources>
                </LocalReport>
               
            </rsweb:ReportViewer>
        </div>
    </form>
</body>
</html>

Answer 6

Can confirm there is an issue in the latest update to the Viewer Control (140.337.80) when running in LocalMode. The team will get a fix out.

Answer 7

An updated build with a fix for the LocalMode issue has just been published to Nuget - https://www.nuget.org/packages/Microsoft.ReportingServices.ReportViewerControl.Webforms/140.340.80