Link to home
Start Free TrialLog in
Avatar of phytomer
phytomer

asked on

Error connecting to report server - Could not establish trust relationship for the ssl/tls secure channel. (system.web.services)

Performed and inplace upgrade from 2000 to 2005.  Everything works fine except for the report server.

In Microsoft sql server manager, I select connect then reporting services.  From here I can browse the report server, but while trying to connect I get the following error:

Cannot connect to "server\data"
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. (System.Web.Services)
The remot certificate is invalid according to the validation procedure.

I ran the "Reporting Services Configuration" tool... if that helps.

Avatar of igor_alpha
igor_alpha

Hi phytomer,
Try following:
in start-->program files-->microsoft sql server--> configurtion tools-->

reporting server configuration.

in report server virtual directory --> uncheck the require secure socket layer (ssl) connections--> press apply


If a Secure Sockets Layer (SSL) certificate is installed and you get the error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel", set ReportServerUrl to the fully-qualified domain name of the server for which the SSL certificate was issued. For example, if the certificate is registered to https://adventure-works.com.onlinesales, the report server URL would be https://adventure-works.com.onlinesales/reportserver.
Avatar of phytomer

ASKER

SSL connections was never checked.  And as far as I can tell, the report server is using the same FQDN as specified in the certificate.  The virtual directories are the same as they were prior to the upgrade using the reporting server configuration utility so, in theory, I thought I could maintain the FQDN and the cert would be happy.  But... that's not the case.

A couple things I'm confused about...
Who issued the certificate?
How can I test if the Certificate is valid?

ASKER CERTIFIED SOLUTION
Avatar of igor_alpha
igor_alpha

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I reinstalled the certificate and everything works. Thanks for your help!
FYI in case anyone else runs into the same issue that I ran into...

I have ReportServer 2008 running on Windows Server 2008 with IIS6.0
Our database team installed ReportServer 2008 which by default took over port 80
While this would normally work well for a dedicated report server, this didn't work so well with the intended primary role of the server "Intranet Web Server"...
Of course all you have to do is enter the Report Server Configuration utility and change the default port from port 80 to whatever else works (8 for example)....
However when this was done, ReportServer 2008 automatically enabled SSL which required an active certificate.
It just so happened the server had an active certificate at the time of the change so no issue was identified at the time...
Unfortunately 6 months later the certificate expired and report services quit with the above error message being returned.

The fix:
Locate rsreportserver.config and change <Add Key="SecureConnectionLevel" Value="2"/> to <Add Key="SecureConnectionLevel" Value="0"/>
This disables the requirement of a secure connection and should resolve any errors you may have gotten due to it.
Note: I was unable to remove SSL using the Report Server Configuration tool and get the service to work.