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.
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >
>> >
>>
>

altering columns performance issues

Good Day:
When altering column width in SQL2000SP3a we find that this is taking a long
running time on tables with many rows.
We are trying to alter some numeric (7,2) columns to numeric (8,3) and thus
the data should not need to be transformed, only the column altered.
There are some 20 million rows and some 200 columns that need this
alteration.
Any thoughts on how to speed this up?
We could create new tables and copy the data, but that requires all user
activity to be stopped, and that is not palatable.
I note that Oracle can do this sort of an alter instantly, for some reason.
THANKS
Mr. Lynn Teska
Mayo ClinicHi Lynn
I just wrote an article on ALTER TABLE for SQL Server Magazine, and why some
changes take a long time and other don't. Unfortunately, it won't appear
until January, so I'll give you a sneak preview.
You are right that the data doesn't need to be transformed, but I'm not sure
what you mean by 'only the column altered'. Yes, the column needs to be
altered, and in every single row in the table. For some changes, like
changing to a smaller datatype, only the metadata needs to be changed (but
the existing data does need to be validated to make sure it 'fits' into the
smaller type.)
If you alter a column's datatype to one that needs more storage space, SQL
Server will actually make the physical change to every row to allow the
additional bytes that are needed to store numeric(8,3).
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Lynn Teska" <lteska@.mayo.edu> wrote in message
news:OfwNwoknDHA.2628@.TK2MSFTNGP10.phx.gbl...
> Good Day:
> When altering column width in SQL2000SP3a we find that this is taking a
long
> running time on tables with many rows.
> We are trying to alter some numeric (7,2) columns to numeric (8,3) and
thus
> the data should not need to be transformed, only the column altered.
> There are some 20 million rows and some 200 columns that need this
> alteration.
> Any thoughts on how to speed this up?
> We could create new tables and copy the data, but that requires all user
> activity to be stopped, and that is not palatable.
> I note that Oracle can do this sort of an alter instantly, for some
reason.
> THANKS
> Mr. Lynn Teska
> Mayo Clinic
>|||In addition to Kalen's response:
Watch out if you use EM for this. EM generally creates a new table, copy the data etc etc instead of
executing an ALTER TABLE tblname ALTER COLUMN colname command.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Lynn Teska" <lteska@.mayo.edu> wrote in message news:OfwNwoknDHA.2628@.TK2MSFTNGP10.phx.gbl...
> Good Day:
> When altering column width in SQL2000SP3a we find that this is taking a long
> running time on tables with many rows.
> We are trying to alter some numeric (7,2) columns to numeric (8,3) and thus
> the data should not need to be transformed, only the column altered.
> There are some 20 million rows and some 200 columns that need this
> alteration.
> Any thoughts on how to speed this up?
> We could create new tables and copy the data, but that requires all user
> activity to be stopped, and that is not palatable.
> I note that Oracle can do this sort of an alter instantly, for some reason.
> THANKS
> Mr. Lynn Teska
> Mayo Clinic
>|||Good Day:
Well here is a hypothetical situation:
We have a 24x7x365 app with a particular table that has some 200
numeric(7,2) columns.
There are a number of other columns with constraints and indexes, but none
of the numeric (7,2) columns is indexed or constrained.
The applications store new data in the table every 1 minute, or thereabouts.
There are 25 Million rows in the table.
We need to widen all the numeric (7,2) columns to numeric (8,3).
We need to minimize or eliminate application outage.
SQL server is doing a huge amount of I/O to alter the columns.
SQL server appears to only be able to alter one column at a time.
Now when I add new columns SQL server is quick as you please.
What strategy would this group think best to accomplish the task of widening
the columns?
Thanks for any insight!
Lynn Teska
Mayo Clinic
--
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eyk5vqrnDHA.688@.TK2MSFTNGP10.phx.gbl...
> In addition to Kalen's response:
> Watch out if you use EM for this. EM generally creates a new table, copy
the data etc etc instead of
> executing an ALTER TABLE tblname ALTER COLUMN colname command.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Lynn Teska" <lteska@.mayo.edu> wrote in message
news:OfwNwoknDHA.2628@.TK2MSFTNGP10.phx.gbl...
> > Good Day:
> >
> > When altering column width in SQL2000SP3a we find that this is taking a
long
> > running time on tables with many rows.
> > We are trying to alter some numeric (7,2) columns to numeric (8,3) and
thus
> > the data should not need to be transformed, only the column altered.
> > There are some 20 million rows and some 200 columns that need this
> > alteration.
> >
> > Any thoughts on how to speed this up?
> > We could create new tables and copy the data, but that requires all user
> > activity to be stopped, and that is not palatable.
> >
> > I note that Oracle can do this sort of an alter instantly, for some
reason.
> >
> > THANKS
> > Mr. Lynn Teska
> > Mayo Clinic
> >
> >
>|||Hi Lynn,
I would like to thank Kalen and Tibor for their help. As I understand, you
want to widen all the numeric (7,2) columns to numeric (8,3) in the table
on the machine. If I have misunderstood, please feel free to let me know.
To change the schema of the table, we can perform SQL statements using
Query Analyzer or Change the table schema directly in SQL Server Enterprise
Manager. Because Enterprise Manager will create a new tale and drop the
original table for changing the schema, I think it is better to use Query
Analyzer with ALTER TABLE statement.
Example:
alter table <table name> alter column <column name> numeric(8,3)
For additional information regarding ALTER TABLE, please refer to the
following article on SQL Server Books Online.
Topic: "ALTER TABLE"
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||I understand how to do the task with the EM or TSQL.
The problem is the time it takes with 25 million rows is not acceptable in
at 24x7x365 system.
TSQL can only alter one column at a time, and with 200 columns to do that is
not so good.
EM makes copies as you note and that is not efficient in terms of disk i/o.
I am trying to get a strategy that will minimize or eliminate down time and
blocking of the table.
Interestingly Oracle can do this sort of alteration instantly, according to
our vendor.
Thanks
Lynn Teska
Mayo Clinic
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> Hi Lynn,
> I would like to thank Kalen and Tibor for their help. As I understand, you
> want to widen all the numeric (7,2) columns to numeric (8,3) in the table
> on the machine. If I have misunderstood, please feel free to let me know.
> To change the schema of the table, we can perform SQL statements using
> Query Analyzer or Change the table schema directly in SQL Server
Enterprise
> Manager. Because Enterprise Manager will create a new tale and drop the
> original table for changing the schema, I think it is better to use Query
> Analyzer with ALTER TABLE statement.
> Example:
> alter table <table name> alter column <column name> numeric(8,3)
> For additional information regarding ALTER TABLE, please refer to the
> following article on SQL Server Books Online.
> Topic: "ALTER TABLE"
> Please feel free to post in the group if this solves your problem or if
you
> would like further assistance.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Lynn
The vendors says Oracle can do this instantly, but you've never tried it
yourself?
I wouldn't be surprised if a SQL Server vendor said SQL Server could do it
instantly too, that's why you come to a Technical forum to find out. Have
you asked this on an Oracle Technical forum?
As I mentioned, there are some kinds of ALTER TABLEs that can be done
instantly, and there is a lot of confusion, so someone who had not
researched this issue in technical detail could easily tell you that this
was an instantaneous operation, even on SQL Server.
You are wanting to physically change 25 million rows? How could this
possible be an instantaneous operation?
One faster way you might consider is to create a new table using select
into, which is a very fast command, and then dropping the old table, and
renaming the new one to the old name.
SELECT convert(numeric(8,3), col1) as col1, convert(newdatatype, col2) as
col2 ...
INTO newtable
FROM original_table
GO
--recreate constraints, indexes etc on newtable
DROP original_table
EXEC sp_rename newtable, original_table
Good Luck!
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Lynn Teska" <lteska@.mayo.edu> wrote in message
news:#HIbWl9nDHA.2064@.TK2MSFTNGP11.phx.gbl...
> I understand how to do the task with the EM or TSQL.
> The problem is the time it takes with 25 million rows is not acceptable in
> at 24x7x365 system.
> TSQL can only alter one column at a time, and with 200 columns to do that
is
> not so good.
> EM makes copies as you note and that is not efficient in terms of disk
i/o.
> I am trying to get a strategy that will minimize or eliminate down time
and
> blocking of the table.
> Interestingly Oracle can do this sort of alteration instantly, according
to
> our vendor.
> Thanks
> Lynn Teska
> Mayo Clinic
>
> "Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
> news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> > Hi Lynn,
> >
> > I would like to thank Kalen and Tibor for their help. As I understand,
you
> > want to widen all the numeric (7,2) columns to numeric (8,3) in the
table
> > on the machine. If I have misunderstood, please feel free to let me
know.
> >
> > To change the schema of the table, we can perform SQL statements using
> > Query Analyzer or Change the table schema directly in SQL Server
> Enterprise
> > Manager. Because Enterprise Manager will create a new tale and drop the
> > original table for changing the schema, I think it is better to use
Query
> > Analyzer with ALTER TABLE statement.
> >
> > Example:
> >
> > alter table <table name> alter column <column name> numeric(8,3)
> >
> > For additional information regarding ALTER TABLE, please refer to the
> > following article on SQL Server Books Online.
> > Topic: "ALTER TABLE"
> >
> > Please feel free to post in the group if this solves your problem or if
> you
> > would like further assistance.
> >
> > Regards,
> >
> > Michael Shao
> > Microsoft Online Partner Support
> > Get Secure! - www.microsoft.com/security
> > This posting is provided "as is" with no warranties and confers no
rights.
> >
>|||Thanks for the info.
The vended product runs on both SQL server and Oracle, I have no reason to
doubt that the change is fast on Oracle.
They seem to be experienced in both platforms.
Thanks for your suggestion I will have a look at it.
Lynn Teska
PS:
This is an expert of a note I received from an Oracle expert:
Oracle always reserves a minimum of space in every database block for
updates, determined by the PCTFREE parameter (10% of the block size by
default, which we don't modify). Hence, Oracle does not have to reserve any
extra space, it's already there. Initially the old rows will surely fit
inside the new definition, as we have just widened the columns. If some
value needs some extra space, it will use the PCTFREE space. If this is not
enough, a phenomenon called row chaining will take place, as part of the row
will have to be stored in another block, and this is not so good for
performance, but it can be attacked later on. In our case this would never
happen as we won't go updating old values.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:OJjcZz9nDHA.2820@.TK2MSFTNGP10.phx.gbl...
> Lynn
> The vendors says Oracle can do this instantly, but you've never tried it
> yourself?
> I wouldn't be surprised if a SQL Server vendor said SQL Server could do it
> instantly too, that's why you come to a Technical forum to find out. Have
> you asked this on an Oracle Technical forum?
> As I mentioned, there are some kinds of ALTER TABLEs that can be done
> instantly, and there is a lot of confusion, so someone who had not
> researched this issue in technical detail could easily tell you that this
> was an instantaneous operation, even on SQL Server.
> You are wanting to physically change 25 million rows? How could this
> possible be an instantaneous operation?
> One faster way you might consider is to create a new table using select
> into, which is a very fast command, and then dropping the old table, and
> renaming the new one to the old name.
> SELECT convert(numeric(8,3), col1) as col1, convert(newdatatype, col2) as
> col2 ...
> INTO newtable
> FROM original_table
> GO
> --recreate constraints, indexes etc on newtable
> DROP original_table
> EXEC sp_rename newtable, original_table
> Good Luck!
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Lynn Teska" <lteska@.mayo.edu> wrote in message
> news:#HIbWl9nDHA.2064@.TK2MSFTNGP11.phx.gbl...
> > I understand how to do the task with the EM or TSQL.
> > The problem is the time it takes with 25 million rows is not acceptable
in
> > at 24x7x365 system.
> >
> > TSQL can only alter one column at a time, and with 200 columns to do
that
> is
> > not so good.
> > EM makes copies as you note and that is not efficient in terms of disk
> i/o.
> > I am trying to get a strategy that will minimize or eliminate down time
> and
> > blocking of the table.
> >
> > Interestingly Oracle can do this sort of alteration instantly, according
> to
> > our vendor.
> >
> > Thanks
> >
> > Lynn Teska
> > Mayo Clinic
> >
> >
> > "Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
> > news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> > > Hi Lynn,
> > >
> > > I would like to thank Kalen and Tibor for their help. As I understand,
> you
> > > want to widen all the numeric (7,2) columns to numeric (8,3) in the
> table
> > > on the machine. If I have misunderstood, please feel free to let me
> know.
> > >
> > > To change the schema of the table, we can perform SQL statements using
> > > Query Analyzer or Change the table schema directly in SQL Server
> > Enterprise
> > > Manager. Because Enterprise Manager will create a new tale and drop
the
> > > original table for changing the schema, I think it is better to use
> Query
> > > Analyzer with ALTER TABLE statement.
> > >
> > > Example:
> > >
> > > alter table <table name> alter column <column name> numeric(8,3)
> > >
> > > For additional information regarding ALTER TABLE, please refer to the
> > > following article on SQL Server Books Online.
> > > Topic: "ALTER TABLE"
> > >
> > > Please feel free to post in the group if this solves your problem or
if
> > you
> > > would like further assistance.
> > >
> > > Regards,
> > >
> > > Michael Shao
> > > Microsoft Online Partner Support
> > > Get Secure! - www.microsoft.com/security
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > >
> >
> >
>|||All the more interesting since numeric (7,2) and numeric (8,3) both appear
to be stored in 5 bytes.
Lynn
--
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:OJjcZz9nDHA.2820@.TK2MSFTNGP10.phx.gbl...
> Lynn
> The vendors says Oracle can do this instantly, but you've never tried it
> yourself?
> I wouldn't be surprised if a SQL Server vendor said SQL Server could do it
> instantly too, that's why you come to a Technical forum to find out. Have
> you asked this on an Oracle Technical forum?
> As I mentioned, there are some kinds of ALTER TABLEs that can be done
> instantly, and there is a lot of confusion, so someone who had not
> researched this issue in technical detail could easily tell you that this
> was an instantaneous operation, even on SQL Server.
> You are wanting to physically change 25 million rows? How could this
> possible be an instantaneous operation?
> One faster way you might consider is to create a new table using select
> into, which is a very fast command, and then dropping the old table, and
> renaming the new one to the old name.
> SELECT convert(numeric(8,3), col1) as col1, convert(newdatatype, col2) as
> col2 ...
> INTO newtable
> FROM original_table
> GO
> --recreate constraints, indexes etc on newtable
> DROP original_table
> EXEC sp_rename newtable, original_table
> Good Luck!
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Lynn Teska" <lteska@.mayo.edu> wrote in message
> news:#HIbWl9nDHA.2064@.TK2MSFTNGP11.phx.gbl...
> > I understand how to do the task with the EM or TSQL.
> > The problem is the time it takes with 25 million rows is not acceptable
in
> > at 24x7x365 system.
> >
> > TSQL can only alter one column at a time, and with 200 columns to do
that
> is
> > not so good.
> > EM makes copies as you note and that is not efficient in terms of disk
> i/o.
> > I am trying to get a strategy that will minimize or eliminate down time
> and
> > blocking of the table.
> >
> > Interestingly Oracle can do this sort of alteration instantly, according
> to
> > our vendor.
> >
> > Thanks
> >
> > Lynn Teska
> > Mayo Clinic
> >
> >
> > "Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
> > news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> > > Hi Lynn,
> > >
> > > I would like to thank Kalen and Tibor for their help. As I understand,
> you
> > > want to widen all the numeric (7,2) columns to numeric (8,3) in the
> table
> > > on the machine. If I have misunderstood, please feel free to let me
> know.
> > >
> > > To change the schema of the table, we can perform SQL statements using
> > > Query Analyzer or Change the table schema directly in SQL Server
> > Enterprise
> > > Manager. Because Enterprise Manager will create a new tale and drop
the
> > > original table for changing the schema, I think it is better to use
> Query
> > > Analyzer with ALTER TABLE statement.
> > >
> > > Example:
> > >
> > > alter table <table name> alter column <column name> numeric(8,3)
> > >
> > > For additional information regarding ALTER TABLE, please refer to the
> > > following article on SQL Server Books Online.
> > > Topic: "ALTER TABLE"
> > >
> > > Please feel free to post in the group if this solves your problem or
if
> > you
> > > would like further assistance.
> > >
> > > Regards,
> > >
> > > Michael Shao
> > > Microsoft Online Partner Support
> > > Get Secure! - www.microsoft.com/security
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > >
> >
> >
>|||Yes, there does appear to be some unexpected behavior going on. I am still
researching this issue.
OTOH, I have just learned that although you are correct, that Oracle does
make this change and all ALTER TABLE changes instantly, as only a metadata
change, the tradeoff is that actual row size adjustment must be made during
actual data use. In fact, if you change the datatype size to something very
different, or smaller, like char(5) to char(3) or char to int, Oracle will
not do any validation at the time of the alter table, but will wait until
your read the row. So you can end up getting conversion errors just by
reading data, which can be very problematic.
So, like many choices, there is a tradeoff. Normally, since altering tables
is a rare occurance, but updating and modifying data is done during
production operations, I'd rather the overhead was accrued during the alter,
when I can plan for it.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Lynn Teska" <lteska@.mayo.edu> wrote in message
news:#Nl5XwioDHA.2488@.TK2MSFTNGP12.phx.gbl...
> All the more interesting since numeric (7,2) and numeric (8,3) both appear
> to be stored in 5 bytes.
> Lynn
> --
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:OJjcZz9nDHA.2820@.TK2MSFTNGP10.phx.gbl...
> > Lynn
> >
> > The vendors says Oracle can do this instantly, but you've never tried it
> > yourself?
> >
> > I wouldn't be surprised if a SQL Server vendor said SQL Server could do
it
> > instantly too, that's why you come to a Technical forum to find out.
Have
> > you asked this on an Oracle Technical forum?
> >
> > As I mentioned, there are some kinds of ALTER TABLEs that can be done
> > instantly, and there is a lot of confusion, so someone who had not
> > researched this issue in technical detail could easily tell you that
this
> > was an instantaneous operation, even on SQL Server.
> >
> > You are wanting to physically change 25 million rows? How could this
> > possible be an instantaneous operation?
> >
> > One faster way you might consider is to create a new table using select
> > into, which is a very fast command, and then dropping the old table, and
> > renaming the new one to the old name.
> >
> > SELECT convert(numeric(8,3), col1) as col1, convert(newdatatype, col2)
as
> > col2 ...
> > INTO newtable
> > FROM original_table
> > GO
> >
> > --recreate constraints, indexes etc on newtable
> >
> > DROP original_table
> >
> > EXEC sp_rename newtable, original_table
> >
> > Good Luck!
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "Lynn Teska" <lteska@.mayo.edu> wrote in message
> > news:#HIbWl9nDHA.2064@.TK2MSFTNGP11.phx.gbl...
> > > I understand how to do the task with the EM or TSQL.
> > > The problem is the time it takes with 25 million rows is not
acceptable
> in
> > > at 24x7x365 system.
> > >
> > > TSQL can only alter one column at a time, and with 200 columns to do
> that
> > is
> > > not so good.
> > > EM makes copies as you note and that is not efficient in terms of disk
> > i/o.
> > > I am trying to get a strategy that will minimize or eliminate down
time
> > and
> > > blocking of the table.
> > >
> > > Interestingly Oracle can do this sort of alteration instantly,
according
> > to
> > > our vendor.
> > >
> > > Thanks
> > >
> > > Lynn Teska
> > > Mayo Clinic
> > >
> > >
> > > "Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
> > > news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> > > > Hi Lynn,
> > > >
> > > > I would like to thank Kalen and Tibor for their help. As I
understand,
> > you
> > > > want to widen all the numeric (7,2) columns to numeric (8,3) in the
> > table
> > > > on the machine. If I have misunderstood, please feel free to let me
> > know.
> > > >
> > > > To change the schema of the table, we can perform SQL statements
using
> > > > Query Analyzer or Change the table schema directly in SQL Server
> > > Enterprise
> > > > Manager. Because Enterprise Manager will create a new tale and drop
> the
> > > > original table for changing the schema, I think it is better to use
> > Query
> > > > Analyzer with ALTER TABLE statement.
> > > >
> > > > Example:
> > > >
> > > > alter table <table name> alter column <column name> numeric(8,3)
> > > >
> > > > For additional information regarding ALTER TABLE, please refer to
the
> > > > following article on SQL Server Books Online.
> > > > Topic: "ALTER TABLE"
> > > >
> > > > Please feel free to post in the group if this solves your problem or
> if
> > > you
> > > > would like further assistance.
> > > >
> > > > Regards,
> > > >
> > > > Michael Shao
> > > > Microsoft Online Partner Support
> > > > Get Secure! - www.microsoft.com/security
> > > > This posting is provided "as is" with no warranties and confers no
> > rights.
> > > >
> > >
> > >
> >
> >
>|||OK Thanks.
Let me know what you find.
A 4 hour outage is not a plus for us.
Thanks
Lynn Teska
--
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%23Jo3UejoDHA.3040@.TK2MSFTNGP11.phx.gbl...
> Yes, there does appear to be some unexpected behavior going on. I am still
> researching this issue.
> OTOH, I have just learned that although you are correct, that Oracle does
> make this change and all ALTER TABLE changes instantly, as only a metadata
> change, the tradeoff is that actual row size adjustment must be made
during
> actual data use. In fact, if you change the datatype size to something
very
> different, or smaller, like char(5) to char(3) or char to int, Oracle will
> not do any validation at the time of the alter table, but will wait until
> your read the row. So you can end up getting conversion errors just by
> reading data, which can be very problematic.
> So, like many choices, there is a tradeoff. Normally, since altering
tables
> is a rare occurance, but updating and modifying data is done during
> production operations, I'd rather the overhead was accrued during the
alter,
> when I can plan for it.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Lynn Teska" <lteska@.mayo.edu> wrote in message
> news:#Nl5XwioDHA.2488@.TK2MSFTNGP12.phx.gbl...
> > All the more interesting since numeric (7,2) and numeric (8,3) both
appear
> > to be stored in 5 bytes.
> >
> > Lynn
> >
> > --
> >
> >
> > "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> > news:OJjcZz9nDHA.2820@.TK2MSFTNGP10.phx.gbl...
> > > Lynn
> > >
> > > The vendors says Oracle can do this instantly, but you've never tried
it
> > > yourself?
> > >
> > > I wouldn't be surprised if a SQL Server vendor said SQL Server could
do
> it
> > > instantly too, that's why you come to a Technical forum to find out.
> Have
> > > you asked this on an Oracle Technical forum?
> > >
> > > As I mentioned, there are some kinds of ALTER TABLEs that can be done
> > > instantly, and there is a lot of confusion, so someone who had not
> > > researched this issue in technical detail could easily tell you that
> this
> > > was an instantaneous operation, even on SQL Server.
> > >
> > > You are wanting to physically change 25 million rows? How could this
> > > possible be an instantaneous operation?
> > >
> > > One faster way you might consider is to create a new table using
select
> > > into, which is a very fast command, and then dropping the old table,
and
> > > renaming the new one to the old name.
> > >
> > > SELECT convert(numeric(8,3), col1) as col1, convert(newdatatype, col2)
> as
> > > col2 ...
> > > INTO newtable
> > > FROM original_table
> > > GO
> > >
> > > --recreate constraints, indexes etc on newtable
> > >
> > > DROP original_table
> > >
> > > EXEC sp_rename newtable, original_table
> > >
> > > Good Luck!
> > >
> > > --
> > > HTH
> > > --
> > > Kalen Delaney
> > > SQL Server MVP
> > > www.SolidQualityLearning.com
> > >
> > >
> > > "Lynn Teska" <lteska@.mayo.edu> wrote in message
> > > news:#HIbWl9nDHA.2064@.TK2MSFTNGP11.phx.gbl...
> > > > I understand how to do the task with the EM or TSQL.
> > > > The problem is the time it takes with 25 million rows is not
> acceptable
> > in
> > > > at 24x7x365 system.
> > > >
> > > > TSQL can only alter one column at a time, and with 200 columns to do
> > that
> > > is
> > > > not so good.
> > > > EM makes copies as you note and that is not efficient in terms of
disk
> > > i/o.
> > > > I am trying to get a strategy that will minimize or eliminate down
> time
> > > and
> > > > blocking of the table.
> > > >
> > > > Interestingly Oracle can do this sort of alteration instantly,
> according
> > > to
> > > > our vendor.
> > > >
> > > > Thanks
> > > >
> > > > Lynn Teska
> > > > Mayo Clinic
> > > >
> > > >
> > > > "Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in
message
> > > > news:71L36X9nDHA.2012@.cpmsftngxa06.phx.gbl...
> > > > > Hi Lynn,
> > > > >
> > > > > I would like to thank Kalen and Tibor for their help. As I
> understand,
> > > you
> > > > > want to widen all the numeric (7,2) columns to numeric (8,3) in
the
> > > table
> > > > > on the machine. If I have misunderstood, please feel free to let
me
> > > know.
> > > > >
> > > > > To change the schema of the table, we can perform SQL statements
> using
> > > > > Query Analyzer or Change the table schema directly in SQL Server
> > > > Enterprise
> > > > > Manager. Because Enterprise Manager will create a new tale and
drop
> > the
> > > > > original table for changing the schema, I think it is better to
use
> > > Query
> > > > > Analyzer with ALTER TABLE statement.
> > > > >
> > > > > Example:
> > > > >
> > > > > alter table <table name> alter column <column name> numeric(8,3)
> > > > >
> > > > > For additional information regarding ALTER TABLE, please refer to
> the
> > > > > following article on SQL Server Books Online.
> > > > > Topic: "ALTER TABLE"
> > > > >
> > > > > Please feel free to post in the group if this solves your problem
or
> > if
> > > > you
> > > > > would like further assistance.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Michael Shao
> > > > > Microsoft Online Partner Support
> > > > > Get Secure! - www.microsoft.com/security
> > > > > This posting is provided "as is" with no warranties and confers no
> > > rights.
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>