Поделиться через

SSL and SQL Reporting Services 2005

  • Статья

While setting up a Report Server to run with SSL, one of my customers repeatedly got the following error message:

"The underlying connection was closed: Could not establish trust relationship with
remote server."

The interesting thing was that the /Reports folder worked fine, it was just /ReportServer that threw the exception above.

We followed the standard SSL/SSRS troubleshooting steps:

In rsReportServer.Config:

In rsWebApplication.config:

Still, no joy...finally, we checked the cert associated with our Vdirs, and saw that it was created for domain.com versus machine.domain.com. Since we were just testing, we regenerated the cert to reflect machine.domain.com and we were good to go.

Comments

  • Anonymous
    June 07, 2006
    I had the same problem using SelfSSL on a Win2K3 machine and could not figure out what the issue was for a long time. Finally I noticed that my certificate was in the Personal folder and not the Trusted Certificates folder. There was one in there but it did not have the same name.

    Long story short, you have to make sure your certificate is in the Trusted folder and Personal Folder using MMC and they have to be the same certificate with the same name.

  • Anonymous
    November 17, 2006
    The comment has been removed

  • Anonymous
    March 28, 2007
    Hi,Similar to Julio, I also have the ReportServer folder working fine, but the Reports folder is giving me the: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." error.  However, I get it as soon as I try to bring up the page, I am not able to see the list as Julio describes.Also, if I update rsWebApplication.config to include the fqdn assigned to the certificate, I get a configuration error.Finally, I have copied my certificate from the Personal Folder to the trusted folder.Still no dice.Hmmm... ??? Any ideas?

  • Anonymous
    May 03, 2007
    Thanks Russell, our issue was that someone changed the rsWebApplication.config file and missed out the S for https, your notes pointed that out.We are now up and running after 2 days outage.Cheers

  • Anonymous
    November 05, 2007
    we are getting the error message on accessing the reports VD. We have applied a locally genrated cert (simply called TAURUS08 - which happens to be the machine name also ) and applied it through iis to the relevant web site.  We have set the SSL requirement in the config manager with level 3 and cert name of Taurus08  (on applying this gets changed to the web sites ip address !?). We have set the value of UrlRoot   to https://192.168.2.214/reportserver in reportserver.configWe have set <ReportServerUrl>https://192.168.2.214/reportserver</ReportServerUrl> in RSWebApplication.config.Have we missed anything? Any ideas why we still get the error message?cheers steve

  • Anonymous
    November 10, 2008
    anybody managed to get the SSL working on SQL SRS 2005? i'm having a tough one on the Reportshttps://localhost:2444/Reports/Pages/Folder.aspx?ItemPath=%2fMyDemo&ViewMode=Detailbut the reportserver link is ok..

  • Anonymous
    December 22, 2008
    I'm capable of acessing all Reporting Server sites from the RS machine using https://localhost/... but not using the Machine Name neither using the FQDN as it's configured in the RS Conf tool.Any ideas?

  • Anonymous
    January 18, 2009
    The comment has been removed

  • Anonymous
    July 01, 2009
    For me my customer can cannect to my SQL Reporting database with SSL portal and can export data in .pdf, but it doesn't work with an Excel or Word report. Any ideas ? Thanks

  • Anonymous
    April 28, 2011
    @gced - In IE, try going into Tools, Options... Advanced tab, and under Security, and make sure "Do not save encrypted pages to disk" is NOT checked.