none
ReportViewer ...A connection attempt failed because the connected party did not properly respond RRS feed

  • Question

  • ReportViewer1.ServerReport.ReportServerCredentials = rptCredentials;

    ReportViewer1.ServerReport.ReportPath = rptPath;
    ReportViewer1.ServerReport.Refresh();

    I have this simple code written, which works fine. But it takes more than 20 secs to load the report. So to track down the reason for this delay, I installed Fiddler (third party tool which generates the trace of all the requests) and i found one request  /reportserver/ReportExecution2005.asmx taking longer time....in fact its throwing an error

    [Fiddler] Connection to myreportserver.com failed.<BR>Exception Text: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xxx.xxx:xx

    SOAPAction: "http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices/ListSecureMethods"


    Here I don't understand why the reportviewer is calling this method. And even thought its failing report is getting displayed.

    Note: I haven't added web reference (ReportExecution2005.asmx) in the webcode.

    Any thoughts?

    Thanks in advance!
    Tuesday, November 4, 2008 12:45 AM

Answers

  • ListSecureMethods is called on the reporting services execution endpoint so that the viewer can determine which SOAP methods require the use of SSL.  When you specify the url of the report server, you an specify it as http or https.  If you specify it as https, the viewer will only connect to the report server using SSL.  But if you specify http, the viewer will still use SSL if the report server is configured to require it.

    I'm not sure this is the issue, but I wonder if you are specifying the url using http but your report server is configured to block connections on port 80.  In that case, the viewer may be timing out or failing on that request and then switching to and succeeding with SSL on port 443.  If that is the case, then the fix it to explicitly pass in a https url so that the viewer doesn't even try port 80.

    • Marked as answer by Aniruddha555 Thursday, November 6, 2008 3:27 PM
    Wednesday, November 5, 2008 2:07 PM
    Moderator

All replies

  • ListSecureMethods is called on the reporting services execution endpoint so that the viewer can determine which SOAP methods require the use of SSL.  When you specify the url of the report server, you an specify it as http or https.  If you specify it as https, the viewer will only connect to the report server using SSL.  But if you specify http, the viewer will still use SSL if the report server is configured to require it.

    I'm not sure this is the issue, but I wonder if you are specifying the url using http but your report server is configured to block connections on port 80.  In that case, the viewer may be timing out or failing on that request and then switching to and succeeding with SSL on port 443.  If that is the case, then the fix it to explicitly pass in a https url so that the viewer doesn't even try port 80.

    • Marked as answer by Aniruddha555 Thursday, November 6, 2008 3:27 PM
    Wednesday, November 5, 2008 2:07 PM
    Moderator
  • Thank you very much, Brian!

    You are right, it works fine with https.

    Thursday, November 6, 2008 3:27 PM