Hi:
My long and sad tale of woe. Many months ago I tried to install a very early version of the RS download. I got partially thru when it told me I didn't have the right version of MS Studio. So I stopped and ordered the upgrade and put the whole thing on the back burner for several months. I have since upgraded VS and have downloaded the latest trial version of RS. It always aborts saying that SSL is not on my server. The checkbox where it asks about using SSL never displays during the installation. Feeling that something got set during a aborted install, I have tried numerous times to uninstall everything I can find on my machine related to RS but still with no luck. Any idea how I get around this?Hmm... you might have some random bits of MSI stuck on your machine. You
can try this:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/msizap_exe.asp
If you downloaded the public Beta version of RS, you can try removing the
following product code:
{38747EA3-0793-4AF5-90F8-BD151B4A6ABB}
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Terry Spencer" <Terry Spencer@.discussions.microsoft.com> wrote in message
news:2BB5DC0D-F795-46AF-A8D1-166AC8CB08AA@.microsoft.com...
> Hi:
> My long and sad tale of woe. Many months ago I tried to install a very
> early version of the RS download. I got partially thru when it told me I
> didn't have the right version of MS Studio. So I stopped and ordered the
> upgrade and put the whole thing on the back burner for several months. I
> have since upgraded VS and have downloaded the latest trial version of RS.
> It always aborts saying that SSL is not on my server. The checkbox where
> it asks about using SSL never displays during the installation. Feeling
> that something got set during a aborted install, I have tried numerous
> times to uninstall everything I can find on my machine related to RS but
> still with no luck. Any idea how I get around this?
Showing posts with label ssl. Show all posts
Showing posts with label ssl. Show all posts
Monday, March 12, 2012
Friday, March 9, 2012
RS Over Internet With SSL
Greetings all.
We're trying to run SQL Reporting Services over the internet with SSL. Our
reports contain sensitive data, so we want all Report Server traffic to go
over HTTPS (we do NOT want to allow any HTTP access).
We've got the Report Manager web application working, but with a couple of
quirks that we could use some help on.
Here is the current (functional but unacceptable) configuration...
This is a single-server deployment on Windows Server 2003 (and IIS) with SQL
Server 2000 (SP3a) and SQL Reporting Services (SP1).
IIS Anonymous access is turned off. Only Windows Authentication is used
(along with only Internet Explorer browsers).
The "Require secure channel (SSL)" checkboxes are NOT checked in the IIS
"Directory Security" settings for the Default Web Site along with the
"Reports" and "ReportServer" Virtual Directories (because if we do check it,
Report Manager won't work).
HTTP traffic is set to port 81 in IIS (for now - in order to reject all HTTP
traffic to the default port 80).
HTTPS traffic is set to the default port 443 in IIS.
The security certificate installed on this web server is configured for
"reports.mycompany.com" (of course with "mycompany" substituted for the
actual company name).
RSWebApplication.config:
<ReportServerUrl>http://localhost:81/ReportServer</ReportServerUrl>
<ReportServerExternalUrl>https://reports.mycompany.com/ReportServer</ReportS
erverExternalUrl>
RSReportServer.config:
<Add Key="SecureConnectionLevel" Value="2"/>
<UrlRoot>https://reports.mycompany.com/ReportServer</UrlRoot>
...
Report Manager DOES work over HTTPS with this configuration.
However, all of the Report Manager's upper navigation links ("Home," "My
Subscriptions," "Site Settings," "Help," and the breadcrumb-trail links) use
HTTP (over port 80, which we reject) instead of HTTPS, so none of these
links work.
...
Unfortunately, even though it works, this configuration is unacceptable
because a big requirement we have is that we want all Report Server traffic
to go over HTTPS; we do no want to allow HTTP traffic. The current
configuration still allows HTTP traffic over port 81 because it's the only
way we've been able to get things to work.
If we check the "Require secure channel (SSL)" checkbox in the IIS
"Directory Security" settings (which we want to do), Report Manager gives an
error saying "could not establish secure channel for SSL/TLS."
If we set the "SecureConnectionLevel" value to "3" then Report Manager gives
an error saying "could not establish secure channel for SSL/TLS."
We tried changing the "ReportServerUrl" node in the
"RSWebApplication.config" file to https://localhost/ReportServer (in order
to use nothing HTTPS paths in our configuration), but we continued to get
the "could not establish secure channel for SSL/TLS" error.
Does anyone have any ideas on how we can get all our traffic over HTTPS and
shut off all HTTP traffic?
Many Thanks!
JodyJody,
We do have RS working with SSL on one machine however on another machine we
can not get it to work. From your post I would recommend you change the
ReportServerURL node in your RSWebApplication.config file to
https://[FQDN]/ReportServer rather then https://localhost/ReportServer. For
example https://www.abc.com/ReportServer. Hope this helps.
We're trying to run SQL Reporting Services over the internet with SSL. Our
reports contain sensitive data, so we want all Report Server traffic to go
over HTTPS (we do NOT want to allow any HTTP access).
We've got the Report Manager web application working, but with a couple of
quirks that we could use some help on.
Here is the current (functional but unacceptable) configuration...
This is a single-server deployment on Windows Server 2003 (and IIS) with SQL
Server 2000 (SP3a) and SQL Reporting Services (SP1).
IIS Anonymous access is turned off. Only Windows Authentication is used
(along with only Internet Explorer browsers).
The "Require secure channel (SSL)" checkboxes are NOT checked in the IIS
"Directory Security" settings for the Default Web Site along with the
"Reports" and "ReportServer" Virtual Directories (because if we do check it,
Report Manager won't work).
HTTP traffic is set to port 81 in IIS (for now - in order to reject all HTTP
traffic to the default port 80).
HTTPS traffic is set to the default port 443 in IIS.
The security certificate installed on this web server is configured for
"reports.mycompany.com" (of course with "mycompany" substituted for the
actual company name).
RSWebApplication.config:
<ReportServerUrl>http://localhost:81/ReportServer</ReportServerUrl>
<ReportServerExternalUrl>https://reports.mycompany.com/ReportServer</ReportS
erverExternalUrl>
RSReportServer.config:
<Add Key="SecureConnectionLevel" Value="2"/>
<UrlRoot>https://reports.mycompany.com/ReportServer</UrlRoot>
...
Report Manager DOES work over HTTPS with this configuration.
However, all of the Report Manager's upper navigation links ("Home," "My
Subscriptions," "Site Settings," "Help," and the breadcrumb-trail links) use
HTTP (over port 80, which we reject) instead of HTTPS, so none of these
links work.
...
Unfortunately, even though it works, this configuration is unacceptable
because a big requirement we have is that we want all Report Server traffic
to go over HTTPS; we do no want to allow HTTP traffic. The current
configuration still allows HTTP traffic over port 81 because it's the only
way we've been able to get things to work.
If we check the "Require secure channel (SSL)" checkbox in the IIS
"Directory Security" settings (which we want to do), Report Manager gives an
error saying "could not establish secure channel for SSL/TLS."
If we set the "SecureConnectionLevel" value to "3" then Report Manager gives
an error saying "could not establish secure channel for SSL/TLS."
We tried changing the "ReportServerUrl" node in the
"RSWebApplication.config" file to https://localhost/ReportServer (in order
to use nothing HTTPS paths in our configuration), but we continued to get
the "could not establish secure channel for SSL/TLS" error.
Does anyone have any ideas on how we can get all our traffic over HTTPS and
shut off all HTTP traffic?
Many Thanks!
JodyJody,
We do have RS working with SSL on one machine however on another machine we
can not get it to work. From your post I would recommend you change the
ReportServerURL node in your RSWebApplication.config file to
https://[FQDN]/ReportServer rather then https://localhost/ReportServer. For
example https://www.abc.com/ReportServer. Hope this helps.
RS on SSL losing querystring in URL
Hi,
This is a live problem that Iam facing,
There is this internet application (in SSL) which I deployed at my
Client which access reports by calling something like
https://in4suite.symphonysv.com/ReportServer?/reports/ChangeInDealSizeReport&rs:Command=Render&userid=3®ionid=0
Here is the THE PROBLEM.
After I call the report (by clicking a link in the application) in the
INTERNET application, it opens well taking the default values. When I
change one value in any of the parameters, the parameter toolbar hangs
with the white blank screen. There is no postback happening or it is
hanging at the post back. So The customer cant do anything except see
the report for the default values.
I did this research. I called a report, When I right-clicked on the
report page to see the Properties window, I noticed that the parameters
in the URL which were supposed to be passed are not there. So the
Address:URL looked like this
https://in4suite.symphonysv.com/ReportServer?%2freports%
It does not carry any info on the URL except the report folder. So I
believe this is why the report is hanging. So this means the
querystring is being lost.
What is the workaround or trick to let the URL in full be available
after calling the report the first time. This will help the post back
occur Iam sure.
Help Please.
Anand Sagar
In4VelocityNo WAIT !!
I was wrong. The complete URL qureystring is still there. It does not
lose the querystring, I was not scrolling down completely.
The reason for the problem is something else.|||Here is the actual problem.
Iam passing a parameter '&userid=3' in the URL when I first call the
report. The report shows up fine. Then when I change any other
parameter value in the report parameters UI, a post back occurs and the
report hangs. I noticed that when I drag down the separator between the
parameter area and the report area, I see another report page behind
which says
"This report requires a default or user-defined value for the report
parameter 'userid'. To run or subscribe to this report, you must
provide a parameter value. (rsReportParameterValueNotSet)"
So this means when a postback occurs, the default parameter in the URL
is lost. Why does this happen. Any ideas ? The report server is in SSL.
Is this an issue ?
Thanks,
Anand Sagar
This is a live problem that Iam facing,
There is this internet application (in SSL) which I deployed at my
Client which access reports by calling something like
https://in4suite.symphonysv.com/ReportServer?/reports/ChangeInDealSizeReport&rs:Command=Render&userid=3®ionid=0
Here is the THE PROBLEM.
After I call the report (by clicking a link in the application) in the
INTERNET application, it opens well taking the default values. When I
change one value in any of the parameters, the parameter toolbar hangs
with the white blank screen. There is no postback happening or it is
hanging at the post back. So The customer cant do anything except see
the report for the default values.
I did this research. I called a report, When I right-clicked on the
report page to see the Properties window, I noticed that the parameters
in the URL which were supposed to be passed are not there. So the
Address:URL looked like this
https://in4suite.symphonysv.com/ReportServer?%2freports%
It does not carry any info on the URL except the report folder. So I
believe this is why the report is hanging. So this means the
querystring is being lost.
What is the workaround or trick to let the URL in full be available
after calling the report the first time. This will help the post back
occur Iam sure.
Help Please.
Anand Sagar
In4VelocityNo WAIT !!
I was wrong. The complete URL qureystring is still there. It does not
lose the querystring, I was not scrolling down completely.
The reason for the problem is something else.|||Here is the actual problem.
Iam passing a parameter '&userid=3' in the URL when I first call the
report. The report shows up fine. Then when I change any other
parameter value in the report parameters UI, a post back occurs and the
report hangs. I noticed that when I drag down the separator between the
parameter area and the report area, I see another report page behind
which says
"This report requires a default or user-defined value for the report
parameter 'userid'. To run or subscribe to this report, you must
provide a parameter value. (rsReportParameterValueNotSet)"
So this means when a postback occurs, the default parameter in the URL
is lost. Why does this happen. Any ideas ? The report server is in SSL.
Is this an issue ?
Thanks,
Anand Sagar
Wednesday, March 7, 2012
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
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
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
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
Subscribe to:
Posts (Atom)