Alternate SSL port

Is it possible for Reporting Services with SP1 to use a port other than 443
for SSL? Our web server already has a web site running on port 443 which we
can't move.Yes, you can navigate to the Web Site tab of the Default web site
properties page to change the port.
Also note that if you enable SSL after setup is run, make sure that the
SecureConnectionLevel in the configuration file (RSReportServer.config) is
modified from 2 to 3.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Alternate SSL port
>thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>X-WBNR-Posting-Host: 62.3.118.193
>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>Subject: Alternate SSL port
>Date: Wed, 30 Mar 2005 08:47:08 -0800
>Lines: 4
>Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46483
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>Is it possible for Reporting Services with SP1 to use a port other than
443
>for SSL? Our web server already has a web site running on port 443 which
we
>can't move.
>|||William,
I tried changing the SSL port in the default web site to 4445 and I ran
rsactive again. However the links from
http://dps-01/reports/Pages/Folder.aspx to the https pages, such as 'New Data
Source' do not have port 4445 added so they fail. How do I configure
Reporting Services to use this port?
Paul
"William Wang[MSFT]" wrote:
> Yes, you can navigate to the Web Site tab of the Default web site
> properties page to change the port.
> Also note that if you enable SSL after setup is run, make sure that the
> SecureConnectionLevel in the configuration file (RSReportServer.config) is
> modified from 2 to 3.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> >Thread-Topic: Alternate SSL port
> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==> >X-WBNR-Posting-Host: 62.3.118.193
> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >Subject: Alternate SSL port
> >Date: Wed, 30 Mar 2005 08:47:08 -0800
> >Lines: 4
> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46483
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >Is it possible for Reporting Services with SP1 to use a port other than
> 443
> >for SSL? Our web server already has a web site running on port 443 which
> we
> >can't move.
> >
> >
>|||Hi Paul,
It seems that we'll still need to make two changes in the config files.
- UrlRoot entry in the RSReportServer.config
- ReportServerUrl entry in the RSWebApplication.config
Change these entries to be https://YourReportServerName:4445/ReportServer
Replace YourReportServerName with your server's name.
After that, type https://YourReportServerName:4445/ReportServer to see if
you can access the report server and then try to access the report manager.
Feel free to let me know if it works.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Alternate SSL port
>thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==>X-WBNR-Posting-Host: 62.3.118.193
>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
<x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Alternate SSL port
>Date: Thu, 31 Mar 2005 08:03:02 -0800
>Lines: 61
>Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46590
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>William,
>I tried changing the SSL port in the default web site to 4445 and I ran
>rsactive again. However the links from
>http://dps-01/reports/Pages/Folder.aspx to the https pages, such as 'New
Data
>Source' do not have port 4445 added so they fail. How do I configure
>Reporting Services to use this port?
>Paul
>"William Wang[MSFT]" wrote:
>> Yes, you can navigate to the Web Site tab of the Default web site
>> properties page to change the port.
>> Also note that if you enable SSL after setup is run, make sure that the
>> SecureConnectionLevel in the configuration file (RSReportServer.config)
is
>> modified from 2 to 3.
>> Sincerely,
>> William Wang
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>> --
>> >Thread-Topic: Alternate SSL port
>> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>> >X-WBNR-Posting-Host: 62.3.118.193
>> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >Subject: Alternate SSL port
>> >Date: Wed, 30 Mar 2005 08:47:08 -0800
>> >Lines: 4
>> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.sqlserver.reportingsvcs:46483
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >Is it possible for Reporting Services with SP1 to use a port other than
>> 443
>> >for SSL? Our web server already has a web site running on port 443
which
>> we
>> >can't move.
>> >
>> >
>>
>|||William,
Thanks for the new information it help a lot. I have made the changes you
suggested and we are making progress. Navigating to
https://fqdn:4445/reportserver prompts for credentials and then shows the
page as expected. However, navigating to https://fqdn:4445/reports takes a
long time and finally shows a page with a 'The underlying connection was
closed: An unexpected error occurred on a receive.' error.
Hopefully you will have some ideas on this error as well...
Paul
"William Wang[MSFT]" wrote:
> Hi Paul,
> It seems that we'll still need to make two changes in the config files.
> - UrlRoot entry in the RSReportServer.config
> - ReportServerUrl entry in the RSWebApplication.config
> Change these entries to be https://YourReportServerName:4445/ReportServer
> Replace YourReportServerName with your server's name.
> After that, type https://YourReportServerName:4445/ReportServer to see if
> you can access the report server and then try to access the report manager.
> Feel free to let me know if it works.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> >Thread-Topic: Alternate SSL port
> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==> >X-WBNR-Posting-Host: 62.3.118.193
> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> >Subject: RE: Alternate SSL port
> >Date: Thu, 31 Mar 2005 08:03:02 -0800
> >Lines: 61
> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46590
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >William,
> >
> >I tried changing the SSL port in the default web site to 4445 and I ran
> >rsactive again. However the links from
> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as 'New
> Data
> >Source' do not have port 4445 added so they fail. How do I configure
> >Reporting Services to use this port?
> >
> >Paul
> >
> >"William Wang[MSFT]" wrote:
> >
> >> Yes, you can navigate to the Web Site tab of the Default web site
> >> properties page to change the port.
> >>
> >> Also note that if you enable SSL after setup is run, make sure that the
> >> SecureConnectionLevel in the configuration file (RSReportServer.config)
> is
> >> modified from 2 to 3.
> >>
> >> Sincerely,
> >>
> >> William Wang
> >> Microsoft Online Partner Support
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >>
> >> --
> >> >Thread-Topic: Alternate SSL port
> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >Subject: Alternate SSL port
> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
> >> >Lines: 4
> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA03.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:46483
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >
> >> >Is it possible for Reporting Services with SP1 to use a port other than
> >> 443
> >> >for SSL? Our web server already has a web site running on port 443
> which
> >> we
> >> >can't move.
> >> >
> >> >
> >>
> >>
> >
>|||Hi Paul,
I've got the same result as yours. In addition, if I use the default port
for SSL, I can access the Report Manager and Report Server without any
problem. It seems that Report Manager is not designed to be used with SSL
with non-default port. I will perform further research on it and will
update you once I have more information.
Regarding your situation, is it applicable for you to install RS on the
existing web site that has SSL enabled with default port?
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Alternate SSL port
>thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==>X-WBNR-Posting-Host: 62.3.118.193
>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
<x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
<B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
<6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Alternate SSL port
>Date: Sun, 3 Apr 2005 07:01:02 -0700
>Lines: 135
>Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46816
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>William,
>Thanks for the new information it help a lot. I have made the changes you
>suggested and we are making progress. Navigating to
>https://fqdn:4445/reportserver prompts for credentials and then shows the
>page as expected. However, navigating to https://fqdn:4445/reports takes a
>long time and finally shows a page with a 'The underlying connection was
>closed: An unexpected error occurred on a receive.' error.
>Hopefully you will have some ideas on this error as well...
>Paul
>"William Wang[MSFT]" wrote:
>> Hi Paul,
>> It seems that we'll still need to make two changes in the config files.
>> - UrlRoot entry in the RSReportServer.config
>> - ReportServerUrl entry in the RSWebApplication.config
>> Change these entries to be https://YourReportServerName:4445/ReportServer
>> Replace YourReportServerName with your server's name.
>> After that, type https://YourReportServerName:4445/ReportServer to see
if
>> you can access the report server and then try to access the report
manager.
>> Feel free to let me know if it works.
>> Sincerely,
>> William Wang
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>> --
>> >Thread-Topic: Alternate SSL port
>> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==>> >X-WBNR-Posting-Host: 62.3.118.193
>> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> >Subject: RE: Alternate SSL port
>> >Date: Thu, 31 Mar 2005 08:03:02 -0800
>> >Lines: 61
>> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.sqlserver.reportingsvcs:46590
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >William,
>> >
>> >I tried changing the SSL port in the default web site to 4445 and I ran
>> >rsactive again. However the links from
>> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as
'New
>> Data
>> >Source' do not have port 4445 added so they fail. How do I configure
>> >Reporting Services to use this port?
>> >
>> >Paul
>> >
>> >"William Wang[MSFT]" wrote:
>> >
>> >> Yes, you can navigate to the Web Site tab of the Default web site
>> >> properties page to change the port.
>> >>
>> >> Also note that if you enable SSL after setup is run, make sure that
the
>> >> SecureConnectionLevel in the configuration file
(RSReportServer.config)
>> is
>> >> modified from 2 to 3.
>> >>
>> >> Sincerely,
>> >>
>> >> William Wang
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your newsreader
so
>> >> that others may learn and benefit from your issue.
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >> --
>> >> >Thread-Topic: Alternate SSL port
>> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >Subject: Alternate SSL port
>> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
>> >> >Lines: 4
>> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> microsoft.public.sqlserver.reportingsvcs:46483
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >
>> >> >Is it possible for Reporting Services with SP1 to use a port other
than
>> >> 443
>> >> >for SSL? Our web server already has a web site running on port 443
>> which
>> >> we
>> >> >can't move.
>> >> >
>> >> >
>> >>
>> >>
>> >
>>
>|||William,
It's good that we are getting the same results. I have also tried going back
to the default SSL port and it works for me as well. Hopefully you can find a
solution to this problem; in the meantime I will try adding a secondary IP
address to my server and using port 443 for SSL bound to that one address for
Reporting Services.
Paul
"William Wang[MSFT]" wrote:
> Hi Paul,
> I've got the same result as yours. In addition, if I use the default port
> for SSL, I can access the Report Manager and Report Server without any
> problem. It seems that Report Manager is not designed to be used with SSL
> with non-default port. I will perform further research on it and will
> update you once I have more information.
> Regarding your situation, is it applicable for you to install RS on the
> existing web site that has SSL enabled with default port?
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> >Thread-Topic: Alternate SSL port
> >thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==> >X-WBNR-Posting-Host: 62.3.118.193
> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
> >Subject: RE: Alternate SSL port
> >Date: Sun, 3 Apr 2005 07:01:02 -0700
> >Lines: 135
> >Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.reportingsvcs:46816
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >William,
> >
> >Thanks for the new information it help a lot. I have made the changes you
> >suggested and we are making progress. Navigating to
> >https://fqdn:4445/reportserver prompts for credentials and then shows the
> >page as expected. However, navigating to https://fqdn:4445/reports takes a
> >long time and finally shows a page with a 'The underlying connection was
> >closed: An unexpected error occurred on a receive.' error.
> >
> >Hopefully you will have some ideas on this error as well...
> >
> >Paul
> >
> >"William Wang[MSFT]" wrote:
> >
> >> Hi Paul,
> >>
> >> It seems that we'll still need to make two changes in the config files.
> >>
> >> - UrlRoot entry in the RSReportServer.config
> >> - ReportServerUrl entry in the RSWebApplication.config
> >>
> >> Change these entries to be https://YourReportServerName:4445/ReportServer
> >>
> >> Replace YourReportServerName with your server's name.
> >>
> >> After that, type https://YourReportServerName:4445/ReportServer to see
> if
> >> you can access the report server and then try to access the report
> manager.
> >>
> >> Feel free to let me know if it works.
> >>
> >> Sincerely,
> >>
> >> William Wang
> >> Microsoft Online Partner Support
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >>
> >> --
> >> >Thread-Topic: Alternate SSL port
> >> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> >> >Subject: RE: Alternate SSL port
> >> >Date: Thu, 31 Mar 2005 08:03:02 -0800
> >> >Lines: 61
> >> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA03.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:46590
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >
> >> >William,
> >> >
> >> >I tried changing the SSL port in the default web site to 4445 and I ran
> >> >rsactive again. However the links from
> >> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as
> 'New
> >> Data
> >> >Source' do not have port 4445 added so they fail. How do I configure
> >> >Reporting Services to use this port?
> >> >
> >> >Paul
> >> >
> >> >"William Wang[MSFT]" wrote:
> >> >
> >> >> Yes, you can navigate to the Web Site tab of the Default web site
> >> >> properties page to change the port.
> >> >>
> >> >> Also note that if you enable SSL after setup is run, make sure that
> the
> >> >> SecureConnectionLevel in the configuration file
> (RSReportServer.config)
> >> is
> >> >> modified from 2 to 3.
> >> >>
> >> >> Sincerely,
> >> >>
> >> >> William Wang
> >> >> Microsoft Online Partner Support
> >> >>
> >> >> When responding to posts, please "Reply to Group" via your newsreader
> so
> >> >> that others may learn and benefit from your issue.
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> >>
> >> >> --
> >> >> >Thread-Topic: Alternate SSL port
> >> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==> >> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >> >Subject: Alternate SSL port
> >> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
> >> >> >Lines: 4
> >> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> >> >MIME-Version: 1.0
> >> >> >Content-Type: text/plain;
> >> >> > charset="Utf-8"
> >> >> >Content-Transfer-Encoding: 7bit
> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >> >Content-Class: urn:content-classes:message
> >> >> >Importance: normal
> >> >> >Priority: normal
> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
> >> microsoft.public.sqlserver.reportingsvcs:46483
> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >> >
> >> >> >Is it possible for Reporting Services with SP1 to use a port other
> than
> >> >> 443
> >> >> >for SSL? Our web server already has a web site running on port 443
> >> which
> >> >> we
> >> >> >can't move.
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >>
> >>
> >
>|||Hi Paul
I'm still researching this issue. I will get back to you as soon as I have
more information.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Alternate SSL port
>thread-index: AcU5c2R+j/f5lpFqQmiEGRiHesM1NQ==>X-WBNR-Posting-Host: 62.3.118.193
>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
<x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
<B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
<6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
<4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
<gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Alternate SSL port
>Date: Mon, 4 Apr 2005 17:07:02 -0700
>Lines: 208
>Message-ID: <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40030
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>William,
>It's good that we are getting the same results. I have also tried going
back
>to the default SSL port and it works for me as well. Hopefully you can
find a
>solution to this problem; in the meantime I will try adding a secondary IP
>address to my server and using port 443 for SSL bound to that one address
for
>Reporting Services.
>Paul
>"William Wang[MSFT]" wrote:
>> Hi Paul,
>> I've got the same result as yours. In addition, if I use the default
port
>> for SSL, I can access the Report Manager and Report Server without any
>> problem. It seems that Report Manager is not designed to be used with
SSL
>> with non-default port. I will perform further research on it and will
>> update you once I have more information.
>> Regarding your situation, is it applicable for you to install RS on the
>> existing web site that has SSL enabled with default port?
>> Sincerely,
>> William Wang
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>> --
>> >Thread-Topic: Alternate SSL port
>> >thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==>> >X-WBNR-Posting-Host: 62.3.118.193
>> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>> >Subject: RE: Alternate SSL port
>> >Date: Sun, 3 Apr 2005 07:01:02 -0700
>> >Lines: 135
>> >Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.sqlserver.reportingsvcs:46816
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >William,
>> >
>> >Thanks for the new information it help a lot. I have made the changes
you
>> >suggested and we are making progress. Navigating to
>> >https://fqdn:4445/reportserver prompts for credentials and then shows
the
>> >page as expected. However, navigating to https://fqdn:4445/reports
takes a
>> >long time and finally shows a page with a 'The underlying connection
was
>> >closed: An unexpected error occurred on a receive.' error.
>> >
>> >Hopefully you will have some ideas on this error as well...
>> >
>> >Paul
>> >
>> >"William Wang[MSFT]" wrote:
>> >
>> >> Hi Paul,
>> >>
>> >> It seems that we'll still need to make two changes in the config
files.
>> >>
>> >> - UrlRoot entry in the RSReportServer.config
>> >> - ReportServerUrl entry in the RSWebApplication.config
>> >>
>> >> Change these entries to be
https://YourReportServerName:4445/ReportServer
>> >>
>> >> Replace YourReportServerName with your server's name.
>> >>
>> >> After that, type https://YourReportServerName:4445/ReportServer to
see
>> if
>> >> you can access the report server and then try to access the report
>> manager.
>> >>
>> >> Feel free to let me know if it works.
>> >>
>> >> Sincerely,
>> >>
>> >> William Wang
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your newsreader
so
>> >> that others may learn and benefit from your issue.
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >> --
>> >> >Thread-Topic: Alternate SSL port
>> >> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==>> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> >> >Subject: RE: Alternate SSL port
>> >> >Date: Thu, 31 Mar 2005 08:03:02 -0800
>> >> >Lines: 61
>> >> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> microsoft.public.sqlserver.reportingsvcs:46590
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >
>> >> >William,
>> >> >
>> >> >I tried changing the SSL port in the default web site to 4445 and I
ran
>> >> >rsactive again. However the links from
>> >> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as
>> 'New
>> >> Data
>> >> >Source' do not have port 4445 added so they fail. How do I configure
>> >> >Reporting Services to use this port?
>> >> >
>> >> >Paul
>> >> >
>> >> >"William Wang[MSFT]" wrote:
>> >> >
>> >> >> Yes, you can navigate to the Web Site tab of the Default web site
>> >> >> properties page to change the port.
>> >> >>
>> >> >> Also note that if you enable SSL after setup is run, make sure
that
>> the
>> >> >> SecureConnectionLevel in the configuration file
>> (RSReportServer.config)
>> >> is
>> >> >> modified from 2 to 3.
>> >> >>
>> >> >> Sincerely,
>> >> >>
>> >> >> William Wang
>> >> >> Microsoft Online Partner Support
>> >> >>
>> >> >> When responding to posts, please "Reply to Group" via your
newsreader
>> so
>> >> >> that others may learn and benefit from your issue.
>> >> >> This posting is provided "AS IS" with no warranties, and confers
no
>> >> rights.
>> >> >>
>> >> >> --
>> >> >> >Thread-Topic: Alternate SSL port
>> >> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>> >> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >> >Subject: Alternate SSL port
>> >> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
>> >> >> >Lines: 4
>> >> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> >> >MIME-Version: 1.0
>> >> >> >Content-Type: text/plain;
>> >> >> > charset="Utf-8"
>> >> >> >Content-Transfer-Encoding: 7bit
>> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> >Content-Class: urn:content-classes:message
>> >> >> >Importance: normal
>> >> >> >Priority: normal
>> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> >> microsoft.public.sqlserver.reportingsvcs:46483
>> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> >
>> >> >> >Is it possible for Reporting Services with SP1 to use a port
other
>> than
>> >> >> 443
>> >> >> >for SSL? Our web server already has a web site running on port
443
>> >> which
>> >> >> we
>> >> >> >can't move.
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >
>>
>|||Hi Paul,
Based on my research, there has not been a solution for this issue. I will
let the product team know this issue and if I got more information, I will
let you know.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>X-Tomcat-ID: 136009157
>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
<x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
<B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
<6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
<4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
<gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
<884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: v-rxwang@.online.microsoft.com (William Wang[MSFT])
>Organization: Microsoft
>Date: Tue, 05 Apr 2005 08:10:54 GMT
>Subject: RE: Alternate SSL port
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>Message-ID: <boYxDcbOFHA.3892@.TK2MSFTNGXA01.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>Lines: 257
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40047
>NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>Hi Paul
>I'm still researching this issue. I will get back to you as soon as I have
>more information.
>Sincerely,
>William Wang
>Microsoft Online Partner Support
>When responding to posts, please "Reply to Group" via your newsreader so
>that others may learn and benefit from your issue.
>=====================================================>Business-Critical Phone Support (BCPS) provides you with technical phone
>support at no charge during critical LAN outages or "business down"
>situations. This benefit is available 24 hours a day, 7 days a week to all
>Microsoft technology partners in the United States and Canada.
>This and other support options are available here:
>BCPS:
>https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
>Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>If you are outside the United States, please visit our International
>Support page:
>http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
>=====================================================>This posting is provided "AS IS" with no warranties, and confers no rights.
>--
>>Thread-Topic: Alternate SSL port
>>thread-index: AcU5c2R+j/f5lpFqQmiEGRiHesM1NQ==>>X-WBNR-Posting-Host: 62.3.118.193
>>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
><x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
><B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
><6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
><4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
><gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
>>Subject: RE: Alternate SSL port
>>Date: Mon, 4 Apr 2005 17:07:02 -0700
>>Lines: 208
>>Message-ID: <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40030
>>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>>William,
>>It's good that we are getting the same results. I have also tried going
>back
>>to the default SSL port and it works for me as well. Hopefully you can
>find a
>>solution to this problem; in the meantime I will try adding a secondary
IP
>>address to my server and using port 443 for SSL bound to that one address
>for
>>Reporting Services.
>>Paul
>>"William Wang[MSFT]" wrote:
>> Hi Paul,
>> I've got the same result as yours. In addition, if I use the default
>port
>> for SSL, I can access the Report Manager and Report Server without any
>> problem. It seems that Report Manager is not designed to be used with
>SSL
>> with non-default port. I will perform further research on it and will
>> update you once I have more information.
>> Regarding your situation, is it applicable for you to install RS on the
>> existing web site that has SSL enabled with default port?
>> Sincerely,
>> William Wang
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader
so
>> that others may learn and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no
>rights.
>> --
>> >Thread-Topic: Alternate SSL port
>> >thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==>> >X-WBNR-Posting-Host: 62.3.118.193
>> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>> >Subject: RE: Alternate SSL port
>> >Date: Sun, 3 Apr 2005 07:01:02 -0700
>> >Lines: 135
>> >Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl
>microsoft.public.sqlserver.reportingsvcs:46816
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >William,
>> >
>> >Thanks for the new information it help a lot. I have made the changes
>you
>> >suggested and we are making progress. Navigating to
>> >https://fqdn:4445/reportserver prompts for credentials and then shows
>the
>> >page as expected. However, navigating to https://fqdn:4445/reports
>takes a
>> >long time and finally shows a page with a 'The underlying connection
>was
>> >closed: An unexpected error occurred on a receive.' error.
>> >
>> >Hopefully you will have some ideas on this error as well...
>> >
>> >Paul
>> >
>> >"William Wang[MSFT]" wrote:
>> >
>> >> Hi Paul,
>> >>
>> >> It seems that we'll still need to make two changes in the config
>files.
>> >>
>> >> - UrlRoot entry in the RSReportServer.config
>> >> - ReportServerUrl entry in the RSWebApplication.config
>> >>
>> >> Change these entries to be
>https://YourReportServerName:4445/ReportServer
>> >>
>> >> Replace YourReportServerName with your server's name.
>> >>
>> >> After that, type https://YourReportServerName:4445/ReportServer to
>see
>> if
>> >> you can access the report server and then try to access the report
>> manager.
>> >>
>> >> Feel free to let me know if it works.
>> >>
>> >> Sincerely,
>> >>
>> >> William Wang
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your
newsreader
>so
>> >> that others may learn and benefit from your issue.
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >> --
>> >> >Thread-Topic: Alternate SSL port
>> >> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==>> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> >> >Subject: RE: Alternate SSL port
>> >> >Date: Thu, 31 Mar 2005 08:03:02 -0800
>> >> >Lines: 61
>> >> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> microsoft.public.sqlserver.reportingsvcs:46590
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >
>> >> >William,
>> >> >
>> >> >I tried changing the SSL port in the default web site to 4445 and I
>ran
>> >> >rsactive again. However the links from
>> >> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as
>> 'New
>> >> Data
>> >> >Source' do not have port 4445 added so they fail. How do I
configure
>> >> >Reporting Services to use this port?
>> >> >
>> >> >Paul
>> >> >
>> >> >"William Wang[MSFT]" wrote:
>> >> >
>> >> >> Yes, you can navigate to the Web Site tab of the Default web site
>> >> >> properties page to change the port.
>> >> >>
>> >> >> Also note that if you enable SSL after setup is run, make sure
>that
>> the
>> >> >> SecureConnectionLevel in the configuration file
>> (RSReportServer.config)
>> >> is
>> >> >> modified from 2 to 3.
>> >> >>
>> >> >> Sincerely,
>> >> >>
>> >> >> William Wang
>> >> >> Microsoft Online Partner Support
>> >> >>
>> >> >> When responding to posts, please "Reply to Group" via your
>newsreader
>> so
>> >> >> that others may learn and benefit from your issue.
>> >> >> This posting is provided "AS IS" with no warranties, and confers
>no
>> >> rights.
>> >> >>
>> >> >> --
>> >> >> >Thread-Topic: Alternate SSL port
>> >> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>> >> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >> >Subject: Alternate SSL port
>> >> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
>> >> >> >Lines: 4
>> >> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> >> >MIME-Version: 1.0
>> >> >> >Content-Type: text/plain;
>> >> >> > charset="Utf-8"
>> >> >> >Content-Transfer-Encoding: 7bit
>> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> >Content-Class: urn:content-classes:message
>> >> >> >Importance: normal
>> >> >> >Priority: normal
>> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> >> microsoft.public.sqlserver.reportingsvcs:46483
>> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> >
>> >> >> >Is it possible for Reporting Services with SP1 to use a port
>other
>> than
>> >> >> 443
>> >> >> >for SSL? Our web server already has a web site running on port
>443
>> >> which
>> >> >> we
>> >> >> >can't move.
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >
>>
>|||William,
Thank you for the update. For now we have taken the easy option and just
added an additional server to host Reporting Services.
Paul
"William Wang[MSFT]" wrote:
> Hi Paul,
> Based on my research, there has not been a solution for this issue. I will
> let the product team know this issue and if I got more information, I will
> let you know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> >X-Tomcat-ID: 136009157
> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
> <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
> <gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
> <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain
> >Content-Transfer-Encoding: 7bit
> >From: v-rxwang@.online.microsoft.com (William Wang[MSFT])
> >Organization: Microsoft
> >Date: Tue, 05 Apr 2005 08:10:54 GMT
> >Subject: RE: Alternate SSL port
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >Message-ID: <boYxDcbOFHA.3892@.TK2MSFTNGXA01.phx.gbl>
> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >Lines: 257
> >Path: TK2MSFTNGXA01.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40047
> >NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
> >
> >Hi Paul
> >
> >I'm still researching this issue. I will get back to you as soon as I have
> >more information.
> >
> >Sincerely,
> >
> >William Wang
> >Microsoft Online Partner Support
> >
> >When responding to posts, please "Reply to Group" via your newsreader so
> >that others may learn and benefit from your issue.
> >
> >=====================================================> >
> >Business-Critical Phone Support (BCPS) provides you with technical phone
> >support at no charge during critical LAN outages or "business down"
> >situations. This benefit is available 24 hours a day, 7 days a week to all
> >Microsoft technology partners in the United States and Canada.
> >
> >This and other support options are available here:
> >BCPS:
> >https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> >Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
> >
> >If you are outside the United States, please visit our International
> >Support page:
> >http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> >
> >=====================================================> >
> >This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >--
> >>Thread-Topic: Alternate SSL port
> >>thread-index: AcU5c2R+j/f5lpFqQmiEGRiHesM1NQ==> >>X-WBNR-Posting-Host: 62.3.118.193
> >>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> ><x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> ><B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> ><6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
> ><4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
> ><gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
> >>Subject: RE: Alternate SSL port
> >>Date: Mon, 4 Apr 2005 17:07:02 -0700
> >>Lines: 208
> >>Message-ID: <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="Utf-8"
> >>Content-Transfer-Encoding: 7bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>Content-Class: urn:content-classes:message
> >>Importance: normal
> >>Priority: normal
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40030
> >>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >>
> >>William,
> >>
> >>It's good that we are getting the same results. I have also tried going
> >back
> >>to the default SSL port and it works for me as well. Hopefully you can
> >find a
> >>solution to this problem; in the meantime I will try adding a secondary
> IP
> >>address to my server and using port 443 for SSL bound to that one address
> >for
> >>Reporting Services.
> >>
> >>Paul
> >>
> >>"William Wang[MSFT]" wrote:
> >>
> >> Hi Paul,
> >>
> >> I've got the same result as yours. In addition, if I use the default
> >port
> >> for SSL, I can access the Report Manager and Report Server without any
> >> problem. It seems that Report Manager is not designed to be used with
> >SSL
> >> with non-default port. I will perform further research on it and will
> >> update you once I have more information.
> >>
> >> Regarding your situation, is it applicable for you to install RS on the
> >> existing web site that has SSL enabled with default port?
> >>
> >> Sincerely,
> >>
> >> William Wang
> >> Microsoft Online Partner Support
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader
> so
> >> that others may learn and benefit from your issue.
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >rights.
> >>
> >> --
> >> >Thread-Topic: Alternate SSL port
> >> >thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> >> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> >> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
> >> >Subject: RE: Alternate SSL port
> >> >Date: Sun, 3 Apr 2005 07:01:02 -0700
> >> >Lines: 135
> >> >Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA03.phx.gbl
> >microsoft.public.sqlserver.reportingsvcs:46816
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >
> >> >William,
> >> >
> >> >Thanks for the new information it help a lot. I have made the changes
> >you
> >> >suggested and we are making progress. Navigating to
> >> >https://fqdn:4445/reportserver prompts for credentials and then shows
> >the
> >> >page as expected. However, navigating to https://fqdn:4445/reports
> >takes a
> >> >long time and finally shows a page with a 'The underlying connection
> >was
> >> >closed: An unexpected error occurred on a receive.' error.
> >> >
> >> >Hopefully you will have some ideas on this error as well...
> >> >
> >> >Paul
> >> >
> >> >"William Wang[MSFT]" wrote:
> >> >
> >> >> Hi Paul,
> >> >>
> >> >> It seems that we'll still need to make two changes in the config
> >files.
> >> >>
> >> >> - UrlRoot entry in the RSReportServer.config
> >> >> - ReportServerUrl entry in the RSWebApplication.config
> >> >>
> >> >> Change these entries to be
> >https://YourReportServerName:4445/ReportServer
> >> >>
> >> >> Replace YourReportServerName with your server's name.
> >> >>
> >> >> After that, type https://YourReportServerName:4445/ReportServer to
> >see
> >> if
> >> >> you can access the report server and then try to access the report
> >> manager.
> >> >>
> >> >> Feel free to let me know if it works.
> >> >>
> >> >> Sincerely,
> >> >>
> >> >> William Wang
> >> >> Microsoft Online Partner Support
> >> >>
> >> >> When responding to posts, please "Reply to Group" via your
> newsreader
> >so
> >> >> that others may learn and benefit from your issue.
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> >>
> >> >> --
> >> >> >Thread-Topic: Alternate SSL port
> >> >> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==> >> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
> >> >> >Subject: RE: Alternate SSL port
> >> >> >Date: Thu, 31 Mar 2005 08:03:02 -0800
> >> >> >Lines: 61
> >> >> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
> >> >> >MIME-Version: 1.0
> >> >> >Content-Type: text/plain;
> >> >> > charset="Utf-8"
> >> >> >Content-Transfer-Encoding: 7bit
> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >> >Content-Class: urn:content-classes:message
> >> >> >Importance: normal
> >> >> >Priority: normal
> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
> >> microsoft.public.sqlserver.reportingsvcs:46590
> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >> >
> >> >> >William,
> >> >> >
> >> >> >I tried changing the SSL port in the default web site to 4445 and I
> >ran
> >> >> >rsactive again. However the links from
> >> >> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such as
> >> 'New
> >> >> Data
> >> >> >Source' do not have port 4445 added so they fail. How do I
> configure
> >> >> >Reporting Services to use this port?
> >> >> >
> >> >> >Paul
> >> >> >
> >> >> >"William Wang[MSFT]" wrote:
> >> >> >
> >> >> >> Yes, you can navigate to the Web Site tab of the Default web site
> >> >> >> properties page to change the port.
> >> >> >>
> >> >> >> Also note that if you enable SSL after setup is run, make sure
> >that
> >> the
> >> >> >> SecureConnectionLevel in the configuration file
> >> (RSReportServer.config)
> >> >> is
> >> >> >> modified from 2 to 3.
> >> >> >>
> >> >> >> Sincerely,
> >> >> >>
> >> >> >> William Wang
> >> >> >> Microsoft Online Partner Support
> >> >> >>
> >> >> >> When responding to posts, please "Reply to Group" via your
> >newsreader
> >> so
> >> >> >> that others may learn and benefit from your issue.
> >> >> >> This posting is provided "AS IS" with no warranties, and confers
> >no
> >> >> rights.
> >> >> >>
> >> >> >> --
> >> >> >> >Thread-Topic: Alternate SSL port
> >> >> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==> >> >> >> >X-WBNR-Posting-Host: 62.3.118.193
> >> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
> >> >> >> >Subject: Alternate SSL port
> >> >> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
> >> >> >> >Lines: 4
> >> >> >> >Message-ID: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
> >> >> >> >MIME-Version: 1.0
> >> >> >> >Content-Type: text/plain;
> >> >> >> > charset="Utf-8"
> >> >> >> >Content-Transfer-Encoding: 7bit
> >> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >> >> >Content-Class: urn:content-classes:message
> >> >> >> >Importance: normal
> >> >> >> >Priority: normal
> >> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
> >> >> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
> >> >> microsoft.public.sqlserver.reportingsvcs:46483
> >> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >> >> >> >
> >> >> >> >Is it possible for Reporting Services with SP1 to use a port
> >other
> >> than
> >> >> >> 443
> >> >> >> >for SSL? Our web server already has a web site running on port
> >443
> >> >> which
> >> >> >> we
> >> >> >> >can't move.
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >
> >
>|||Great! I hope the community would benefit from our conversation.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Alternate SSL port
>thread-index: AcU/JHIP888TGhIxTkyiceyosaDDIw==>X-WBNR-Posting-Host: 62.3.118.193
>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
<x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
<B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
<6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
<4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
<gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
<884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
<boYxDcbOFHA.3892@.TK2MSFTNGXA01.phx.gbl>
<IqtSrjAPFHA.2944@.TK2MSFTNGXA01.phx.gbl>
>Subject: RE: Alternate SSL port
>Date: Mon, 11 Apr 2005 22:57:01 -0700
>Lines: 350
>Message-ID: <75372142-7508-4D7E-AF75-A3B800806F4E@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:40612
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>William,
>Thank you for the update. For now we have taken the easy option and just
>added an additional server to host Reporting Services.
>Paul
>"William Wang[MSFT]" wrote:
>> Hi Paul,
>> Based on my research, there has not been a solution for this issue. I
will
>> let the product team know this issue and if I got more information, I
will
>> let you know.
>> Sincerely,
>> William Wang
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>> --
>> >X-Tomcat-ID: 136009157
>> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>> <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>> <gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
>> <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain
>> >Content-Transfer-Encoding: 7bit
>> >From: v-rxwang@.online.microsoft.com (William Wang[MSFT])
>> >Organization: Microsoft
>> >Date: Tue, 05 Apr 2005 08:10:54 GMT
>> >Subject: RE: Alternate SSL port
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >Message-ID: <boYxDcbOFHA.3892@.TK2MSFTNGXA01.phx.gbl>
>> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >Lines: 257
>> >Path: TK2MSFTNGXA01.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sqlserver.reportingsvcs:40047
>> >NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>> >
>> >Hi Paul
>> >
>> >I'm still researching this issue. I will get back to you as soon as I
have
>> >more information.
>> >
>> >Sincerely,
>> >
>> >William Wang
>> >Microsoft Online Partner Support
>> >
>> >When responding to posts, please "Reply to Group" via your newsreader
so
>> >that others may learn and benefit from your issue.
>> >
>> >=====================================================>> >
>> >Business-Critical Phone Support (BCPS) provides you with technical
phone
>> >support at no charge during critical LAN outages or "business down"
>> >situations. This benefit is available 24 hours a day, 7 days a week to
all
>> >Microsoft technology partners in the United States and Canada.
>> >
>> >This and other support options are available here:
>> >BCPS:
>https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
>> >Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
>> >
>> >If you are outside the United States, please visit our International
>> >Support page:
>> >http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
>> >
>> >=====================================================>> >
>> >This posting is provided "AS IS" with no warranties, and confers no
rights.
>> >
>> >--
>> >>Thread-Topic: Alternate SSL port
>> >>thread-index: AcU5c2R+j/f5lpFqQmiEGRiHesM1NQ==>> >>X-WBNR-Posting-Host: 62.3.118.193
>> >>From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >>References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> ><x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> ><B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> ><6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>> ><4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>> ><gfeUjvPOFHA.1944@.TK2MSFTNGXA03.phx.gbl>
>> >>Subject: RE: Alternate SSL port
>> >>Date: Mon, 4 Apr 2005 17:07:02 -0700
>> >>Lines: 208
>> >>Message-ID: <884A6743-4551-4070-8B8C-2DAA04A8743D@.microsoft.com>
>> >>MIME-Version: 1.0
>> >>Content-Type: text/plain;
>> >> charset="Utf-8"
>> >>Content-Transfer-Encoding: 7bit
>> >>X-Newsreader: Microsoft CDO for Windows 2000
>> >>Content-Class: urn:content-classes:message
>> >>Importance: normal
>> >>Priority: normal
>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sqlserver.reportingsvcs:40030
>> >>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >>
>> >>William,
>> >>
>> >>It's good that we are getting the same results. I have also tried
going
>> >back
>> >>to the default SSL port and it works for me as well. Hopefully you can
>> >find a
>> >>solution to this problem; in the meantime I will try adding a
secondary
>> IP
>> >>address to my server and using port 443 for SSL bound to that one
address
>> >for
>> >>Reporting Services.
>> >>
>> >>Paul
>> >>
>> >>"William Wang[MSFT]" wrote:
>> >>
>> >> Hi Paul,
>> >>
>> >> I've got the same result as yours. In addition, if I use the default
>> >port
>> >> for SSL, I can access the Report Manager and Report Server without
any
>> >> problem. It seems that Report Manager is not designed to be used
with
>> >SSL
>> >> with non-default port. I will perform further research on it and
will
>> >> update you once I have more information.
>> >>
>> >> Regarding your situation, is it applicable for you to install RS on
the
>> >> existing web site that has SSL enabled with default port?
>> >>
>> >> Sincerely,
>> >>
>> >> William Wang
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your
newsreader
>> so
>> >> that others may learn and benefit from your issue.
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >rights.
>> >>
>> >> --
>> >> >Thread-Topic: Alternate SSL port
>> >> >thread-index: AcU4VZJHANEOJiaUREitCWTY4HF0Zw==>> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >References: <7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> >> <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> >> <6pLyPXqNFHA.2720@.TK2MSFTNGXA03.phx.gbl>
>> >> >Subject: RE: Alternate SSL port
>> >> >Date: Sun, 3 Apr 2005 07:01:02 -0700
>> >> >Lines: 135
>> >> >Message-ID: <4C3E45D0-31F2-4F5C-8F63-D8FD557270FC@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> >microsoft.public.sqlserver.reportingsvcs:46816
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >
>> >> >William,
>> >> >
>> >> >Thanks for the new information it help a lot. I have made the
changes
>> >you
>> >> >suggested and we are making progress. Navigating to
>> >> >https://fqdn:4445/reportserver prompts for credentials and then
shows
>> >the
>> >> >page as expected. However, navigating to https://fqdn:4445/reports
>> >takes a
>> >> >long time and finally shows a page with a 'The underlying
connection
>> >was
>> >> >closed: An unexpected error occurred on a receive.' error.
>> >> >
>> >> >Hopefully you will have some ideas on this error as well...
>> >> >
>> >> >Paul
>> >> >
>> >> >"William Wang[MSFT]" wrote:
>> >> >
>> >> >> Hi Paul,
>> >> >>
>> >> >> It seems that we'll still need to make two changes in the config
>> >files.
>> >> >>
>> >> >> - UrlRoot entry in the RSReportServer.config
>> >> >> - ReportServerUrl entry in the RSWebApplication.config
>> >> >>
>> >> >> Change these entries to be
>> >https://YourReportServerName:4445/ReportServer
>> >> >>
>> >> >> Replace YourReportServerName with your server's name.
>> >> >>
>> >> >> After that, type https://YourReportServerName:4445/ReportServer
to
>> >see
>> >> if
>> >> >> you can access the report server and then try to access the
report
>> >> manager.
>> >> >>
>> >> >> Feel free to let me know if it works.
>> >> >>
>> >> >> Sincerely,
>> >> >>
>> >> >> William Wang
>> >> >> Microsoft Online Partner Support
>> >> >>
>> >> >> When responding to posts, please "Reply to Group" via your
>> newsreader
>> >so
>> >> >> that others may learn and benefit from your issue.
>> >> >> This posting is provided "AS IS" with no warranties, and confers
no
>> >> rights.
>> >> >>
>> >> >> --
>> >> >> >Thread-Topic: Alternate SSL port
>> >> >> >thread-index: AcU2Cx2mhO0VVxPfStSdmJfFFOfRBg==>> >> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >> >References:
<7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> >> <x5BezxZNFHA.964@.TK2MSFTNGXA03.phx.gbl>
>> >> >> >Subject: RE: Alternate SSL port
>> >> >> >Date: Thu, 31 Mar 2005 08:03:02 -0800
>> >> >> >Lines: 61
>> >> >> >Message-ID: <B6C875C1-8A24-4E41-851A-9ACF87A6659E@.microsoft.com>
>> >> >> >MIME-Version: 1.0
>> >> >> >Content-Type: text/plain;
>> >> >> > charset="Utf-8"
>> >> >> >Content-Transfer-Encoding: 7bit
>> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> >Content-Class: urn:content-classes:message
>> >> >> >Importance: normal
>> >> >> >Priority: normal
>> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> >> microsoft.public.sqlserver.reportingsvcs:46590
>> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> >
>> >> >> >William,
>> >> >> >
>> >> >> >I tried changing the SSL port in the default web site to 4445
and I
>> >ran
>> >> >> >rsactive again. However the links from
>> >> >> >http://dps-01/reports/Pages/Folder.aspx to the https pages, such
as
>> >> 'New
>> >> >> Data
>> >> >> >Source' do not have port 4445 added so they fail. How do I
>> configure
>> >> >> >Reporting Services to use this port?
>> >> >> >
>> >> >> >Paul
>> >> >> >
>> >> >> >"William Wang[MSFT]" wrote:
>> >> >> >
>> >> >> >> Yes, you can navigate to the Web Site tab of the Default web
site
>> >> >> >> properties page to change the port.
>> >> >> >>
>> >> >> >> Also note that if you enable SSL after setup is run, make sure
>> >that
>> >> the
>> >> >> >> SecureConnectionLevel in the configuration file
>> >> (RSReportServer.config)
>> >> >> is
>> >> >> >> modified from 2 to 3.
>> >> >> >>
>> >> >> >> Sincerely,
>> >> >> >>
>> >> >> >> William Wang
>> >> >> >> Microsoft Online Partner Support
>> >> >> >>
>> >> >> >> When responding to posts, please "Reply to Group" via your
>> >newsreader
>> >> so
>> >> >> >> that others may learn and benefit from your issue.
>> >> >> >> This posting is provided "AS IS" with no warranties, and
confers
>> >no
>> >> >> rights.
>> >> >> >>
>> >> >> >> --
>> >> >> >> >Thread-Topic: Alternate SSL port
>> >> >> >> >thread-index: AcU1SBzZtdItkQP+SjOnux2ZxJciiA==>> >> >> >> >X-WBNR-Posting-Host: 62.3.118.193
>> >> >> >> >From: "=?Utf-8?B?UGF1bA==?=" <paul.collis@.newsgroup.nospam>
>> >> >> >> >Subject: Alternate SSL port
>> >> >> >> >Date: Wed, 30 Mar 2005 08:47:08 -0800
>> >> >> >> >Lines: 4
>> >> >> >> >Message-ID:
<7C334982-BCD6-498C-8DF8-75AD12306781@.microsoft.com>
>> >> >> >> >MIME-Version: 1.0
>> >> >> >> >Content-Type: text/plain;
>> >> >> >> > charset="Utf-8"
>> >> >> >> >Content-Transfer-Encoding: 7bit
>> >> >> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >> >> >Content-Class: urn:content-classes:message
>> >> >> >> >Importance: normal
>> >> >> >> >Priority: normal
>> >> >> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >> >> >> >Newsgroups: microsoft.public.sqlserver.reportingsvcs
>> >> >> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >> >> >Xref: TK2MSFTNGXA03.phx.gbl
>> >> >> microsoft.public.sqlserver.reportingsvcs:46483
>> >> >> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >> >> >> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >> >> >> >
>> >> >> >> >Is it possible for Reporting Services with SP1 to use a port
>> >other
>> >> than
>> >> >> >> 443
>> >> >> >> >for SSL? Our web server already has a web site running on
port
>> >443
>> >> >> which
>> >> >> >> we
>> >> >> >> >can't move.
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >
>> >
>>
>

