Saturday, February 25, 2012

Could not establish secure channel for SSL/TLS

I've seen posts for this error, but real explanation or solution.
Information about my settings are below.
ReportManager : RSWebApplication.config
<ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
ReportServer : RSReportServer.config
<Add Key="SecureConnectionLevel" Value="3"/>
<UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
Default Website, Reports (Report Manager), and ReportServer site all
have Require secure channel (SSL) - checked.
Error Message is:
The underlying connection was closed: Could not establish secure
channel for SSL/TLS.
Explanation/Solution? Thank you!I've seen this happening when the name for which the certificate was
requested does not match the name of the URL, or has expired, or is
otherwise invalid. If you navigate to https://mycompanyserver/ReportServer
and get a warning dialog-box in IE, the SOAP calls will fail with the
message you describe.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"swruble" <swruble@.alogistics.com> wrote in message
news:de0fd1d1.0406280355.2aeb382e@.posting.google.com...
> I've seen posts for this error, but real explanation or solution.
> Information about my settings are below.
> ReportManager : RSWebApplication.config
> <ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
> ReportServer : RSReportServer.config
> <Add Key="SecureConnectionLevel" Value="3"/>
> <UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
> Default Website, Reports (Report Manager), and ReportServer site all
> have Require secure channel (SSL) - checked.
> Error Message is:
> The underlying connection was closed: Could not establish secure
> channel for SSL/TLS.
> Explanation/Solution? Thank you!|||Tudor, thanks for your response. Everything looks OK with the
certificate with the site configuration. I find that
https://mycompanyserver/ReportServer allows me to browse the
directory. Opening a folder and selecting a report allows me to view
reports fine. I get the original error message whenever I attempt to
access https://mycompanyserver/Reports.
"Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message news:<OQ3TwuTXEHA.2964@.TK2MSFTNGP09.phx.gbl>...
> I've seen this happening when the name for which the certificate was
> requested does not match the name of the URL, or has expired, or is
> otherwise invalid. If you navigate to https://mycompanyserver/ReportServer
> and get a warning dialog-box in IE, the SOAP calls will fail with the
> message you describe.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "swruble" <swruble@.alogistics.com> wrote in message
> news:de0fd1d1.0406280355.2aeb382e@.posting.google.com...
> > I've seen posts for this error, but real explanation or solution.
> > Information about my settings are below.
> >
> > ReportManager : RSWebApplication.config
> > <ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
> >
> > ReportServer : RSReportServer.config
> > <Add Key="SecureConnectionLevel" Value="3"/>
> > <UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
> >
> > Default Website, Reports (Report Manager), and ReportServer site all
> > have Require secure channel (SSL) - checked.
> >
> > Error Message is:
> > The underlying connection was closed: Could not establish secure
> > channel for SSL/TLS.
> >
> > Explanation/Solution? Thank you!|||Make sure the URL in RSWebApplication.config contains the same server name
as the one to which the certificate was granted to.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"swruble" <swruble@.alogistics.com> wrote in message
news:de0fd1d1.0406292104.4648e20f@.posting.google.com...
> Tudor, thanks for your response. Everything looks OK with the
> certificate with the site configuration. I find that
> https://mycompanyserver/ReportServer allows me to browse the
> directory. Opening a folder and selecting a report allows me to view
> reports fine. I get the original error message whenever I attempt to
> access https://mycompanyserver/Reports.
>
> "Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message
news:<OQ3TwuTXEHA.2964@.TK2MSFTNGP09.phx.gbl>...
> > I've seen this happening when the name for which the certificate was
> > requested does not match the name of the URL, or has expired, or is
> > otherwise invalid. If you navigate to
https://mycompanyserver/ReportServer
> > and get a warning dialog-box in IE, the SOAP calls will fail with the
> > message you describe.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "swruble" <swruble@.alogistics.com> wrote in message
> > news:de0fd1d1.0406280355.2aeb382e@.posting.google.com...
> > > I've seen posts for this error, but real explanation or solution.
> > > Information about my settings are below.
> > >
> > > ReportManager : RSWebApplication.config
> > >
<ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
> > >
> > > ReportServer : RSReportServer.config
> > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > <UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
> > >
> > > Default Website, Reports (Report Manager), and ReportServer site all
> > > have Require secure channel (SSL) - checked.
> > >
> > > Error Message is:
> > > The underlying connection was closed: Could not establish secure
> > > channel for SSL/TLS.
> > >
> > > Explanation/Solution? Thank you!|||I have checked the URL and certificate. The URL in
RSWebApplication.config is:
https://reports.mydomain.com/ReportServer. The certificate was
granted to: reports.mydomain.com
When I change <Add Key="SecureConnectionLevel" Value="3"/> to a Value
of 2, I do not get the error, but all my top links are wrong... http
instead of https.
I found a related article "Consuming Webservices over HTTPS" that
describes this issue. However, since I am only working with
configuration settings rather than code, I obviously have missed
something in the setup.
I appreciate your help!
"Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message news:<eaDs7TvXEHA.952@.TK2MSFTNGP10.phx.gbl>...
> Make sure the URL in RSWebApplication.config contains the same server name
> as the one to which the certificate was granted to.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "swruble" <swruble@.alogistics.com> wrote in message
> news:de0fd1d1.0406292104.4648e20f@.posting.google.com...
> > Tudor, thanks for your response. Everything looks OK with the
> > certificate with the site configuration. I find that
> > https://mycompanyserver/ReportServer allows me to browse the
> > directory. Opening a folder and selecting a report allows me to view
> > reports fine. I get the original error message whenever I attempt to
> > access https://mycompanyserver/Reports.
> >
> >
> > "Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message
> news:<OQ3TwuTXEHA.2964@.TK2MSFTNGP09.phx.gbl>...
> > > I've seen this happening when the name for which the certificate was
> > > requested does not match the name of the URL, or has expired, or is
> > > otherwise invalid. If you navigate to
> https://mycompanyserver/ReportServer
> > > and get a warning dialog-box in IE, the SOAP calls will fail with the
> > > message you describe.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "swruble" <swruble@.alogistics.com> wrote in message
> > > news:de0fd1d1.0406280355.2aeb382e@.posting.google.com...
> > > > I've seen posts for this error, but real explanation or solution.
> > > > Information about my settings are below.
> > > >
> > > > ReportManager : RSWebApplication.config
> > > >
> <ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
> > > >
> > > > ReportServer : RSReportServer.config
> > > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > > <UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
> > > >
> > > > Default Website, Reports (Report Manager), and ReportServer site all
> > > > have Require secure channel (SSL) - checked.
> > > >
> > > > Error Message is:
> > > > The underlying connection was closed: Could not establish secure
> > > > channel for SSL/TLS.
> > > >
> > > > Explanation/Solution? Thank you!|||The related article mentioned in my other post is:
http://weblogs.asp.net/jan/archive/2003/12/04/41154.aspx
"Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message news:<eaDs7TvXEHA.952@.TK2MSFTNGP10.phx.gbl>...
> Make sure the URL in RSWebApplication.config contains the same server name
> as the one to which the certificate was granted to.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "swruble" <swruble@.alogistics.com> wrote in message
> news:de0fd1d1.0406292104.4648e20f@.posting.google.com...
> > Tudor, thanks for your response. Everything looks OK with the
> > certificate with the site configuration. I find that
> > https://mycompanyserver/ReportServer allows me to browse the
> > directory. Opening a folder and selecting a report allows me to view
> > reports fine. I get the original error message whenever I attempt to
> > access https://mycompanyserver/Reports.
> >
> >
> > "Tudor Trufinescu \(MSFT\)" <tudortr@.ms.com> wrote in message
> news:<OQ3TwuTXEHA.2964@.TK2MSFTNGP09.phx.gbl>...
> > > I've seen this happening when the name for which the certificate was
> > > requested does not match the name of the URL, or has expired, or is
> > > otherwise invalid. If you navigate to
> https://mycompanyserver/ReportServer
> > > and get a warning dialog-box in IE, the SOAP calls will fail with the
> > > message you describe.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "swruble" <swruble@.alogistics.com> wrote in message
> > > news:de0fd1d1.0406280355.2aeb382e@.posting.google.com...
> > > > I've seen posts for this error, but real explanation or solution.
> > > > Information about my settings are below.
> > > >
> > > > ReportManager : RSWebApplication.config
> > > >
> <ReportServerUrl>https://mycompanyserver/ReportServer</ReportServerUrl>
> > > >
> > > > ReportServer : RSReportServer.config
> > > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > > <UrlRoot>https://mycompanyserver/ReportServer</UrlRoot>
> > > >
> > > > Default Website, Reports (Report Manager), and ReportServer site all
> > > > have Require secure channel (SSL) - checked.
> > > >
> > > > Error Message is:
> > > > The underlying connection was closed: Could not establish secure
> > > > channel for SSL/TLS.
> > > >
> > > > Explanation/Solution? Thank you!

No comments:

Post a Comment