SQL Server: SSRS 2008- Underlying connection was closed – could not establish trust relationship for SSL/TLS

SSRS 2008- Underlying connection was closed – could not establish trust relationship for SSL/TLS…

Hi Friends,

In my previous blog, I wrote about SSRS 2005 “unable to connect to remote server” issue and the fix for it. You can find it here;

So here is the next issue with SQL Server 2008 Reporting Services. “The underlying connection was closed: could not establish trust relationship for the SSL/TLS secure channel.”

This error popped up after a fresh, successful installation, when I tried to access the report manager at http://localhost/Reports_SQL2K8

1_SQL_Server_SSRS2008_Underlying_connection_was_closed_could_not_establish_trust_relationship

Well, this one was not so difficult to figure out. Since the error clearly said that it has something to do with SSL. I fired up Reporting Services Configuration Manager. And clicked on “Report Manager URL” section, and this is what I saw:

2_SQL_Server_SSRS2008_Underlying_connection_was_closed_could_not_establish_trust_relationship

   

 

If you observe, https:// has been configured. But I did not do it. May be, the default configuration. I clicked on Advanced. See the screenshot below:

3_SQL_Server_SSRS2008_Underlying_connection_was_closed_could_not_establish_trust_relationship

If you observe, default SSL certificate for both IPv4 & IPv6 was configured which was causing the problem. This default configuration was done by SSRS 2008 installation. I suspect, this was due to Windows Server 2008 R2 network services or any other role/feature I enabled before SSRS installation. Now, I did not need SSL configuration on my personal laptop and/or this configuration had to be fixed. I removed both the configurations and clicked OK. But it still not done. The same configuration has to be removed from “Web Service URL” section in SSRS configuration – exactly in the same way.

That’s it. You are done. The Report Manager was now showing up, successfully.

 

 

   

About Amit Bansal

Amit Bansal is always brainstorming around SQL Server. Despite working with SQL since 1997, he is amazed that he keeps learning new things every single day. SQL Server is AB's first love, and his wife does not mind that. He tries to share as much and spreads the SQL goodness. Internals and Performance Tuning excites him, and also gives him sleepless nights at times, simply because he is not a genius, but quite a hard worker and does not give up. It has been a long and exciting journey since 1997, you can read here: http://sqlmaestros.com/amit-bansal/ He is on Twitter: https://www.twitter.com/A_Bansal

View all posts by Amit Bansal →

6 Comments on “SQL Server: SSRS 2008- Underlying connection was closed – could not establish trust relationship for SSL/TLS”

  1. Now that was informative, i was not aware that SSRS 2008 by default enables SSL.

    Thanks for adding this to my knowledge.

    Sarabpreet Singh

  2. Dear Amit Sir,

    I am new to MSBI, and currently working on SSRS for 1.5 year.

    But Recently I am facing a problem during SSRS deployment and unable to retrive report manager via reports virtual directory showing The underlying connection was closed: The connection was closed unexpectedly,it was running before.

    My sql server version is 2008. And problem occured after network Admin department instal the Visual studio 2012 and Kaspersky internet security in my system. I tried a lot to solve this pblm, still same problem occur again and again, even after un instal VS2012

    Kindly help in this problem

  3. I’m seeing the above error “The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.” in SQL Server 2014 Reporting Services.
    When I remove the SSL Identities from both the Web Service URL and the Report Manager URL, I get another error:
    Unable to connect to the remote server
    I’ve tried to allow the programs through the Windows Firewall, but it was already allowed.
    Any suggestions?

Leave a Reply

Your email address will not be published.