Alter Index...Rebuild

Running SQL 2005, SP1
In migrating over to SQL 2005, we also took on a different indexing strategy,
going from DBCC DBREINDEX to ALTER INDEX...REBUILD.
There are a couple of things that are worrisome. A sample of the ALTER INDEX
statement I use is included at the end of this message. I only run this on
indexes that are fragmented as per sys.dm_db_index_physical_stats. The
following are the two items of concern.
1. The weekly ALTER INDEX takes longer to complete than the weekly DBCC
DBREINDEX. I have SORT_IN_TEMPDB = ON, but there is relatively little growth,
if any to TempDB. So I assume it may be done in memory. TempDB is on drive C,
a set of internal SCSI disks. The data and log files are on the SAN, spread
across 26 disks.
2. The data file growth is significant (sometimes the log files, but mostly
the data files) when running ALTER INDEX. As noted in concern 1,
SORT_IN_TEMPDB = ON, so I am perplexed why there is such growth on the data
files?
SAMPLE:
ALTER INDEX [name of index] ON [name of database].dbo.[name of table]
REBUILD WITH ( FILLFACTOR = 90, SORT_IN_TEMPDB = ON)
--
Message posted via http://www.sqlmonster.comWhen you rebuild an index with either DBREINDEX or ALTER INDEX REBUILD it
completely rebuilds the indexes (this includes the table if there is a
clustered index) by creating a new copy of them in the data file(s). This
means you need free space in the data files to hold the old and new indexes
at the same time. Only when it is completed does it drop the original
indexes. So you always need plenty of free space in the data files for
operations such as these. You have been around here long enough to know by
know you should ALWAYS have plenty of free space in the database files both
data & Log. If you are getting growth in the data files it sounds like you
shrunk it at some point. This is also a bad idea to shrink the files. The
SORT_IN_TEMPDB can help reduce time and some of the space needed in the data
files as it can serve as a work space to sort the indexes etc during the
processing. But it does not remove the need for the place to rebuild the
index itself. You say there is little growth to Tempdb during this process.
Well again if there is any growth you didn't size the files correctly to
begin with. Lack of growth of the files has nothing to do with how much work
they are performing. As long as there is room in the data files for what it
has to do there should be no growth. That is the proper and expected
behavior.
--
Andrew J. Kelly SQL MVP
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:7675a0e8fcb67@.uwe...
> Running SQL 2005, SP1
> In migrating over to SQL 2005, we also took on a different indexing
> strategy,
> going from DBCC DBREINDEX to ALTER INDEX...REBUILD.
> There are a couple of things that are worrisome. A sample of the ALTER
> INDEX
> statement I use is included at the end of this message. I only run this on
> indexes that are fragmented as per sys.dm_db_index_physical_stats. The
> following are the two items of concern.
> 1. The weekly ALTER INDEX takes longer to complete than the weekly DBCC
> DBREINDEX. I have SORT_IN_TEMPDB = ON, but there is relatively little
> growth,
> if any to TempDB. So I assume it may be done in memory. TempDB is on drive
> C,
> a set of internal SCSI disks. The data and log files are on the SAN,
> spread
> across 26 disks.
> 2. The data file growth is significant (sometimes the log files, but
> mostly
> the data files) when running ALTER INDEX. As noted in concern 1,
> SORT_IN_TEMPDB = ON, so I am perplexed why there is such growth on the
> data
> files?
> SAMPLE:
> ALTER INDEX [name of index] ON [name of database].dbo.[name of table]
> REBUILD WITH ( FILLFACTOR = 90, SORT_IN_TEMPDB = ON)
> --
> Message posted via http://www.sqlmonster.com
>