Could not establish secure channel for SSL/TLS

We are getting the same error. We changed the asp timeout at the master property level, and we are now getting the same error. I have checked the RSWebApplication.config and it matches the server name.
I have gone through the other posts around this issue, but haven't been able to resolve the issue. I am at the point of reinstalling Reporting Services and setting up all of our reports again.
Any help would be appreciated!!!I found no solution ... and try to uninstall Report Services to make a new
installation. Also was not able to uninstall ... had to move to a new Server
:(
Tiago Andrade e Silva
"kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> We are getting the same error. We changed the asp timeout at the master
property level, and we are now getting the same error. I have checked the
RSWebApplication.config and it matches the server name.
> I have gone through the other posts around this issue, but haven't been
able to resolve the issue. I am at the point of reinstalling Reporting
Services and setting up all of our reports again.
> Any help would be appreciated!!!
>|||SSL is not a requirement for Reporting services. Try setting
SecureConnectionLevel to 0 in RSReportsErver.config - there are more details
about it in the books online.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> Tiago,
> Did you ever get a resolution or a workaround from MS on this issue? We
are having the same problem, and IIS on the report server is NOT configured
for SSL! Do you know if SSL is a requirement for Reporting Services?
> Thanks,
> Aisha
> "Tiago Andrade e Silva" wrote:
> > I found no solution ... and try to uninstall Report Services to make a
new
> > installation. Also was not able to uninstall ... had to move to a new
Server
> > :(
> >
> > Tiago Andrade e Silva
> > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
> > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > We are getting the same error. We changed the asp timeout at the
master
> > property level, and we are now getting the same error. I have checked
the
> > RSWebApplication.config and it matches the server name.
> > >
> > > I have gone through the other posts around this issue, but haven't
been
> > able to resolve the issue. I am at the point of reinstalling Reporting
> > Services and setting up all of our reports again.
> > >
> > > Any help would be appreciated!!!
> > >
> >
> >
> >|||The error in the title of this post is "Could not establish secure channel
for SSL/TLS". You should never get this error if you are not using SSL, are
you saying you are getting it? What is the exact request that fails with
this error?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> Tudor,
> That has already been established per RSReportServer.config , <Add
Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we are
NOT USING SSL.
> What books online are you talking about? Can you provide more details on
this? Seems like several others have the same issue, like Tiago, and he
never found a resolution and ended up moving Reporting Services to another
server? Is that the resolution? What if it starts happening on the new
server?
> Please provide more helpful information on this issue. Most of these
threads with this issue have been started since May and no resolution posted
thus far?
> Aisha
> "Tudor Trufinescu (MSFT)" wrote:
> > SSL is not a requirement for Reporting services. Try setting
> > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
details
> > about it in the books online.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > Tiago,
> > >
> > > Did you ever get a resolution or a workaround from MS on this issue?
We
> > are having the same problem, and IIS on the report server is NOT
configured
> > for SSL! Do you know if SSL is a requirement for Reporting Services?
> > >
> > > Thanks,
> > > Aisha
> > >
> > > "Tiago Andrade e Silva" wrote:
> > >
> > > > I found no solution ... and try to uninstall Report Services to
make a
> > new
> > > > installation. Also was not able to uninstall ... had to move to a
new
> > Server
> > > > :(
> > > >
> > > > Tiago Andrade e Silva
> > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
wrote in
> > > > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > We are getting the same error. We changed the asp timeout at the
> > master
> > > > property level, and we are now getting the same error. I have
checked
> > the
> > > > RSWebApplication.config and it matches the server name.
> > > > >
> > > > > I have gone through the other posts around this issue, but haven't
> > been
> > > > able to resolve the issue. I am at the point of reinstalling
Reporting
> > > > Services and setting up all of our reports again.
> > > > >
> > > > > Any help would be appreciated!!!
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||What is the URL in RSWebApplication.config ?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:78F9C232-00B0-4611-9048-7D40CD3D9399@.microsoft.com...
> Tudor,
> Here is a copy of the ReportServerWebApp__08_04_2004_08_56_18.log from
this morning when I tried accessing http://myservername/reports:
> <begin ReportServerWebApp log file>
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Central Daylight Time</TimeZone>
> <Path>D:\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__08_04_2004_08_56_18.log</Path>
> <SystemName>myservername</SystemName>
> <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> <OSVersion>5.0.2195.0</OSVersion>
> </Header>
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: The underlying connection
was closed: Could not establish secure channel for SSL/TLS.
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
establish secure channel for SSL/TLS. -->
System.ComponentModel.Win32Exception: The function completed successfully,
but must be called again to complete the context
> -- End of inner exception stack trace --
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
> at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
> </end ReportServerWebApp log file>
> Here is the IIS log from this morning:
> <begin IIS log>
> #Software: Microsoft Internet Information Services 5.0
> #Version: 1.0
> #Date: 2004-08-04 13:56:18
> #Fields: date time s-port cs-method cs-uri-stem cs-uri-query sc-status
cs(User-Agent)
> 2004-08-04 13:56:18 80 GET /reports - 401
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/ - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/Home.aspx - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 GET /reports/Pages/Folder.aspx - 500
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/js/ReportingServices.js - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/styles/ReportingServices.css - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/blank.gif - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/48error.jpg - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> </end IIS log>
> Please let me know if you need any other information. I didn't see a
place to upload files, so that is why I am just putting the information in
here. Also, if you search this newsgroup for the "Could not establish
secure channel for SSL/TLS" error, you will find some other posts with users
with this same problem when the SecureConnectionLevel Value = 0.
> Thanks,
> Aisha
>
> "Tudor Trufinescu (MSFT)" wrote:
> > The error in the title of this post is "Could not establish secure
channel
> > for SSL/TLS". You should never get this error if you are not using SSL,
are
> > you saying you are getting it? What is the exact request that fails with
> > this error?
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> > > Tudor,
> > >
> > > That has already been established per RSReportServer.config , <Add
> > Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we
are
> > NOT USING SSL.
> > >
> > > What books online are you talking about? Can you provide more details
on
> > this? Seems like several others have the same issue, like Tiago, and he
> > never found a resolution and ended up moving Reporting Services to
another
> > server? Is that the resolution? What if it starts happening on the new
> > server?
> > >
> > > Please provide more helpful information on this issue. Most of these
> > threads with this issue have been started since May and no resolution
posted
> > thus far?
> > >
> > > Aisha
> > >
> > > "Tudor Trufinescu (MSFT)" wrote:
> > >
> > > > SSL is not a requirement for Reporting services. Try setting
> > > > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
> > details
> > > > about it in the books online.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > > > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > > > Tiago,
> > > > >
> > > > > Did you ever get a resolution or a workaround from MS on this
issue?
> > We
> > > > are having the same problem, and IIS on the report server is NOT
> > configured
> > > > for SSL! Do you know if SSL is a requirement for Reporting
Services?
> > > > >
> > > > > Thanks,
> > > > > Aisha
> > > > >
> > > > > "Tiago Andrade e Silva" wrote:
> > > > >
> > > > > > I found no solution ... and try to uninstall Report Services to
> > make a
> > > > new
> > > > > > installation. Also was not able to uninstall ... had to move to
a
> > new
> > > > Server
> > > > > > :(
> > > > > >
> > > > > > Tiago Andrade e Silva
> > > > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
> > wrote in
> > > > > > message
news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > > > We are getting the same error. We changed the asp timeout at
the
> > > > master
> > > > > > property level, and we are now getting the same error. I have
> > checked
> > > > the
> > > > > > RSWebApplication.config and it matches the server name.
> > > > > > >
> > > > > > > I have gone through the other posts around this issue, but
haven't
> > > > been
> > > > > > able to resolve the issue. I am at the point of reinstalling
> > Reporting
> > > > > > Services and setting up all of our reports again.
> > > > > > >
> > > > > > > Any help would be appreciated!!!
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >