RS Error: The underlying connection was closed: Could not establish secure channel for SSL

Hi,
I have been running Reporting Services without a hitch for the last
few weeks. Suddenly on saturday I started getting this error:
The underlying connection was closed: Could not establish secure
channel for SSL/TLS.
When I installed RS I did not check the SSL option.
SecureConnectionLevel is set to 0 in the config file.
No settings have been changed.
Any advise?
TerryRelated post:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Olap Worker" <olapwork@.yahoo.com> wrote in message
news:e0f48230.0407251452.4c976b05@.posting.google.com...
> Hi,
> I have been running Reporting Services without a hitch for the last
> few weeks. Suddenly on saturday I started getting this error:
> The underlying connection was closed: Could not establish secure
> channel for SSL/TLS.
> When I installed RS I did not check the SSL option.
> SecureConnectionLevel is set to 0 in the config file.
> No settings have been changed.
> Any advise?
> Terry|||> Related post:
> http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
Yeah, I have seen this article, but I am NOT using SSL. When I
navigate to the reports I use http://mycompany/reports
I tried navigating to https://mycompanyserver/ReportServer but IE
never loads the page
I also tried setting SecureConnectionLevel to 3 but nothing works.
I will try reinstall RS and see if this helps|||SSL is not a prerequisite for Reporting Services.
Can you access the report manager root and report root from IE? Please let
me know. I'll then follow up on your issue further.
--
Ravi Mumulla (Microsoft)
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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> Ravi,
> We are having the same problem, but the IIS on the report server is NOT
configured for SSL! Is this a requirement for Reporting Services? Is there
a resolution to this problem if we are not configured for SSL to begin with?
Please advise, as this has happened in test and we would like to prevent it
from happening in our live area.
> Thanks,
> Aisha/Ray
> "Ravi Mumulla (Microsoft)" wrote:
> > Related post:
> >
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> >
> > --
> > Ravi Mumulla (Microsoft)
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> > > Hi,
> > >
> > > I have been running Reporting Services without a hitch for the last
> > > few weeks. Suddenly on saturday I started getting this error:
> > > The underlying connection was closed: Could not establish secure
> > > channel for SSL/TLS.
> > >
> > > When I installed RS I did not check the SSL option.
> > > SecureConnectionLevel is set to 0 in the config file.
> > >
> > > No settings have been changed.
> > >
> > > Any advise?
> > >
> > > Terry
> >
> >
> >|||Ravi,
No, we cannot access the report manager, root directory from IE. When navigating to the reports I use http://mycompanyserver/reports which results in the "The underlying connection was closed: Could not establish secure channel for SSL/TLS."
When I try navigating to http://mycompanyserver/ReportServer ,IE does not load the page and gives error "You are not authorized to view this page."
Please advise.
Thanks,
Aisha
"Ravi Mumulla (Microsoft)" wrote:
> SSL is not a prerequisite for Reporting Services.
> Can you access the report manager root and report root from IE? Please let
> me know. I'll then follow up on your issue further.
> --
> Ravi Mumulla (Microsoft)
> 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> > Ravi,
> >
> > We are having the same problem, but the IIS on the report server is NOT
> configured for SSL! Is this a requirement for Reporting Services? Is there
> a resolution to this problem if we are not configured for SSL to begin with?
> Please advise, as this has happened in test and we would like to prevent it
> from happening in our live area.
> >
> > Thanks,
> > Aisha/Ray
> >
> > "Ravi Mumulla (Microsoft)" wrote:
> >
> > > Related post:
> > >
> http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> > >
> > > --
> > > Ravi Mumulla (Microsoft)
> > > SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> > > > Hi,
> > > >
> > > > I have been running Reporting Services without a hitch for the last
> > > > few weeks. Suddenly on saturday I started getting this error:
> > > > The underlying connection was closed: Could not establish secure
> > > > channel for SSL/TLS.
> > > >
> > > > When I installed RS I did not check the SSL option.
> > > > SecureConnectionLevel is set to 0 in the config file.
> > > >
> > > > No settings have been changed.
> > > >
> > > > Any advise?
> > > >
> > > > Terry
> > >
> > >
> > >
>
>|||Hi all, I am experiencing the same issue. I am trying to trial the reporting
services (eval version) and am not using SSL. I have looked through all the
threads on this subject and many people are having this problem and there has
yet to be a solution. I am running the reporting services on a dev machine
with WinXP SP2, VS.Net 2003, SQL Server 2000 SP3a and IIS 5.1
I am running sql server authentication in mixed mode and my MSSQLSERVER
service is running under the local system account.
I try to access http:\\machinename\reports and I get the error:
The underlying connection was closed: Could not establish secure channel for
SSL/TLS.
I have read all the post in this newsgroup regarding this issue so please do
not ask me to check if SSL required is checked or if the <Add
Key="SecureConnectionLevel" Value="0"/> is present.
Thanks in advance for any help you can provide.
"Ray" wrote:
> Ravi,
> What is the status on this?
> Aisha
> "Ravi Mumulla (Microsoft)" wrote:
> > SSL is not a prerequisite for Reporting Services.
> >
> > Can you access the report manager root and report root from IE? Please let
> > me know. I'll then follow up on your issue further.
> >
> > --
> > Ravi Mumulla (Microsoft)
> > 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> > > Ravi,
> > >
> > > We are having the same problem, but the IIS on the report server is NOT
> > configured for SSL! Is this a requirement for Reporting Services? Is there
> > a resolution to this problem if we are not configured for SSL to begin with?
> > Please advise, as this has happened in test and we would like to prevent it
> > from happening in our live area.
> > >
> > > Thanks,
> > > Aisha/Ray
> > >
> > > "Ravi Mumulla (Microsoft)" wrote:
> > >
> > > > Related post:
> > > >
> > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> > > >
> > > > --
> > > > Ravi Mumulla (Microsoft)
> > > > SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> > > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> > > > > Hi,
> > > > >
> > > > > I have been running Reporting Services without a hitch for the last
> > > > > few weeks. Suddenly on saturday I started getting this error:
> > > > > The underlying connection was closed: Could not establish secure
> > > > > channel for SSL/TLS.
> > > > >
> > > > > When I installed RS I did not check the SSL option.
> > > > > SecureConnectionLevel is set to 0 in the config file.
> > > > >
> > > > > No settings have been changed.
> > > > >
> > > > > Any advise?
> > > > >
> > > > > Terry
> > > >
> > > >
> > > >
> >
> >
> >|||I figured out my problem. I checked my reportserver in IIS and noticed that
my application mappings were not set up correctly. I used the microsoft
knowledge base article located at http://support.microsoft.com/?kbid=867872
to figure out what the mappings should be. In the section to set up the
ReportServer application mappings in IIS you need to remove the mappings and
then add the mapping * click all verbs and select the Aspnet_isapi.dll.
It seems that this did not happen. For those of you using IIS 5.1 if you
try to enter just the * in the extension then you will not be able to click
OK (it will be disabled) enter ".*" (no quotes) and the OK button will be
enabled.
See http://forums.devarticles.com/archive/t-2527 for more info.
Click OK then restart the ReportServer Service and presto I am up and running.
So if you are using reporting services and not using SSL then check your
mappings and this may fix your problem and hopefully your frustrations.
I'm back in business baby!
Alex
"Alex" wrote:
> Hi all, I am experiencing the same issue. I am trying to trial the reporting
> services (eval version) and am not using SSL. I have looked through all the
> threads on this subject and many people are having this problem and there has
> yet to be a solution. I am running the reporting services on a dev machine
> with WinXP SP2, VS.Net 2003, SQL Server 2000 SP3a and IIS 5.1
> I am running sql server authentication in mixed mode and my MSSQLSERVER
> service is running under the local system account.
> I try to access http:\\machinename\reports and I get the error:
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS.
> I have read all the post in this newsgroup regarding this issue so please do
> not ask me to check if SSL required is checked or if the <Add
> Key="SecureConnectionLevel" Value="0"/> is present.
> Thanks in advance for any help you can provide.
>
> "Ray" wrote:
> > Ravi,
> >
> > What is the status on this?
> >
> > Aisha
> >
> > "Ravi Mumulla (Microsoft)" wrote:
> >
> > > SSL is not a prerequisite for Reporting Services.
> > >
> > > Can you access the report manager root and report root from IE? Please let
> > > me know. I'll then follow up on your issue further.
> > >
> > > --
> > > Ravi Mumulla (Microsoft)
> > > 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> > > > Ravi,
> > > >
> > > > We are having the same problem, but the IIS on the report server is NOT
> > > configured for SSL! Is this a requirement for Reporting Services? Is there
> > > a resolution to this problem if we are not configured for SSL to begin with?
> > > Please advise, as this has happened in test and we would like to prevent it
> > > from happening in our live area.
> > > >
> > > > Thanks,
> > > > Aisha/Ray
> > > >
> > > > "Ravi Mumulla (Microsoft)" wrote:
> > > >
> > > > > Related post:
> > > > >
> > > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> > > > >
> > > > > --
> > > > > Ravi Mumulla (Microsoft)
> > > > > SQL Server Reporting Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> > > > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> > > > > > Hi,
> > > > > >
> > > > > > I have been running Reporting Services without a hitch for the last
> > > > > > few weeks. Suddenly on saturday I started getting this error:
> > > > > > The underlying connection was closed: Could not establish secure
> > > > > > channel for SSL/TLS.
> > > > > >
> > > > > > When I installed RS I did not check the SSL option.
> > > > > > SecureConnectionLevel is set to 0 in the config file.
> > > > > >
> > > > > > No settings have been changed.
> > > > > >
> > > > > > Any advise?
> > > > > >
> > > > > > Terry
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >|||Thank you soo much!
This post helped fixed my problem (RS stopped working after renaming the
server). It was the IIS application mappings in RS.
Marlon
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:694C9B98-9AFF-4A4B-9D7A-258E4622A957@.microsoft.com...
>I figured out my problem. I checked my reportserver in IIS and noticed
>that
> my application mappings were not set up correctly. I used the microsoft
> knowledge base article located at
> http://support.microsoft.com/?kbid=867872
> to figure out what the mappings should be. In the section to set up the
> ReportServer application mappings in IIS you need to remove the mappings
> and
> then add the mapping * click all verbs and select the Aspnet_isapi.dll.
> It seems that this did not happen. For those of you using IIS 5.1 if you
> try to enter just the * in the extension then you will not be able to
> click
> OK (it will be disabled) enter ".*" (no quotes) and the OK button will be
> enabled.
> See http://forums.devarticles.com/archive/t-2527 for more info.
> Click OK then restart the ReportServer Service and presto I am up and
> running.
> So if you are using reporting services and not using SSL then check your
> mappings and this may fix your problem and hopefully your frustrations.
> I'm back in business baby!
> Alex
>
> "Alex" wrote:
>> Hi all, I am experiencing the same issue. I am trying to trial the
>> reporting
>> services (eval version) and am not using SSL. I have looked through all
>> the
>> threads on this subject and many people are having this problem and there
>> has
>> yet to be a solution. I am running the reporting services on a dev
>> machine
>> with WinXP SP2, VS.Net 2003, SQL Server 2000 SP3a and IIS 5.1
>> I am running sql server authentication in mixed mode and my MSSQLSERVER
>> service is running under the local system account.
>> I try to access http:\\machinename\reports and I get the error:
>> The underlying connection was closed: Could not establish secure channel
>> for
>> SSL/TLS.
>> I have read all the post in this newsgroup regarding this issue so please
>> do
>> not ask me to check if SSL required is checked or if the <Add
>> Key="SecureConnectionLevel" Value="0"/> is present.
>> Thanks in advance for any help you can provide.
>>
>> "Ray" wrote:
>> > Ravi,
>> >
>> > What is the status on this?
>> >
>> > Aisha
>> >
>> > "Ravi Mumulla (Microsoft)" wrote:
>> >
>> > > SSL is not a prerequisite for Reporting Services.
>> > >
>> > > Can you access the report manager root and report root from IE?
>> > > Please let
>> > > me know. I'll then follow up on your issue further.
>> > >
>> > > --
>> > > Ravi Mumulla (Microsoft)
>> > > 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
>> > > > Ravi,
>> > > >
>> > > > We are having the same problem, but the IIS on the report server is
>> > > > NOT
>> > > configured for SSL! Is this a requirement for Reporting Services?
>> > > Is there
>> > > a resolution to this problem if we are not configured for SSL to
>> > > begin with?
>> > > Please advise, as this has happened in test and we would like to
>> > > prevent it
>> > > from happening in our live area.
>> > > >
>> > > > Thanks,
>> > > > Aisha/Ray
>> > > >
>> > > > "Ravi Mumulla (Microsoft)" wrote:
>> > > >
>> > > > > Related post:
>> > > > >
>> > > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
>> > > > >
>> > > > > --
>> > > > > Ravi Mumulla (Microsoft)
>> > > > > SQL Server Reporting Services
>> > > > >
>> > > > > This posting is provided "AS IS" with no warranties, and confers
>> > > > > no
>> > > rights.
>> > > > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
>> > > > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
>> > > > > > Hi,
>> > > > > >
>> > > > > > I have been running Reporting Services without a hitch for the
>> > > > > > last
>> > > > > > few weeks. Suddenly on saturday I started getting this error:
>> > > > > > The underlying connection was closed: Could not establish
>> > > > > > secure
>> > > > > > channel for SSL/TLS.
>> > > > > >
>> > > > > > When I installed RS I did not check the SSL option.
>> > > > > > SecureConnectionLevel is set to 0 in the config file.
>> > > > > >
>> > > > > > No settings have been changed.
>> > > > > >
>> > > > > > Any advise?
>> > > > > >
>> > > > > > Terry
>> > > > >
>> > > > >
>> > > > >
>> > >
>> > >
>> > >|||THANK YOU! i was having similar problem after installing the full VS.net pro
version over an earlier version. where once my RS was working perfectly, i
then had the same problems as this post. followed your directions and the
post article from "junkies" site and i'm back in business. this group is
great!
dale
"TechnoSpyke" wrote:
> Thank you soo much!
> This post helped fixed my problem (RS stopped working after renaming the
> server). It was the IIS application mappings in RS.
> Marlon
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:694C9B98-9AFF-4A4B-9D7A-258E4622A957@.microsoft.com...
> >I figured out my problem. I checked my reportserver in IIS and noticed
> >that
> > my application mappings were not set up correctly. I used the microsoft
> > knowledge base article located at
> > http://support.microsoft.com/?kbid=867872
> > to figure out what the mappings should be. In the section to set up the
> > ReportServer application mappings in IIS you need to remove the mappings
> > and
> > then add the mapping * click all verbs and select the Aspnet_isapi.dll.
> >
> > It seems that this did not happen. For those of you using IIS 5.1 if you
> > try to enter just the * in the extension then you will not be able to
> > click
> > OK (it will be disabled) enter ".*" (no quotes) and the OK button will be
> > enabled.
> >
> > See http://forums.devarticles.com/archive/t-2527 for more info.
> >
> > Click OK then restart the ReportServer Service and presto I am up and
> > running.
> >
> > So if you are using reporting services and not using SSL then check your
> > mappings and this may fix your problem and hopefully your frustrations.
> >
> > I'm back in business baby!
> > Alex
> >
> >
> > "Alex" wrote:
> >
> >> Hi all, I am experiencing the same issue. I am trying to trial the
> >> reporting
> >> services (eval version) and am not using SSL. I have looked through all
> >> the
> >> threads on this subject and many people are having this problem and there
> >> has
> >> yet to be a solution. I am running the reporting services on a dev
> >> machine
> >> with WinXP SP2, VS.Net 2003, SQL Server 2000 SP3a and IIS 5.1
> >> I am running sql server authentication in mixed mode and my MSSQLSERVER
> >> service is running under the local system account.
> >>
> >> I try to access http:\\machinename\reports and I get the error:
> >> The underlying connection was closed: Could not establish secure channel
> >> for
> >> SSL/TLS.
> >>
> >> I have read all the post in this newsgroup regarding this issue so please
> >> do
> >> not ask me to check if SSL required is checked or if the <Add
> >> Key="SecureConnectionLevel" Value="0"/> is present.
> >>
> >> Thanks in advance for any help you can provide.
> >>
> >>
> >> "Ray" wrote:
> >>
> >> > Ravi,
> >> >
> >> > What is the status on this?
> >> >
> >> > Aisha
> >> >
> >> > "Ravi Mumulla (Microsoft)" wrote:
> >> >
> >> > > SSL is not a prerequisite for Reporting Services.
> >> > >
> >> > > Can you access the report manager root and report root from IE?
> >> > > Please let
> >> > > me know. I'll then follow up on your issue further.
> >> > >
> >> > > --
> >> > > Ravi Mumulla (Microsoft)
> >> > > 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> >> > > > Ravi,
> >> > > >
> >> > > > We are having the same problem, but the IIS on the report server is
> >> > > > NOT
> >> > > configured for SSL! Is this a requirement for Reporting Services?
> >> > > Is there
> >> > > a resolution to this problem if we are not configured for SSL to
> >> > > begin with?
> >> > > Please advise, as this has happened in test and we would like to
> >> > > prevent it
> >> > > from happening in our live area.
> >> > > >
> >> > > > Thanks,
> >> > > > Aisha/Ray
> >> > > >
> >> > > > "Ravi Mumulla (Microsoft)" wrote:
> >> > > >
> >> > > > > Related post:
> >> > > > >
> >> > > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> >> > > > >
> >> > > > > --
> >> > > > > Ravi Mumulla (Microsoft)
> >> > > > > SQL Server Reporting Services
> >> > > > >
> >> > > > > This posting is provided "AS IS" with no warranties, and confers
> >> > > > > no
> >> > > rights.
> >> > > > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> >> > > > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > I have been running Reporting Services without a hitch for the
> >> > > > > > last
> >> > > > > > few weeks. Suddenly on saturday I started getting this error:
> >> > > > > > The underlying connection was closed: Could not establish
> >> > > > > > secure
> >> > > > > > channel for SSL/TLS.
> >> > > > > >
> >> > > > > > When I installed RS I did not check the SSL option.
> >> > > > > > SecureConnectionLevel is set to 0 in the config file.
> >> > > > > >
> >> > > > > > No settings have been changed.
> >> > > > > >
> >> > > > > > Any advise?
> >> > > > > >
> >> > > > > > Terry
> >> > > > >
> >> > > > >
> >> > > > >
> >> > >
> >> > >
> >> > >
>
>|||I was not using SSL.
I seemed to get this issue at about the last time I ran Lockdown on IIS.
Setting an App Map in the config section of your Report Server virtual dir
for extension '*' seems to have resolved my issue.
This may not be too secure though
"Olap Worker" wrote:
> Hi,
> I have been running Reporting Services without a hitch for the last
> few weeks. Suddenly on saturday I started getting this error:
> The underlying connection was closed: Could not establish secure
> channel for SSL/TLS.
> When I installed RS I did not check the SSL option.
> SecureConnectionLevel is set to 0 in the config file.
> No settings have been changed.
> Any advise?
> Terry
>|||Alex,
I tried your fix, and followed the support article you mentioned,but i can't
put a '*' in the mappings box as it keeps telling me it's the wrong format! I
am using IIS6 Win2003, any ideas
"Alex" wrote:
> I figured out my problem. I checked my reportserver in IIS and noticed that
> my application mappings were not set up correctly. I used the microsoft
> knowledge base article located at http://support.microsoft.com/?kbid=867872
> to figure out what the mappings should be. In the section to set up the
> ReportServer application mappings in IIS you need to remove the mappings and
> then add the mapping * click all verbs and select the Aspnet_isapi.dll.
> It seems that this did not happen. For those of you using IIS 5.1 if you
> try to enter just the * in the extension then you will not be able to click
> OK (it will be disabled) enter ".*" (no quotes) and the OK button will be
> enabled.
> See http://forums.devarticles.com/archive/t-2527 for more info.
> Click OK then restart the ReportServer Service and presto I am up and running.
> So if you are using reporting services and not using SSL then check your
> mappings and this may fix your problem and hopefully your frustrations.
> I'm back in business baby!
> Alex
>
> "Alex" wrote:
> > Hi all, I am experiencing the same issue. I am trying to trial the reporting
> > services (eval version) and am not using SSL. I have looked through all the
> > threads on this subject and many people are having this problem and there has
> > yet to be a solution. I am running the reporting services on a dev machine
> > with WinXP SP2, VS.Net 2003, SQL Server 2000 SP3a and IIS 5.1
> > I am running sql server authentication in mixed mode and my MSSQLSERVER
> > service is running under the local system account.
> >
> > I try to access http:\\machinename\reports and I get the error:
> > The underlying connection was closed: Could not establish secure channel for
> > SSL/TLS.
> >
> > I have read all the post in this newsgroup regarding this issue so please do
> > not ask me to check if SSL required is checked or if the <Add
> > Key="SecureConnectionLevel" Value="0"/> is present.
> >
> > Thanks in advance for any help you can provide.
> >
> >
> > "Ray" wrote:
> >
> > > Ravi,
> > >
> > > What is the status on this?
> > >
> > > Aisha
> > >
> > > "Ravi Mumulla (Microsoft)" wrote:
> > >
> > > > SSL is not a prerequisite for Reporting Services.
> > > >
> > > > Can you access the report manager root and report root from IE? Please let
> > > > me know. I'll then follow up on your issue further.
> > > >
> > > > --
> > > > Ravi Mumulla (Microsoft)
> > > > 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:AECF6320-C5AA-4FE5-B2E3-54356D0D5029@.microsoft.com...
> > > > > Ravi,
> > > > >
> > > > > We are having the same problem, but the IIS on the report server is NOT
> > > > configured for SSL! Is this a requirement for Reporting Services? Is there
> > > > a resolution to this problem if we are not configured for SSL to begin with?
> > > > Please advise, as this has happened in test and we would like to prevent it
> > > > from happening in our live area.
> > > > >
> > > > > Thanks,
> > > > > Aisha/Ray
> > > > >
> > > > > "Ravi Mumulla (Microsoft)" wrote:
> > > > >
> > > > > > Related post:
> > > > > >
> > > > http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=3a7ae971-73e5-4ae1-a41d-7f14be6875ab
> > > > > >
> > > > > > --
> > > > > > Ravi Mumulla (Microsoft)
> > > > > > SQL Server Reporting Services
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > > rights.
> > > > > > "Olap Worker" <olapwork@.yahoo.com> wrote in message
> > > > > > news:e0f48230.0407251452.4c976b05@.posting.google.com...
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have been running Reporting Services without a hitch for the last
> > > > > > > few weeks. Suddenly on saturday I started getting this error:
> > > > > > > The underlying connection was closed: Could not establish secure
> > > > > > > channel for SSL/TLS.
> > > > > > >
> > > > > > > When I installed RS I did not check the SSL option.
> > > > > > > SecureConnectionLevel is set to 0 in the config file.
> > > > > > >
> > > > > > > No settings have been changed.
> > > > > > >
> > > > > > > Any advise?
> > > > > > >
> > > > > > > Terry
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >