Please....help....I've to go live with the production environment - next
week...
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
Many thanks...Bye the way...I'm using the Reporting Service Developer Edition on my Test
serverâ?¦
"Dominic" wrote:
> Please....help....I've to go live with the production environment - next
> week...
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
> Many thanks...|||Hi Dominic,
I had exactly the same problem as you described. I'm also using the
Reporting Server Developer Edition too on our test system. After alot of
effort I tracked it down to the SSL certificate we have on our test server
not been written to the "Trusted Certificated List". To Fix this I used
selfSSL with the option /T see below this fixed it with no other changes
required. If I missed out the /T option I got exactly the same error as you.
Regards,
Microsoft (R) SelfSSL Version 1.0
Copyright (C) 2003 Microsoft Corporation. All rights reserved.
Installs self-signed SSL certificate into IIS.
SELFSSL [/T] [/N:cn] [/K:key size] [/S:site id] [/P:port]
/T Adds the self-signed certificate to "Trusted Certificates"
list. The local browser will trust the self-signed
certificate
if this flag is specified.
/N:cn Specifies the common name of the certificate. The computer
name is used if not specified.
/K:key size Specifies the key length. Default is 1024.
/V:validity days Specifies the validity of the certificate. Default is 7 days.
/S:site id Specifies the id of the site. Default is 1 (Default Site).
/P:port Specifies the SSL port. Default is 443.
/Q Quiet mode. You will not be prompted when SSL settings are
overwritten.
I ran selfssl on the command line with the following options
selfssl.exe /T /N:CN=EDGE /K:1024 /V:365 /S:1 /P:443
"Dominic" wrote:
> Bye the way...I'm using the Reporting Service Developer Edition on my Test
> serverâ?¦
>
> "Dominic" wrote:
> > Please....help....I've to go live with the production environment - next
> > week...
> >
> > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?&guid=&sloc=en-us&dg=microsoft.public.sqlserver.reportingsvcs&p=1&tid=a80ed727-334a-47c9-a6c8-2b76dfc141cd
> >
> > Many thanks...
Saturday, February 25, 2012
Could not establish trust relationship with remote server.
I am trying to setup SQL Server 2000 Reporting services with an SSL
connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
have tried setting up Certificates from both and Stand-Alone and Enterprise
CA. I have tried several combinations of the Issue To name (server |
server.company | server.company.local) I have modified the
rsWebApplication.config and rsReportServer.config to match the certificateâ's
Issue to exactly. I have tried installs with both Domain Accounts and NT
AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
to work but I have had no luck with the report manager
https://server/reports. How do I fix this error?
ThankyouThe most likely reason this is failing is that your Report Server does not
trust the Root Certificate Authority that created the certificate you are
using.
If you go to https://machine/ReportServer and IE says "this certificate is
not valid are you sure you want to accept it?" then you will know that the
certificate is not 100% trusted and that is why you are receiving the error.
You will need to export the Trusted Root Authority certificate from the
issuing server and import it on the Report Server.
--
SQL Server Developer Support Engineer
"vbchewie" wrote:
> I am trying to setup SQL Server 2000 Reporting services with an SSL
> connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> have tried setting up Certificates from both and Stand-Alone and Enterprise
> CA. I have tried several combinations of the Issue To name (server |
> server.company | server.company.local) I have modified the
> rsWebApplication.config and rsReportServer.config to match the certificateâ's
> Issue to exactly. I have tried installs with both Domain Accounts and NT
> AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> to work but I have had no luck with the report manager
> https://server/reports. How do I fix this error?
> Thankyou
>|||I went to the stand alone root certificate authority and exported the
certificate for that server. I then imported it into both the SQL Server and
Reporting Server. Now when I type the FQDN
(https://machine.domain.local/Reports ) I no longer get a certificate error,
but I do still get â'The underlying connection was closed: Could not establish
trust relationship with remote server.â'
Is there something else I can do? Does it have to be an Enterprise Root
Certificate Authority in order to work?
Thank You.
"Chris Alton [MS]" wrote:
> The most likely reason this is failing is that your Report Server does not
> trust the Root Certificate Authority that created the certificate you are
> using.
> If you go to https://machine/ReportServer and IE says "this certificate is
> not valid are you sure you want to accept it?" then you will know that the
> certificate is not 100% trusted and that is why you are receiving the error.
> You will need to export the Trusted Root Authority certificate from the
> issuing server and import it on the Report Server.
> --
> SQL Server Developer Support Engineer
>
> "vbchewie" wrote:
> > I am trying to setup SQL Server 2000 Reporting services with an SSL
> > connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> > Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> > have tried setting up Certificates from both and Stand-Alone and Enterprise
> > CA. I have tried several combinations of the Issue To name (server |
> > server.company | server.company.local) I have modified the
> > rsWebApplication.config and rsReportServer.config to match the certificateâ's
> > Issue to exactly. I have tried installs with both Domain Accounts and NT
> > AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> > to work but I have had no luck with the report manager
> > https://server/reports. How do I fix this error?
> >
> > Thankyou
> >|||You also need to make sure that the SSL certificate you are using matches
the machine name you are accessing it by EXACTLY. You will also need to
make sure that in the Reporting Services configuration tool that you have
checked the "Require Secure Socket Layer (SSL) Connections" and put the
same name you are accessing the server by in the "Certificate Name" field.
So in your example you would put "machine.domain.local" in the Certificate
Field and the certificate should be issued to "machine.domain.local".
The easiest way to tell if the certificate is valid is to open up
https://machine.domain.local/ReportServer from the web server and if IE
complains about the certificate at all then it will not work.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||In RSReportServer.config I have my "SecureConnectionLevel" Value="3" and my
<UrlRoot>https://machine.domain.local/ReportServer</UrlRoot>
in RSWebApplication.config
I have
<ReportServerUrl>https://machine.domain.local/ReportServer</ReportServerUrl>
When I go to IIS on the Reporting Server and right click on Default Web Site
> Properties > Directory Security.
And click on 'View Certificate...' it says Issued to: machine.domain.local I
also checked the friendly name it also has machine.domain.local.
When I click 'Edit...' under 'Secure communications' both Require secure
channel(SSL) and Require 128-bit encryption are checked.
When I click 'Edit...' Under 'Authentication and access control' Enable
anonymous access is unchecked.
The same is true for my Virtual Directories 'Reports' and ReportServer'
When I go to https://machine/domain.local/Reports there are no certificate
errors. It goes straight though to a page that says
"The underlying connection was closed: Could not establish trust
relationship with remote server."
You mentioned Reporting Services Configuration Tool. This is Reporting
Services for SQL Server 2000. Is there a Reporting Services Configuration
Tool for this version? I thought that was for 2005.
Iâ'm not sure what I am missing. Any other ideas?
Thank you
"Chris Alton [MSFT]" wrote:
> You also need to make sure that the SSL certificate you are using matches
> the machine name you are accessing it by EXACTLY. You will also need to
> make sure that in the Reporting Services configuration tool that you have
> checked the "Require Secure Socket Layer (SSL) Connections" and put the
> same name you are accessing the server by in the "Certificate Name" field.
> So in your example you would put "machine.domain.local" in the Certificate
> Field and the certificate should be issued to "machine.domain.local".
> The easiest way to tell if the certificate is valid is to open up
> https://machine.domain.local/ReportServer from the web server and if IE
> complains about the certificate at all then it will not work.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I didn't know you were using SQL 2000. The only thing I can think of is
that you need to install the Root CA Certificate in the Certificate Store
of the Machine account. What account do you have the SRS Windows Service
and the IIS Application Pool running under?
If it is LocalSystem or Network Service you can install the certificate by
following these steps:
a. Click Start->Run
b. Type mmc and hit enter.
c. Click File->Add/Remove Snap-in
d. Click the "Add" button.
e. Select "Certificates" from the list
f. Click the "Add" button.
g. Click the "Computer Account" radio button.
h. Click "Next"
i. Make sure "Local Computer" is selected and click "Finish"
j. Click "Close"
k. Click "Ok"
l. Branch down on Certificates.
m. Right click Trusted Root Certification Authorities->All
Tasks->Import...
n. Click "Next" and browse to the certificate you are importing.
o. Click "Next" and make sure the "Place all certificates in the
following store" is selected and "Trusted Root Certification Authorities"
is listed in the "Certificate Store" box. If not browse to it by clicking
the "Browse" button.
p. Click "Next" and then click "Finish"
q. The Trusted Root Authority Certificate should now be imported and
available to web application/service.
Hopefully that should get it now.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||It works!!!
SRS is running under a domain\account. In order to get Kerberos to function
properly I used setspn to allow the domain\account to use the http service.
So I am not running under LocalSystem or Network Service.
I logged into the computer with the domain\account that is running both the
SRS Service and the ReportingServices Application Pool. I followed your
directions exactly with only one variation. Instead of picking "Computer
Account" at g. I chose "My Account". It looks like it is working now.
To recap for anyone else that runs into this issue:
SQL Server 2000 is on machine1
SharePoint and Reporting Services are on machine2 and are running under a
domain\account (very limited rights).
SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
Thank you very much for your help,
"Chris Alton [MSFT]" wrote:
> I didn't know you were using SQL 2000. The only thing I can think of is
> that you need to install the Root CA Certificate in the Certificate Store
> of the Machine account. What account do you have the SRS Windows Service
> and the IIS Application Pool running under?
> If it is LocalSystem or Network Service you can install the certificate by
> following these steps:
> a. Click Start->Run
> b. Type mmc and hit enter.
> c. Click File->Add/Remove Snap-in
> d. Click the "Add" button.
> e. Select "Certificates" from the list
> f. Click the "Add" button.
> g. Click the "Computer Account" radio button.
> h. Click "Next"
> i. Make sure "Local Computer" is selected and click "Finish"
> j. Click "Close"
> k. Click "Ok"
> l. Branch down on Certificates.
> m. Right click Trusted Root Certification Authorities->All
> Tasks->Import...
> n. Click "Next" and browse to the certificate you are importing.
> o. Click "Next" and make sure the "Place all certificates in the
> following store" is selected and "Trusted Root Certification Authorities"
> is listed in the "Certificate Store" box. If not browse to it by clicking
> the "Browse" button.
> p. Click "Next" and then click "Finish"
> q. The Trusted Root Authority Certificate should now be imported and
> available to web application/service.
> Hopefully that should get it now.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||If the Windows Service and Application Pool all run under a domain account
then you really don't have to go through all those convoluted steps to
import the cert. That is only if you are using LocalSystem/Network Service
since those are considered the "Machine" account.
If you can log on to the account in an interactive session all you really
have to do to import the certificate is logon and then double click the
cer file and follow the prompts :)
Glad its working for you now though, those SSL issues with SRS can be quite
complicated sometimes.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Could not establish trust relationship with remote server.
> From: <vbchewie@.discussions.microsoft.com>
> Subject: RE: Could not establish trust relationship with remote server.
> Date: Tue, 2 Oct 2007 14:18:01 -0700
> It works!!!
> SRS is running under a domain\account. In order to get Kerberos to
function
> properly I used setspn to allow the domain\account to use the http
service.
> So I am not running under LocalSystem or Network Service.
> I logged into the computer with the domain\account that is running both
the
> SRS Service and the ReportingServices Application Pool. I followed your
> directions exactly with only one variation. Instead of picking "Computer
> Account" at g. I chose "My Account". It looks like it is working now.
> To recap for anyone else that runs into this issue:
> SQL Server 2000 is on machine1
> SharePoint and Reporting Services are on machine2 and are running under a
> domain\account (very limited rights).
> SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
> Thank you very much for your help,
>
> "Chris Alton [MSFT]" wrote:
> > I didn't know you were using SQL 2000. The only thing I can think of is
> > that you need to install the Root CA Certificate in the Certificate
Store
> > of the Machine account. What account do you have the SRS Windows
Service
> > and the IIS Application Pool running under?
> >
> > If it is LocalSystem or Network Service you can install the certificate
by
> > following these steps:
> >
> > a. Click Start->Run
> > b. Type mmc and hit enter.
> > c. Click File->Add/Remove Snap-in
> > d. Click the "Add" button.
> > e. Select "Certificates" from the list
> > f. Click the "Add" button.
> > g. Click the "Computer Account" radio button.
> > h. Click "Next"
> > i. Make sure "Local Computer" is selected and click "Finish"
> > j. Click "Close"
> > k. Click "Ok"
> > l. Branch down on Certificates.
> > m. Right click Trusted Root Certification Authorities->All
> > Tasks->Import...
> > n. Click "Next" and browse to the certificate you are importing.
> > o. Click "Next" and make sure the "Place all certificates in the
> > following store" is selected and "Trusted Root Certification
Authorities"
> > is listed in the "Certificate Store" box. If not browse to it by
clicking
> > the "Browse" button.
> > p. Click "Next" and then click "Finish"
> > q. The Trusted Root Authority Certificate should now be imported
and
> > available to web application/service.
> >
> > Hopefully that should get it now.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
>
connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
have tried setting up Certificates from both and Stand-Alone and Enterprise
CA. I have tried several combinations of the Issue To name (server |
server.company | server.company.local) I have modified the
rsWebApplication.config and rsReportServer.config to match the certificateâ's
Issue to exactly. I have tried installs with both Domain Accounts and NT
AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
to work but I have had no luck with the report manager
https://server/reports. How do I fix this error?
ThankyouThe most likely reason this is failing is that your Report Server does not
trust the Root Certificate Authority that created the certificate you are
using.
If you go to https://machine/ReportServer and IE says "this certificate is
not valid are you sure you want to accept it?" then you will know that the
certificate is not 100% trusted and that is why you are receiving the error.
You will need to export the Trusted Root Authority certificate from the
issuing server and import it on the Report Server.
--
SQL Server Developer Support Engineer
"vbchewie" wrote:
> I am trying to setup SQL Server 2000 Reporting services with an SSL
> connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> have tried setting up Certificates from both and Stand-Alone and Enterprise
> CA. I have tried several combinations of the Issue To name (server |
> server.company | server.company.local) I have modified the
> rsWebApplication.config and rsReportServer.config to match the certificateâ's
> Issue to exactly. I have tried installs with both Domain Accounts and NT
> AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> to work but I have had no luck with the report manager
> https://server/reports. How do I fix this error?
> Thankyou
>|||I went to the stand alone root certificate authority and exported the
certificate for that server. I then imported it into both the SQL Server and
Reporting Server. Now when I type the FQDN
(https://machine.domain.local/Reports ) I no longer get a certificate error,
but I do still get â'The underlying connection was closed: Could not establish
trust relationship with remote server.â'
Is there something else I can do? Does it have to be an Enterprise Root
Certificate Authority in order to work?
Thank You.
"Chris Alton [MS]" wrote:
> The most likely reason this is failing is that your Report Server does not
> trust the Root Certificate Authority that created the certificate you are
> using.
> If you go to https://machine/ReportServer and IE says "this certificate is
> not valid are you sure you want to accept it?" then you will know that the
> certificate is not 100% trusted and that is why you are receiving the error.
> You will need to export the Trusted Root Authority certificate from the
> issuing server and import it on the Report Server.
> --
> SQL Server Developer Support Engineer
>
> "vbchewie" wrote:
> > I am trying to setup SQL Server 2000 Reporting services with an SSL
> > connection. The SQL Server (Windows Server 2003 SP2 Standard) and Reporting
> > Server (Windows Server 2003 R2 SP2 Standard) are on separate machines. I
> > have tried setting up Certificates from both and Stand-Alone and Enterprise
> > CA. I have tried several combinations of the Issue To name (server |
> > server.company | server.company.local) I have modified the
> > rsWebApplication.config and rsReportServer.config to match the certificateâ's
> > Issue to exactly. I have tried installs with both Domain Accounts and NT
> > AUTHORITY\SYSTEM logins. I have managed to get https://server/ReportServer
> > to work but I have had no luck with the report manager
> > https://server/reports. How do I fix this error?
> >
> > Thankyou
> >|||You also need to make sure that the SSL certificate you are using matches
the machine name you are accessing it by EXACTLY. You will also need to
make sure that in the Reporting Services configuration tool that you have
checked the "Require Secure Socket Layer (SSL) Connections" and put the
same name you are accessing the server by in the "Certificate Name" field.
So in your example you would put "machine.domain.local" in the Certificate
Field and the certificate should be issued to "machine.domain.local".
The easiest way to tell if the certificate is valid is to open up
https://machine.domain.local/ReportServer from the web server and if IE
complains about the certificate at all then it will not work.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||In RSReportServer.config I have my "SecureConnectionLevel" Value="3" and my
<UrlRoot>https://machine.domain.local/ReportServer</UrlRoot>
in RSWebApplication.config
I have
<ReportServerUrl>https://machine.domain.local/ReportServer</ReportServerUrl>
When I go to IIS on the Reporting Server and right click on Default Web Site
> Properties > Directory Security.
And click on 'View Certificate...' it says Issued to: machine.domain.local I
also checked the friendly name it also has machine.domain.local.
When I click 'Edit...' under 'Secure communications' both Require secure
channel(SSL) and Require 128-bit encryption are checked.
When I click 'Edit...' Under 'Authentication and access control' Enable
anonymous access is unchecked.
The same is true for my Virtual Directories 'Reports' and ReportServer'
When I go to https://machine/domain.local/Reports there are no certificate
errors. It goes straight though to a page that says
"The underlying connection was closed: Could not establish trust
relationship with remote server."
You mentioned Reporting Services Configuration Tool. This is Reporting
Services for SQL Server 2000. Is there a Reporting Services Configuration
Tool for this version? I thought that was for 2005.
Iâ'm not sure what I am missing. Any other ideas?
Thank you
"Chris Alton [MSFT]" wrote:
> You also need to make sure that the SSL certificate you are using matches
> the machine name you are accessing it by EXACTLY. You will also need to
> make sure that in the Reporting Services configuration tool that you have
> checked the "Require Secure Socket Layer (SSL) Connections" and put the
> same name you are accessing the server by in the "Certificate Name" field.
> So in your example you would put "machine.domain.local" in the Certificate
> Field and the certificate should be issued to "machine.domain.local".
> The easiest way to tell if the certificate is valid is to open up
> https://machine.domain.local/ReportServer from the web server and if IE
> complains about the certificate at all then it will not work.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I didn't know you were using SQL 2000. The only thing I can think of is
that you need to install the Root CA Certificate in the Certificate Store
of the Machine account. What account do you have the SRS Windows Service
and the IIS Application Pool running under?
If it is LocalSystem or Network Service you can install the certificate by
following these steps:
a. Click Start->Run
b. Type mmc and hit enter.
c. Click File->Add/Remove Snap-in
d. Click the "Add" button.
e. Select "Certificates" from the list
f. Click the "Add" button.
g. Click the "Computer Account" radio button.
h. Click "Next"
i. Make sure "Local Computer" is selected and click "Finish"
j. Click "Close"
k. Click "Ok"
l. Branch down on Certificates.
m. Right click Trusted Root Certification Authorities->All
Tasks->Import...
n. Click "Next" and browse to the certificate you are importing.
o. Click "Next" and make sure the "Place all certificates in the
following store" is selected and "Trusted Root Certification Authorities"
is listed in the "Certificate Store" box. If not browse to it by clicking
the "Browse" button.
p. Click "Next" and then click "Finish"
q. The Trusted Root Authority Certificate should now be imported and
available to web application/service.
Hopefully that should get it now.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.|||It works!!!
SRS is running under a domain\account. In order to get Kerberos to function
properly I used setspn to allow the domain\account to use the http service.
So I am not running under LocalSystem or Network Service.
I logged into the computer with the domain\account that is running both the
SRS Service and the ReportingServices Application Pool. I followed your
directions exactly with only one variation. Instead of picking "Computer
Account" at g. I chose "My Account". It looks like it is working now.
To recap for anyone else that runs into this issue:
SQL Server 2000 is on machine1
SharePoint and Reporting Services are on machine2 and are running under a
domain\account (very limited rights).
SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
Thank you very much for your help,
"Chris Alton [MSFT]" wrote:
> I didn't know you were using SQL 2000. The only thing I can think of is
> that you need to install the Root CA Certificate in the Certificate Store
> of the Machine account. What account do you have the SRS Windows Service
> and the IIS Application Pool running under?
> If it is LocalSystem or Network Service you can install the certificate by
> following these steps:
> a. Click Start->Run
> b. Type mmc and hit enter.
> c. Click File->Add/Remove Snap-in
> d. Click the "Add" button.
> e. Select "Certificates" from the list
> f. Click the "Add" button.
> g. Click the "Computer Account" radio button.
> h. Click "Next"
> i. Make sure "Local Computer" is selected and click "Finish"
> j. Click "Close"
> k. Click "Ok"
> l. Branch down on Certificates.
> m. Right click Trusted Root Certification Authorities->All
> Tasks->Import...
> n. Click "Next" and browse to the certificate you are importing.
> o. Click "Next" and make sure the "Place all certificates in the
> following store" is selected and "Trusted Root Certification Authorities"
> is listed in the "Certificate Store" box. If not browse to it by clicking
> the "Browse" button.
> p. Click "Next" and then click "Finish"
> q. The Trusted Root Authority Certificate should now be imported and
> available to web application/service.
> Hopefully that should get it now.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||If the Windows Service and Application Pool all run under a domain account
then you really don't have to go through all those convoluted steps to
import the cert. That is only if you are using LocalSystem/Network Service
since those are considered the "Machine" account.
If you can log on to the account in an interactive session all you really
have to do to import the certificate is logon and then double click the
cer file and follow the prompts :)
Glad its working for you now though, those SSL issues with SRS can be quite
complicated sometimes.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Could not establish trust relationship with remote server.
> From: <vbchewie@.discussions.microsoft.com>
> Subject: RE: Could not establish trust relationship with remote server.
> Date: Tue, 2 Oct 2007 14:18:01 -0700
> It works!!!
> SRS is running under a domain\account. In order to get Kerberos to
function
> properly I used setspn to allow the domain\account to use the http
service.
> So I am not running under LocalSystem or Network Service.
> I logged into the computer with the domain\account that is running both
the
> SRS Service and the ReportingServices Application Pool. I followed your
> directions exactly with only one variation. Instead of picking "Computer
> Account" at g. I chose "My Account". It looks like it is working now.
> To recap for anyone else that runs into this issue:
> SQL Server 2000 is on machine1
> SharePoint and Reporting Services are on machine2 and are running under a
> domain\account (very limited rights).
> SSL Certificate was issued from a Stand-Alone Root Certificate Authority.
> Thank you very much for your help,
>
> "Chris Alton [MSFT]" wrote:
> > I didn't know you were using SQL 2000. The only thing I can think of is
> > that you need to install the Root CA Certificate in the Certificate
Store
> > of the Machine account. What account do you have the SRS Windows
Service
> > and the IIS Application Pool running under?
> >
> > If it is LocalSystem or Network Service you can install the certificate
by
> > following these steps:
> >
> > a. Click Start->Run
> > b. Type mmc and hit enter.
> > c. Click File->Add/Remove Snap-in
> > d. Click the "Add" button.
> > e. Select "Certificates" from the list
> > f. Click the "Add" button.
> > g. Click the "Computer Account" radio button.
> > h. Click "Next"
> > i. Make sure "Local Computer" is selected and click "Finish"
> > j. Click "Close"
> > k. Click "Ok"
> > l. Branch down on Certificates.
> > m. Right click Trusted Root Certification Authorities->All
> > Tasks->Import...
> > n. Click "Next" and browse to the certificate you are importing.
> > o. Click "Next" and make sure the "Place all certificates in the
> > following store" is selected and "Trusted Root Certification
Authorities"
> > is listed in the "Certificate Store" box. If not browse to it by
clicking
> > the "Browse" button.
> > p. Click "Next" and then click "Finish"
> > q. The Trusted Root Authority Certificate should now be imported
and
> > available to web application/service.
> >
> > Hopefully that should get it now.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
>
Could not establish trust relationship with remote server.
Error comes up when I try to deploy RS to my web server, "The underlying
connection was closed: Could not establish trust relationship with remote
server." Web server has valid certificate, and I'm using https in my
connection.
OverwriteDataSources: True
TargetFolder: Reports
TargetServerURL: https://webserver/ReportServer
I'm able to see https://webserver/ReportServer through IE, and I see the
folder Reports. I clicked on Reports and I see my old RS files.I also tried without the s in https, but I still get the same error message.
http://webserver/ReportServer
"Mike L" wrote:
> Error comes up when I try to deploy RS to my web server, "The underlying
> connection was closed: Could not establish trust relationship with remote
> server." Web server has valid certificate, and I'm using https in my
> connection.
> OverwriteDataSources: True
> TargetFolder: Reports
> TargetServerURL: https://webserver/ReportServer
> I'm able to see https://webserver/ReportServer through IE, and I see the
> folder Reports. I clicked on Reports and I see my old RS files.
>|||Hello Cadel,
You may try the following steps to disable SSL on report server to test:
1. Within the RSReportServer.config file you'll find in "\Program
Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
set secureconnectionlevel to 0.
Change
<UrlRoot>https://webserver/ReportServer</UrlRoot>
<UrlRoot>http://webserver/ReportServer</UrlRoot>
2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager, change
<ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
<ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
Note: Please backup above files to safe place before you try to modify
them. You may need to restart IIS if it is not take effect
After that, you may want to configure deploy server to
http://webserver/ReportServer in VS to test the situatioin.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
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: Could not establish trust relationship with remote server.
>thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Mon, 23 Jan 2006 13:00:04 -0800
>Lines: 18
>Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>I also tried without the s in https, but I still get the same error
message.
>http://webserver/ReportServer
>"Mike L" wrote:
>> Error comes up when I try to deploy RS to my web server, "The underlying
>> connection was closed: Could not establish trust relationship with
remote
>> server." Web server has valid certificate, and I'm using https in my
>> connection.
>> OverwriteDataSources: True
>> TargetFolder: Reports
>> TargetServerURL: https://webserver/ReportServer
>> I'm able to see https://webserver/ReportServer through IE, and I see the
>> folder Reports. I clicked on Reports and I see my old RS files.
>|||1. I set "secureconnectionlevel" to zero, the URLRoot was already
"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change that.
2. RSReportServer.config in ReportManager, already had
"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
When I tried to deploy in VS, I made sure the TargetServerURL was
"http://webserver/ReportServer", and the TargetFolder was "Reports".
I now get the error, "c:\intranet\Claims.rds The permissions granted to user
'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
"Peter Yang [MSFT]" wrote:
> Hello Cadel,
> You may try the following steps to disable SSL on report server to test:
> 1. Within the RSReportServer.config file you'll find in "\Program
> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
> set secureconnectionlevel to 0.
> Change
> <UrlRoot>https://webserver/ReportServer</UrlRoot>
> <UrlRoot>http://webserver/ReportServer</UrlRoot>
> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager, change
> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
> Note: Please backup above files to safe place before you try to modify
> them. You may need to restart IIS if it is not take effect
> After that, you may want to configure deploy server to
> http://webserver/ReportServer in VS to test the situatioin.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> 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: Could not establish trust relationship with remote server.
> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==> >X-WBNR-Posting-Host: 204.87.106.66
> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
> >Subject: RE: Could not establish trust relationship with remote server.
> >Date: Mon, 23 Jan 2006 13:00:04 -0800
> >Lines: 18
> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >I also tried without the s in https, but I still get the same error
> message.
> >
> >http://webserver/ReportServer
> >
> >"Mike L" wrote:
> >
> >> Error comes up when I try to deploy RS to my web server, "The underlying
> >> connection was closed: Could not establish trust relationship with
> remote
> >> server." Web server has valid certificate, and I'm using https in my
> >> connection.
> >>
> >> OverwriteDataSources: True
> >> TargetFolder: Reports
> >> TargetServerURL: https://webserver/ReportServer
> >>
> >> I'm able to see https://webserver/ReportServer through IE, and I see the
> >> folder Reports. I clicked on Reports and I see my old RS files.
> >>
> >
>|||Hello Cadel,
It seems your report server is configured to allow anonymous
authentication. Please check the following settings:
1. Run Inetmgr, right click Reportserver virtual
directory->Properties->Directory Security tab
2. Click Edit, and uncheck "Enable anonymouse access", make sure
"Integrated Windows authentication" is checked.
3. Restart IIS to test
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
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: Could not establish trust relationship with remote server.
>thread-index: AcYhHcfqfQzv5KrkRySdCQqp8f5RKg==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
<A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
<Kuu46qKIGHA.1236@.TK2MSFTNGXA02.phx.gbl>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Tue, 24 Jan 2006 11:38:41 -0800
>Lines: 111
>Message-ID: <38F8AA05-20C3-4BDB-B64F-6629EB127703@.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.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67414
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>1. I set "secureconnectionlevel" to zero, the URLRoot was already
>"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change
that.
>2. RSReportServer.config in ReportManager, already had
>"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
>When I tried to deploy in VS, I made sure the TargetServerURL was
>"http://webserver/ReportServer", and the TargetFolder was "Reports".
>I now get the error, "c:\intranet\Claims.rds The permissions granted to
user
>'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
>
>
>
>"Peter Yang [MSFT]" wrote:
>> Hello Cadel,
>> You may try the following steps to disable SSL on report server to test:
>> 1. Within the RSReportServer.config file you'll find in "\Program
>> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
>> set secureconnectionlevel to 0.
>> Change
>> <UrlRoot>https://webserver/ReportServer</UrlRoot>
>> <UrlRoot>http://webserver/ReportServer</UrlRoot>
>> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportManager, change
>> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
>> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
>> Note: Please backup above files to safe place before you try to modify
>> them. You may need to restart IIS if it is not take effect
>> After that, you may want to configure deploy server to
>> http://webserver/ReportServer in VS to test the situatioin.
>> Best Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> 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: Could not establish trust relationship with remote server.
>> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>> >X-WBNR-Posting-Host: 204.87.106.66
>> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>> >Subject: RE: Could not establish trust relationship with remote server.
>> >Date: Mon, 23 Jan 2006 13:00:04 -0800
>> >Lines: 18
>> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.sqlserver.reportingsvcs:67357
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >I also tried without the s in https, but I still get the same error
>> message.
>> >
>> >http://webserver/ReportServer
>> >
>> >"Mike L" wrote:
>> >
>> >> Error comes up when I try to deploy RS to my web server, "The
underlying
>> >> connection was closed: Could not establish trust relationship with
>> remote
>> >> server." Web server has valid certificate, and I'm using https in my
>> >> connection.
>> >>
>> >> OverwriteDataSources: True
>> >> TargetFolder: Reports
>> >> TargetServerURL: https://webserver/ReportServer
>> >>
>> >> I'm able to see https://webserver/ReportServer through IE, and I see
the
>> >> folder Reports. I clicked on Reports and I see my old RS files.
>> >>
>> >
>>
>
connection was closed: Could not establish trust relationship with remote
server." Web server has valid certificate, and I'm using https in my
connection.
OverwriteDataSources: True
TargetFolder: Reports
TargetServerURL: https://webserver/ReportServer
I'm able to see https://webserver/ReportServer through IE, and I see the
folder Reports. I clicked on Reports and I see my old RS files.I also tried without the s in https, but I still get the same error message.
http://webserver/ReportServer
"Mike L" wrote:
> Error comes up when I try to deploy RS to my web server, "The underlying
> connection was closed: Could not establish trust relationship with remote
> server." Web server has valid certificate, and I'm using https in my
> connection.
> OverwriteDataSources: True
> TargetFolder: Reports
> TargetServerURL: https://webserver/ReportServer
> I'm able to see https://webserver/ReportServer through IE, and I see the
> folder Reports. I clicked on Reports and I see my old RS files.
>|||Hello Cadel,
You may try the following steps to disable SSL on report server to test:
1. Within the RSReportServer.config file you'll find in "\Program
Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
set secureconnectionlevel to 0.
Change
<UrlRoot>https://webserver/ReportServer</UrlRoot>
<UrlRoot>http://webserver/ReportServer</UrlRoot>
2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager, change
<ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
<ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
Note: Please backup above files to safe place before you try to modify
them. You may need to restart IIS if it is not take effect
After that, you may want to configure deploy server to
http://webserver/ReportServer in VS to test the situatioin.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
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: Could not establish trust relationship with remote server.
>thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Mon, 23 Jan 2006 13:00:04 -0800
>Lines: 18
>Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>I also tried without the s in https, but I still get the same error
message.
>http://webserver/ReportServer
>"Mike L" wrote:
>> Error comes up when I try to deploy RS to my web server, "The underlying
>> connection was closed: Could not establish trust relationship with
remote
>> server." Web server has valid certificate, and I'm using https in my
>> connection.
>> OverwriteDataSources: True
>> TargetFolder: Reports
>> TargetServerURL: https://webserver/ReportServer
>> I'm able to see https://webserver/ReportServer through IE, and I see the
>> folder Reports. I clicked on Reports and I see my old RS files.
>|||1. I set "secureconnectionlevel" to zero, the URLRoot was already
"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change that.
2. RSReportServer.config in ReportManager, already had
"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
When I tried to deploy in VS, I made sure the TargetServerURL was
"http://webserver/ReportServer", and the TargetFolder was "Reports".
I now get the error, "c:\intranet\Claims.rds The permissions granted to user
'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
"Peter Yang [MSFT]" wrote:
> Hello Cadel,
> You may try the following steps to disable SSL on report server to test:
> 1. Within the RSReportServer.config file you'll find in "\Program
> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
> set secureconnectionlevel to 0.
> Change
> <UrlRoot>https://webserver/ReportServer</UrlRoot>
> <UrlRoot>http://webserver/ReportServer</UrlRoot>
> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager, change
> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
> Note: Please backup above files to safe place before you try to modify
> them. You may need to restart IIS if it is not take effect
> After that, you may want to configure deploy server to
> http://webserver/ReportServer in VS to test the situatioin.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> 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: Could not establish trust relationship with remote server.
> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==> >X-WBNR-Posting-Host: 204.87.106.66
> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
> >Subject: RE: Could not establish trust relationship with remote server.
> >Date: Mon, 23 Jan 2006 13:00:04 -0800
> >Lines: 18
> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67357
> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> >
> >I also tried without the s in https, but I still get the same error
> message.
> >
> >http://webserver/ReportServer
> >
> >"Mike L" wrote:
> >
> >> Error comes up when I try to deploy RS to my web server, "The underlying
> >> connection was closed: Could not establish trust relationship with
> remote
> >> server." Web server has valid certificate, and I'm using https in my
> >> connection.
> >>
> >> OverwriteDataSources: True
> >> TargetFolder: Reports
> >> TargetServerURL: https://webserver/ReportServer
> >>
> >> I'm able to see https://webserver/ReportServer through IE, and I see the
> >> folder Reports. I clicked on Reports and I see my old RS files.
> >>
> >
>|||Hello Cadel,
It seems your report server is configured to allow anonymous
authentication. Please check the following settings:
1. Run Inetmgr, right click Reportserver virtual
directory->Properties->Directory Security tab
2. Click Edit, and uncheck "Enable anonymouse access", make sure
"Integrated Windows authentication" is checked.
3. Restart IIS to test
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
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: Could not establish trust relationship with remote server.
>thread-index: AcYhHcfqfQzv5KrkRySdCQqp8f5RKg==>X-WBNR-Posting-Host: 204.87.106.66
>From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
<A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.microsoft.com>
<Kuu46qKIGHA.1236@.TK2MSFTNGXA02.phx.gbl>
>Subject: RE: Could not establish trust relationship with remote server.
>Date: Tue, 24 Jan 2006 11:38:41 -0800
>Lines: 111
>Message-ID: <38F8AA05-20C3-4BDB-B64F-6629EB127703@.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.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67414
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>1. I set "secureconnectionlevel" to zero, the URLRoot was already
>"<UrlRoot>http://WEBSERVER/ReportServer</UrlRoot>", so I didn't change
that.
>2. RSReportServer.config in ReportManager, already had
>"<ReportServerUrl>http://WEBSERVER/ReportServer</ReportServerUrl>"
>When I tried to deploy in VS, I made sure the TargetServerURL was
>"http://webserver/ReportServer", and the TargetFolder was "Reports".
>I now get the error, "c:\intranet\Claims.rds The permissions granted to
user
>'WEBSERVER\IUSR_WEBSERVER' are insufficient for performing this operation."
>
>
>
>"Peter Yang [MSFT]" wrote:
>> Hello Cadel,
>> You may try the following steps to disable SSL on report server to test:
>> 1. Within the RSReportServer.config file you'll find in "\Program
>> Files\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer",
>> set secureconnectionlevel to 0.
>> Change
>> <UrlRoot>https://webserver/ReportServer</UrlRoot>
>> <UrlRoot>http://webserver/ReportServer</UrlRoot>
>> 2. within C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportManager, change
>> <ReportServerUrl>https://webserver/ReportServer</ReportServerUrl> to
>> <ReportServerUrl>http://webserver/ReportServer</ReportServerUrl>
>> Note: Please backup above files to safe place before you try to modify
>> them. You may need to restart IIS if it is not take effect
>> After that, you may want to configure deploy server to
>> http://webserver/ReportServer in VS to test the situatioin.
>> Best Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> 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: Could not establish trust relationship with remote server.
>> >thread-index: AcYgX/vgGz1j0C1/RduYsSVDkkJvAQ==>> >X-WBNR-Posting-Host: 204.87.106.66
>> >From: =?Utf-8?B?TWlrZSBM?= <Cadel@.nospam.nospam>
>> >References: <18E8F20D-2CC6-4F76-9687-BE23EE3D3687@.microsoft.com>
>> >Subject: RE: Could not establish trust relationship with remote server.
>> >Date: Mon, 23 Jan 2006 13:00:04 -0800
>> >Lines: 18
>> >Message-ID: <A3C8E145-FFF3-4828-BC7F-C0C443BFCF63@.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.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.sqlserver.reportingsvcs:67357
>> >X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
>> >
>> >I also tried without the s in https, but I still get the same error
>> message.
>> >
>> >http://webserver/ReportServer
>> >
>> >"Mike L" wrote:
>> >
>> >> Error comes up when I try to deploy RS to my web server, "The
underlying
>> >> connection was closed: Could not establish trust relationship with
>> remote
>> >> server." Web server has valid certificate, and I'm using https in my
>> >> connection.
>> >>
>> >> OverwriteDataSources: True
>> >> TargetFolder: Reports
>> >> TargetServerURL: https://webserver/ReportServer
>> >>
>> >> I'm able to see https://webserver/ReportServer through IE, and I see
the
>> >> folder Reports. I clicked on Reports and I see my old RS files.
>> >>
>> >
>>
>
Could not establish trust relationship with remote server - Part.2
Hi,
Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
helpâ?¦
We have to new installed Server with the same configuration (except hardware):
- Windows 2003 Enterprise (fully updated)
- SQL Server 2000 Enterprise SP3a
- Reporting Services SP1
- Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
domain account for the Report Service and for the SQL Server connections.
- SSL (checked during installation)
The https://myserver.com/reportserver works fine. If I browse to
https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
underlying connection was closed: Could not establish trust relationship with
remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
problemâ?¦.Iâ've everywhere within the config files the corresponding
https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
also). Iâ'm able to browse to any https site on the server using the same
certificate without any messages or warnings. And Iâ've this problem on both
serversâ?¦.:-((
Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
change an other file as well? Or any other ideas ?
Many thanks for your help !!
Dominic
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.878.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
<SystemName>CLAPTON</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
to 'True' as specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server. at
System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level) at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)Did you come up with an answer? if so, please post it... I am having the same
problem.
"Dominic" wrote:
> Hi,
> Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> helpâ?¦
> We have to new installed Server with the same configuration (except hardware):
> - Windows 2003 Enterprise (fully updated)
> - SQL Server 2000 Enterprise SP3a
> - Reporting Services SP1
> - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> domain account for the Report Service and for the SQL Server connections.
> - SSL (checked during installation)
> The https://myserver.com/reportserver works fine. If I browse to
> https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> underlying connection was closed: Could not establish trust relationship with
> remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> problemâ?¦.Iâ've everywhere within the config files the corresponding
> https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> also). Iâ'm able to browse to any https site on the server using the same
> certificate without any messages or warnings. And Iâ've this problem on both
> serversâ?¦.:-((
> Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> change an other file as well? Or any other ideas ?
> Many thanks for your help !!
> Dominic
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.878.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>W. Europe Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> <SystemName>CLAPTON</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> to default value of '1' second(s) because it was not specified in
> Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> DatabaseQueryTimeout to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> default value of 'MSSQLSERVER.1' because it was not specified in
> Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> ProcessRecycleOptions to default value of '0' because it was not specified
> in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsScavengerCycle to default value of '30' second(s) because it
> was not specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsDbCycle to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsAge to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> CleanupCycleMinutes to default value of '10' minute(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> SecureConnectionLevel to default value of '1' because it was not specified
> in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> to 'True' as specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> WebServiceUseFileShareStorage to default value of 'False' because it was not
> specified in Configuration file.
> w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> closed: Could not establish trust relationship with remote server.
> w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
> establish trust relationship with remote server. at
> System.Net.HttpWebRequest.CheckFinalStatus() at
> System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> System.Net.HttpWebRequest.GetRequestStream() at
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level) at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> System.Web.UI.Control.InitRecursive(Control namingContainer) at
> System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)|||Hi Ron
No, I gave up. I'm running it now in mixed mode.....the users are running
the reports using SSL and the management part is actually running without
SSLâ?¦.itâ's bad but we had to go productionâ?¦anyway - the configuration-part is
not very well with RS (the logging is not always a real help)â?¦.RS is nice but
Microsoft has still a lot to do !
Regards,
Dominic
"Ron Sellers" wrote:
> Did you come up with an answer? if so, please post it... I am having the same
> problem.
> "Dominic" wrote:
> > Hi,
> >
> > Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> > helpâ?¦
> >
> > We have to new installed Server with the same configuration (except hardware):
> > - Windows 2003 Enterprise (fully updated)
> > - SQL Server 2000 Enterprise SP3a
> > - Reporting Services SP1
> > - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> > domain account for the Report Service and for the SQL Server connections.
> > - SSL (checked during installation)
> >
> > The https://myserver.com/reportserver works fine. If I browse to
> > https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> > underlying connection was closed: Could not establish trust relationship with
> > remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> > problemâ?¦.Iâ've everywhere within the config files the corresponding
> > https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> > also). Iâ'm able to browse to any https site on the server using the same
> > certificate without any messages or warnings. And Iâ've this problem on both
> > serversâ?¦.:-((
> >
> > Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> > the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> > Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> > change an other file as well? Or any other ideas ?
> >
> > Many thanks for your help !!
> > Dominic
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>W. Europe Standard Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> > <SystemName>CLAPTON</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because it
> > was not specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> > to 'True' as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it was not
> > specified in Configuration file.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server. at
> > System.Net.HttpWebRequest.CheckFinalStatus() at
> > System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> > System.Net.HttpWebRequest.GetRequestStream() at
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level) at
> > Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> > EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> > System.Web.UI.Control.InitRecursive(Control namingContainer) at
> > System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)|||I was having the same problems until a few minutes ago. I went back through
the following article and found the problem (in my situation at least):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sslsetup.asp
Down at the section:
Installing Reporting Services -> Reporting Services Configuration Files ->
RSWebApplication.config
I hadn't changed the <ReportServerUrl> value to the https://reports.xxx.xxx
(must by an exact match to the value in the SSL certificate) or added the
<Add Key="SecureConnectionLevel" Value="3"/> element. Actually, I hadn't even
looked in this file because my eyes fooling me into thinking it was the
RSReportServer.config file. oops!
Anyway making the RSWebApplication.config look like this worked when all
other paths had failed.
++++++++++++++++++++++++++++++
<Configuration>
<UI>
<ReportServerUrl>https://reports.xxx.xxx/ReportServer</ReportServerUrl>
</UI>
<Extensions>
<DeliveryUI>
<Extension Name="Report Server Email"
Type="Microsoft.ReportingServices.EmailDeliveryProvider.EmailDeliveryProviderControl,ReportingServicesEmailDeliveryProvider">
<DefaultDeliveryExtension>True</DefaultDeliveryExtension>
<Configuration>
<RSEmailDPConfiguration>
<DefaultRenderingExtension>MHTML</DefaultRenderingExtension>
</RSEmailDPConfiguration>
</Configuration>
</Extension>
<Extension Name="Report Server FileShare"
Type="Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareUIControl,ReportingServicesFileShareDeliveryProvider">
<Configuration>
<FileShare>
<DefaultRenderingExtension>MHTML</DefaultRenderingExtension>
</FileShare>
</Configuration>
</Extension>
</DeliveryUI>
</Extensions>
<Add Key="SecureConnectionLevel" Value="3"/>
<Add Key="MaxActiveReqForOneUser" Value="20"/>
<Add Key="DisplayErrorLink" Value="true"/>
</Configuration>
++++++++++++++++++++++++++++++
Hope this is what you were looking for.
Mike Shaw
"Ron Sellers" wrote:
> Did you come up with an answer? if so, please post it... I am having the same
> problem.
> "Dominic" wrote:
> > Hi,
> >
> > Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> > helpâ?¦
> >
> > We have to new installed Server with the same configuration (except hardware):
> > - Windows 2003 Enterprise (fully updated)
> > - SQL Server 2000 Enterprise SP3a
> > - Reporting Services SP1
> > - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> > domain account for the Report Service and for the SQL Server connections.
> > - SSL (checked during installation)
> >
> > The https://myserver.com/reportserver works fine. If I browse to
> > https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> > underlying connection was closed: Could not establish trust relationship with
> > remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> > problemâ?¦.Iâ've everywhere within the config files the corresponding
> > https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> > also). Iâ'm able to browse to any https site on the server using the same
> > certificate without any messages or warnings. And Iâ've this problem on both
> > serversâ?¦.:-((
> >
> > Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> > the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> > Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> > change an other file as well? Or any other ideas ?
> >
> > Many thanks for your help !!
> > Dominic
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>W. Europe Standard Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> > <SystemName>CLAPTON</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because it
> > was not specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> > to 'True' as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it was not
> > specified in Configuration file.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server. at
> > System.Net.HttpWebRequest.CheckFinalStatus() at
> > System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> > System.Net.HttpWebRequest.GetRequestStream() at
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level) at
> > Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> > EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> > System.Web.UI.Control.InitRecursive(Control namingContainer) at
> > System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)|||That did it! Thanks Mike!
Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
helpâ?¦
We have to new installed Server with the same configuration (except hardware):
- Windows 2003 Enterprise (fully updated)
- SQL Server 2000 Enterprise SP3a
- Reporting Services SP1
- Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
domain account for the Report Service and for the SQL Server connections.
- SSL (checked during installation)
The https://myserver.com/reportserver works fine. If I browse to
https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
underlying connection was closed: Could not establish trust relationship with
remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
problemâ?¦.Iâ've everywhere within the config files the corresponding
https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
also). Iâ'm able to browse to any https site on the server using the same
certificate without any messages or warnings. And Iâ've this problem on both
serversâ?¦.:-((
Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
change an other file as well? Or any other ideas ?
Many thanks for your help !!
Dominic
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.878.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
<SystemName>CLAPTON</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
to 'True' as specified in Configuration file.
w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server. at
System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level) at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)Did you come up with an answer? if so, please post it... I am having the same
problem.
"Dominic" wrote:
> Hi,
> Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> helpâ?¦
> We have to new installed Server with the same configuration (except hardware):
> - Windows 2003 Enterprise (fully updated)
> - SQL Server 2000 Enterprise SP3a
> - Reporting Services SP1
> - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> domain account for the Report Service and for the SQL Server connections.
> - SSL (checked during installation)
> The https://myserver.com/reportserver works fine. If I browse to
> https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> underlying connection was closed: Could not establish trust relationship with
> remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> problemâ?¦.Iâ've everywhere within the config files the corresponding
> https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> also). Iâ'm able to browse to any https site on the server using the same
> certificate without any messages or warnings. And Iâ've this problem on both
> serversâ?¦.:-((
> Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> change an other file as well? Or any other ideas ?
> Many thanks for your help !!
> Dominic
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.878.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>W. Europe Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> <SystemName>CLAPTON</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> to default value of '1' second(s) because it was not specified in
> Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> DatabaseQueryTimeout to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> default value of 'MSSQLSERVER.1' because it was not specified in
> Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> ProcessRecycleOptions to default value of '0' because it was not specified
> in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsScavengerCycle to default value of '30' second(s) because it
> was not specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsDbCycle to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> RunningRequestsAge to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> CleanupCycleMinutes to default value of '10' minute(s) because it was not
> specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> SecureConnectionLevel to default value of '1' because it was not specified
> in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> to 'True' as specified in Configuration file.
> w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> WebServiceUseFileShareStorage to default value of 'False' because it was not
> specified in Configuration file.
> w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> closed: Could not establish trust relationship with remote server.
> w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
> establish trust relationship with remote server. at
> System.Net.HttpWebRequest.CheckFinalStatus() at
> System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> System.Net.HttpWebRequest.GetRequestStream() at
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters) at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level) at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> System.Web.UI.Control.InitRecursive(Control namingContainer) at
> System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)|||Hi Ron
No, I gave up. I'm running it now in mixed mode.....the users are running
the reports using SSL and the management part is actually running without
SSLâ?¦.itâ's bad but we had to go productionâ?¦anyway - the configuration-part is
not very well with RS (the logging is not always a real help)â?¦.RS is nice but
Microsoft has still a lot to do !
Regards,
Dominic
"Ron Sellers" wrote:
> Did you come up with an answer? if so, please post it... I am having the same
> problem.
> "Dominic" wrote:
> > Hi,
> >
> > Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> > helpâ?¦
> >
> > We have to new installed Server with the same configuration (except hardware):
> > - Windows 2003 Enterprise (fully updated)
> > - SQL Server 2000 Enterprise SP3a
> > - Reporting Services SP1
> > - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> > domain account for the Report Service and for the SQL Server connections.
> > - SSL (checked during installation)
> >
> > The https://myserver.com/reportserver works fine. If I browse to
> > https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> > underlying connection was closed: Could not establish trust relationship with
> > remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> > problemâ?¦.Iâ've everywhere within the config files the corresponding
> > https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> > also). Iâ'm able to browse to any https site on the server using the same
> > certificate without any messages or warnings. And Iâ've this problem on both
> > serversâ?¦.:-((
> >
> > Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> > the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> > Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> > change an other file as well? Or any other ideas ?
> >
> > Many thanks for your help !!
> > Dominic
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>W. Europe Standard Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> > <SystemName>CLAPTON</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because it
> > was not specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> > to 'True' as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it was not
> > specified in Configuration file.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server. at
> > System.Net.HttpWebRequest.CheckFinalStatus() at
> > System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> > System.Net.HttpWebRequest.GetRequestStream() at
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level) at
> > Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> > EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> > System.Web.UI.Control.InitRecursive(Control namingContainer) at
> > System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)|||I was having the same problems until a few minutes ago. I went back through
the following article and found the problem (in my situation at least):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sslsetup.asp
Down at the section:
Installing Reporting Services -> Reporting Services Configuration Files ->
RSWebApplication.config
I hadn't changed the <ReportServerUrl> value to the https://reports.xxx.xxx
(must by an exact match to the value in the SSL certificate) or added the
<Add Key="SecureConnectionLevel" Value="3"/> element. Actually, I hadn't even
looked in this file because my eyes fooling me into thinking it was the
RSReportServer.config file. oops!
Anyway making the RSWebApplication.config look like this worked when all
other paths had failed.
++++++++++++++++++++++++++++++
<Configuration>
<UI>
<ReportServerUrl>https://reports.xxx.xxx/ReportServer</ReportServerUrl>
</UI>
<Extensions>
<DeliveryUI>
<Extension Name="Report Server Email"
Type="Microsoft.ReportingServices.EmailDeliveryProvider.EmailDeliveryProviderControl,ReportingServicesEmailDeliveryProvider">
<DefaultDeliveryExtension>True</DefaultDeliveryExtension>
<Configuration>
<RSEmailDPConfiguration>
<DefaultRenderingExtension>MHTML</DefaultRenderingExtension>
</RSEmailDPConfiguration>
</Configuration>
</Extension>
<Extension Name="Report Server FileShare"
Type="Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareUIControl,ReportingServicesFileShareDeliveryProvider">
<Configuration>
<FileShare>
<DefaultRenderingExtension>MHTML</DefaultRenderingExtension>
</FileShare>
</Configuration>
</Extension>
</DeliveryUI>
</Extensions>
<Add Key="SecureConnectionLevel" Value="3"/>
<Add Key="MaxActiveReqForOneUser" Value="20"/>
<Add Key="DisplayErrorLink" Value="true"/>
</Configuration>
++++++++++++++++++++++++++++++
Hope this is what you were looking for.
Mike Shaw
"Ron Sellers" wrote:
> Did you come up with an answer? if so, please post it... I am having the same
> problem.
> "Dominic" wrote:
> > Hi,
> >
> > Iâ'm posting now for the second time with this issueâ?¦hopefully can somebody
> > helpâ?¦
> >
> > We have to new installed Server with the same configuration (except hardware):
> > - Windows 2003 Enterprise (fully updated)
> > - SQL Server 2000 Enterprise SP3a
> > - Reporting Services SP1
> > - Patch SQL2000-KB810185-8.00.0859 (asked by the installation cause using a
> > domain account for the Report Service and for the SQL Server connections.
> > - SSL (checked during installation)
> >
> > The https://myserver.com/reportserver works fine. If I browse to
> > https://myserver.com/reports (Report manager) Iâ'm getting the message â'The
> > underlying connection was closed: Could not establish trust relationship with
> > remote serverâ'. Itâ's killing me. Iâ'm fighting since a long time with this
> > problemâ?¦.Iâ've everywhere within the config files the corresponding
> > https://myservber.com entries. SecureConnectionLevel set to 3 (tried with 2
> > also). Iâ'm able to browse to any https site on the server using the same
> > certificate without any messages or warnings. And Iâ've this problem on both
> > serversâ?¦.:-((
> >
> > Following you will see theReportServerWebApp_xxxxxxx Log file. Why do I have
> > the entry â'Initializing SecureConnectionLevel to default value of '1' â' ?
> > Iâ've configured this Value to 3 within RSReportServer.config. Do I need to
> > change an other file as well? Or any other ideas ?
> >
> > Many thanks for your help !!
> > Dominic
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>W. Europe Standard Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__11_10_2004_08_05_23.log</Path>
> > <SystemName>CLAPTON</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because it
> > was not specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was not
> > specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not specified
> > in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing DisplayErrorLink
> > to 'True' as specified in Configuration file.
> > w3wp!library!e94!11/10/2004-08:05:23:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it was not
> > specified in Configuration file.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!ea0!11/10/2004-08:05:41:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server. at
> > System.Net.HttpWebRequest.CheckFinalStatus() at
> > System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
> > System.Net.HttpWebRequest.GetRequestStream() at
> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters) at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname) at Microsoft.ReportingServices.UI.Global.SecureAllAPI() at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level) at
> > Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args) at System.EventHandler.Invoke(Object sender,
> > EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at
> > System.Web.UI.Control.InitRecursive(Control namingContainer) at
> > System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!ea0!11/10/2004-08:05:46:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)|||That did it! Thanks Mike!
Could not establish trust relationship with remote server
Hi,
ERROR: The underlying connection was closed: Could not establish trust
relationship with remote server.
Iâ'm not able to start the Report Manager (https://myserver/reports) Webapp
using SSL. The WebApp https://myserver/reportserver is working fine.
My current related RSWebApplication.config is
<ReportServerUrl>https://myserver/reportserver.com/reportserver</ReportServerUrl>
My current related RSReportServer.config are:
<Add Key="SecureConnectionLevel" Value="3"/>
<UrlRoot>https:// myserver/reportserver.com/reportserver</UrlRoot>
My Environment:
- SSL Certificate issued to the myserver.com
- Win2003 Server with SQL Server 2000 Enterprise SP3
- Reporting Server SP1
- all related Services are running with a Domain-User Account with local
Admin rights (for the moment)
If I disable SSL (on IIS and within Conf-Files). I am able to start the
Report Manger.
Please helpâ?¦..my server should go live at the end of this weekâ?¦..:-(((
Many thanks
Dominic
Here is the Error Part from the ReportServerWebApp_xxxxx Log:
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)Sorry...here the right config file parts...I did some mixture while replacing
my real values...
My current related RSWebApplication.config is:
<ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
My current related RSReportServer.config are:
<Add Key="SecureConnectionLevel" Value="3"/>
<UrlRoot>https://myserver.com/reportserver</UrlRoot>
and - of course - the path I'm using within Internet Explorer is
https://myserver.com/reports|||Hi,
can you check you logfiles for web app and report server and see what errors
do you receive?
Andrej
"Dominic" <Dominic@.discussions.microsoft.com> wrote in message
news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> Sorry...here the right config file parts...I did some mixture while
replacing
> my real values...
> My current related RSWebApplication.config is:
> <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> My current related RSReportServer.config are:
> <Add Key="SecureConnectionLevel" Value="3"/>
> <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> and - of course - the path I'm using within Internet Explorer is
> https://myserver.com/reports|||Hi,
Hmmm...I checked also the Windows Application Event Manager. If I browse to
http://myserver.com/reports Iâ'm getting crypt23 error messages. If I browse
to http://myserver.com/reportservrer - everything is fine. But both are using
the same SSL Certificate. Below the error message:
Failed auto update retrieval of third-party root list sequence number from:
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt>
with error: The specified server cannot perform the requested operation.
There is no error within In the logfile ReportServerService__xxxxxx.log.
Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
Best Regards,
Dominic
"Andrej Hudoklin" wrote:
> Hi,
> can you check you logfiles for web app and report server and see what errors
> do you receive?
>
> Andrej
>
> "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > Sorry...here the right config file parts...I did some mixture while
> replacing
> > my real values...
> >
> > My current related RSWebApplication.config is:
> > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > My current related RSReportServer.config are:
> > <Add Key="SecureConnectionLevel" Value="3"/>
> > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> >
> > and - of course - the path I'm using within Internet Explorer is
> > https://myserver.com/reports
>
>|||Well I have the same error with a customer of mine.
Have tried everything and I do not have any idea what else to try.
I'll try to reinstall RS and then see if it will be better.
Please notify me if you'll find a solution.
Regards,
Andrej
"Dominic" <Dominic@.discussions.microsoft.com> wrote in message
news:51189156-E423-419C-BFF9-3B308DED72FF@.microsoft.com...
> Hi,
> Hmmm...I checked also the Windows Application Event Manager. If I browse
to
> http://myserver.com/reports I'm getting crypt23 error messages. If I
browse
> to http://myserver.com/reportservrer - everything is fine. But both are
using
> the same SSL Certificate. Below the error message:
> Failed auto update retrieval of third-party root list sequence number
from:
>
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/
en/authrootseq.txt>
> with error: The specified server cannot perform the requested operation.
> There is no error within In the logfile ReportServerService__xxxxxx.log.
> Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
> 3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
> closed: Could not establish trust relationship with remote server.
> w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
> establish trust relationship with remote server.
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
>
> Best Regards,
> Dominic
>
> "Andrej Hudoklin" wrote:
> > Hi,
> >
> > can you check you logfiles for web app and report server and see what
errors
> > do you receive?
> >
> >
> > Andrej
> >
> >
> >
> > "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> > news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > > Sorry...here the right config file parts...I did some mixture while
> > replacing
> > > my real values...
> > >
> > > My current related RSWebApplication.config is:
> > > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > > My current related RSReportServer.config are:
> > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> > >
> > > and - of course - the path I'm using within Internet Explorer is
> > > https://myserver.com/reports
> >
> >
> >|||Hi Andrej
...did you found a solution? Did a reinstall resolve your problem? Iâ've
still no solution..:-(
Regards,
Dominic
"Andrej Hudoklin" wrote:
> Well I have the same error with a customer of mine.
> Have tried everything and I do not have any idea what else to try.
> I'll try to reinstall RS and then see if it will be better.
> Please notify me if you'll find a solution.
>
> Regards,
> Andrej
>
> "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> news:51189156-E423-419C-BFF9-3B308DED72FF@.microsoft.com...
> > Hi,
> >
> > Hmmm...I checked also the Windows Application Event Manager. If I browse
> to
> > http://myserver.com/reports I'm getting crypt23 error messages. If I
> browse
> > to http://myserver.com/reportservrer - everything is fine. But both are
> using
> > the same SSL Certificate. Below the error message:
> > Failed auto update retrieval of third-party root list sequence number
> from:
> >
> <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/
> en/authrootseq.txt>
> > with error: The specified server cannot perform the requested operation.
> >
> > There is no error within In the logfile ReportServerService__xxxxxx.log.
> >
> > Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
> > 3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server.
> > at System.Net.HttpWebRequest.CheckFinalStatus()
> > at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
> asyncResult)
> > at System.Net.HttpWebRequest.GetRequestStream()
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at
> Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level)
> > at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args)
> > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > at System.Web.UI.Control.OnInit(EventArgs e)
> > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)
> >
> >
> > Best Regards,
> > Dominic
> >
> >
> > "Andrej Hudoklin" wrote:
> >
> > > Hi,
> > >
> > > can you check you logfiles for web app and report server and see what
> errors
> > > do you receive?
> > >
> > >
> > > Andrej
> > >
> > >
> > >
> > > "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> > > news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > > > Sorry...here the right config file parts...I did some mixture while
> > > replacing
> > > > my real values...
> > > >
> > > > My current related RSWebApplication.config is:
> > > > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > > > My current related RSReportServer.config are:
> > > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> > > >
> > > > and - of course - the path I'm using within Internet Explorer is
> > > > https://myserver.com/reports
> > >
> > >
> > >
>
>
ERROR: The underlying connection was closed: Could not establish trust
relationship with remote server.
Iâ'm not able to start the Report Manager (https://myserver/reports) Webapp
using SSL. The WebApp https://myserver/reportserver is working fine.
My current related RSWebApplication.config is
<ReportServerUrl>https://myserver/reportserver.com/reportserver</ReportServerUrl>
My current related RSReportServer.config are:
<Add Key="SecureConnectionLevel" Value="3"/>
<UrlRoot>https:// myserver/reportserver.com/reportserver</UrlRoot>
My Environment:
- SSL Certificate issued to the myserver.com
- Win2003 Server with SQL Server 2000 Enterprise SP3
- Reporting Server SP1
- all related Services are running with a Domain-User Account with local
Admin rights (for the moment)
If I disable SSL (on IIS and within Conf-Files). I am able to start the
Report Manger.
Please helpâ?¦..my server should go live at the end of this weekâ?¦..:-(((
Many thanks
Dominic
Here is the Error Part from the ReportServerWebApp_xxxxx Log:
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)Sorry...here the right config file parts...I did some mixture while replacing
my real values...
My current related RSWebApplication.config is:
<ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
My current related RSReportServer.config are:
<Add Key="SecureConnectionLevel" Value="3"/>
<UrlRoot>https://myserver.com/reportserver</UrlRoot>
and - of course - the path I'm using within Internet Explorer is
https://myserver.com/reports|||Hi,
can you check you logfiles for web app and report server and see what errors
do you receive?
Andrej
"Dominic" <Dominic@.discussions.microsoft.com> wrote in message
news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> Sorry...here the right config file parts...I did some mixture while
replacing
> my real values...
> My current related RSWebApplication.config is:
> <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> My current related RSReportServer.config are:
> <Add Key="SecureConnectionLevel" Value="3"/>
> <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> and - of course - the path I'm using within Internet Explorer is
> https://myserver.com/reports|||Hi,
Hmmm...I checked also the Windows Application Event Manager. If I browse to
http://myserver.com/reports Iâ'm getting crypt23 error messages. If I browse
to http://myserver.com/reportservrer - everything is fine. But both are using
the same SSL Certificate. Below the error message:
Failed auto update retrieval of third-party root list sequence number from:
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt>
with error: The specified server cannot perform the requested operation.
There is no error within In the logfile ReportServerService__xxxxxx.log.
Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
closed: Could not establish trust relationship with remote server.
w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The underlying connection was closed: Could not
establish trust relationship with remote server.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
Best Regards,
Dominic
"Andrej Hudoklin" wrote:
> Hi,
> can you check you logfiles for web app and report server and see what errors
> do you receive?
>
> Andrej
>
> "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > Sorry...here the right config file parts...I did some mixture while
> replacing
> > my real values...
> >
> > My current related RSWebApplication.config is:
> > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > My current related RSReportServer.config are:
> > <Add Key="SecureConnectionLevel" Value="3"/>
> > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> >
> > and - of course - the path I'm using within Internet Explorer is
> > https://myserver.com/reports
>
>|||Well I have the same error with a customer of mine.
Have tried everything and I do not have any idea what else to try.
I'll try to reinstall RS and then see if it will be better.
Please notify me if you'll find a solution.
Regards,
Andrej
"Dominic" <Dominic@.discussions.microsoft.com> wrote in message
news:51189156-E423-419C-BFF9-3B308DED72FF@.microsoft.com...
> Hi,
> Hmmm...I checked also the Windows Application Event Manager. If I browse
to
> http://myserver.com/reports I'm getting crypt23 error messages. If I
browse
> to http://myserver.com/reportservrer - everything is fine. But both are
using
> the same SSL Certificate. Below the error message:
> Failed auto update retrieval of third-party root list sequence number
from:
>
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/
en/authrootseq.txt>
> with error: The specified server cannot perform the requested operation.
> There is no error within In the logfile ReportServerService__xxxxxx.log.
> Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
> 3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
> closed: Could not establish trust relationship with remote server.
> w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
> establish trust relationship with remote server.
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
>
> Best Regards,
> Dominic
>
> "Andrej Hudoklin" wrote:
> > Hi,
> >
> > can you check you logfiles for web app and report server and see what
errors
> > do you receive?
> >
> >
> > Andrej
> >
> >
> >
> > "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> > news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > > Sorry...here the right config file parts...I did some mixture while
> > replacing
> > > my real values...
> > >
> > > My current related RSWebApplication.config is:
> > > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > > My current related RSReportServer.config are:
> > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> > >
> > > and - of course - the path I'm using within Internet Explorer is
> > > https://myserver.com/reports
> >
> >
> >|||Hi Andrej
...did you found a solution? Did a reinstall resolve your problem? Iâ've
still no solution..:-(
Regards,
Dominic
"Andrej Hudoklin" wrote:
> Well I have the same error with a customer of mine.
> Have tried everything and I do not have any idea what else to try.
> I'll try to reinstall RS and then see if it will be better.
> Please notify me if you'll find a solution.
>
> Regards,
> Andrej
>
> "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> news:51189156-E423-419C-BFF9-3B308DED72FF@.microsoft.com...
> > Hi,
> >
> > Hmmm...I checked also the Windows Application Event Manager. If I browse
> to
> > http://myserver.com/reports I'm getting crypt23 error messages. If I
> browse
> > to http://myserver.com/reportservrer - everything is fine. But both are
> using
> > the same SSL Certificate. Below the error message:
> > Failed auto update retrieval of third-party root list sequence number
> from:
> >
> <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/
> en/authrootseq.txt>
> > with error: The specified server cannot perform the requested operation.
> >
> > There is no error within In the logfile ReportServerService__xxxxxx.log.
> >
> > Here is the the errorpart from the ReportServerWebApp__xxxxxx.log:
> > 3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: The underlying connection was
> > closed: Could not establish trust relationship with remote server.
> > w3wp!ui!1454!9/1/2004-11:26:59:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The underlying connection was closed: Could not
> > establish trust relationship with remote server.
> > at System.Net.HttpWebRequest.CheckFinalStatus()
> > at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
> asyncResult)
> > at System.Net.HttpWebRequest.GetRequestStream()
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at
> > Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at
> Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level)
> > at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args)
> > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > at System.Web.UI.Control.OnInit(EventArgs e)
> > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!1454!9/1/2004-11:27:01:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)
> >
> >
> > Best Regards,
> > Dominic
> >
> >
> > "Andrej Hudoklin" wrote:
> >
> > > Hi,
> > >
> > > can you check you logfiles for web app and report server and see what
> errors
> > > do you receive?
> > >
> > >
> > > Andrej
> > >
> > >
> > >
> > > "Dominic" <Dominic@.discussions.microsoft.com> wrote in message
> > > news:8284C729-96D9-4147-8E01-9EF55B3031CC@.microsoft.com...
> > > > Sorry...here the right config file parts...I did some mixture while
> > > replacing
> > > > my real values...
> > > >
> > > > My current related RSWebApplication.config is:
> > > > <ReportServerUrl>https://myserver.com/reportserver</ReportServerUrl>
> > > > My current related RSReportServer.config are:
> > > > <Add Key="SecureConnectionLevel" Value="3"/>
> > > > <UrlRoot>https://myserver.com/reportserver</UrlRoot>
> > > >
> > > > and - of course - the path I'm using within Internet Explorer is
> > > > https://myserver.com/reports
> > >
> > >
> > >
>
>
Could not establish secure channel for SSL/TLS.
I think I am having an installation issue. This is the error I get
The underlying connection was closed: Could not establish secure channel for SSL/TLS.
I am using a server that already has a certificate installed.
Any IdeasHave you fixed this yet, I have same error. Cheers|||John wrote:
> Have you fixed this yet, I have same error. Cheers
do you have certificate from root?
The underlying connection was closed: Could not establish secure channel for SSL/TLS.
I am using a server that already has a certificate installed.
Any IdeasHave you fixed this yet, I have same error. Cheers|||John wrote:
> Have you fixed this yet, I have same error. Cheers
do you have certificate from root?
Could not establish secure channel for SSL/TLS.
Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
The //localhost/reportserver give's me XXX/ReportServer - /
----
Microsoft SQL Server Reporting Services Version 8.00.1038.00
But when connecting to //localhost/reports i get the followwing error.
"
The underlying connection was closed: Could not establish secure channel for
SSL/TLS."
Never installed ssl, and have tried all the security and other ideas so far.
Can anyone help.
Thanks
JohnJohn wrote:
> Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
> The //localhost/reportserver give's me XXX/ReportServer - /
> ----
> Microsoft SQL Server Reporting Services Version 8.00.1038.00
> But when connecting to //localhost/reports i get the followwing error.
> "
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS."
> Never installed ssl, and have tried all the security and other ideas so far.
> Can anyone help.
> Thanks
> John
>
if you have certificate from root,then you have to start trusting it
with you server too :)
try to install it under trusted root certification authorities.|||did you find a solution for this issue?
Grego
From http://www.developmentnow.com/g/115_2005_10_0_0_626044/Could-not-establish-secure-channel-for-SSLTLS-.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
The //localhost/reportserver give's me XXX/ReportServer - /
----
Microsoft SQL Server Reporting Services Version 8.00.1038.00
But when connecting to //localhost/reports i get the followwing error.
"
The underlying connection was closed: Could not establish secure channel for
SSL/TLS."
Never installed ssl, and have tried all the security and other ideas so far.
Can anyone help.
Thanks
JohnJohn wrote:
> Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
> The //localhost/reportserver give's me XXX/ReportServer - /
> ----
> Microsoft SQL Server Reporting Services Version 8.00.1038.00
> But when connecting to //localhost/reports i get the followwing error.
> "
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS."
> Never installed ssl, and have tried all the security and other ideas so far.
> Can anyone help.
> Thanks
> John
>
if you have certificate from root,then you have to start trusting it
with you server too :)
try to install it under trusted root certification authorities.|||did you find a solution for this issue?
Grego
From http://www.developmentnow.com/g/115_2005_10_0_0_626044/Could-not-establish-secure-channel-for-SSLTLS-.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Could not establish secure channel for SSL/TLS
We are getting the same error. We changed the asp timeout at the master property level, and we are now getting the same error. I have checked the RSWebApplication.config and it matches the server name.
I have gone through the other posts around this issue, but haven't been able to resolve the issue. I am at the point of reinstalling Reporting Services and setting up all of our reports again.
Any help would be appreciated!!!I found no solution ... and try to uninstall Report Services to make a new
installation. Also was not able to uninstall ... had to move to a new Server
:(
Tiago Andrade e Silva
"kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> We are getting the same error. We changed the asp timeout at the master
property level, and we are now getting the same error. I have checked the
RSWebApplication.config and it matches the server name.
> I have gone through the other posts around this issue, but haven't been
able to resolve the issue. I am at the point of reinstalling Reporting
Services and setting up all of our reports again.
> Any help would be appreciated!!!
>|||SSL is not a requirement for Reporting services. Try setting
SecureConnectionLevel to 0 in RSReportsErver.config - there are more details
about it in the books online.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> Tiago,
> Did you ever get a resolution or a workaround from MS on this issue? We
are having the same problem, and IIS on the report server is NOT configured
for SSL! Do you know if SSL is a requirement for Reporting Services?
> Thanks,
> Aisha
> "Tiago Andrade e Silva" wrote:
> > I found no solution ... and try to uninstall Report Services to make a
new
> > installation. Also was not able to uninstall ... had to move to a new
Server
> > :(
> >
> > Tiago Andrade e Silva
> > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
> > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > We are getting the same error. We changed the asp timeout at the
master
> > property level, and we are now getting the same error. I have checked
the
> > RSWebApplication.config and it matches the server name.
> > >
> > > I have gone through the other posts around this issue, but haven't
been
> > able to resolve the issue. I am at the point of reinstalling Reporting
> > Services and setting up all of our reports again.
> > >
> > > Any help would be appreciated!!!
> > >
> >
> >
> >|||The error in the title of this post is "Could not establish secure channel
for SSL/TLS". You should never get this error if you are not using SSL, are
you saying you are getting it? What is the exact request that fails with
this error?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> Tudor,
> That has already been established per RSReportServer.config , <Add
Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we are
NOT USING SSL.
> What books online are you talking about? Can you provide more details on
this? Seems like several others have the same issue, like Tiago, and he
never found a resolution and ended up moving Reporting Services to another
server? Is that the resolution? What if it starts happening on the new
server?
> Please provide more helpful information on this issue. Most of these
threads with this issue have been started since May and no resolution posted
thus far?
> Aisha
> "Tudor Trufinescu (MSFT)" wrote:
> > SSL is not a requirement for Reporting services. Try setting
> > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
details
> > about it in the books online.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > Tiago,
> > >
> > > Did you ever get a resolution or a workaround from MS on this issue?
We
> > are having the same problem, and IIS on the report server is NOT
configured
> > for SSL! Do you know if SSL is a requirement for Reporting Services?
> > >
> > > Thanks,
> > > Aisha
> > >
> > > "Tiago Andrade e Silva" wrote:
> > >
> > > > I found no solution ... and try to uninstall Report Services to
make a
> > new
> > > > installation. Also was not able to uninstall ... had to move to a
new
> > Server
> > > > :(
> > > >
> > > > Tiago Andrade e Silva
> > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
wrote in
> > > > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > We are getting the same error. We changed the asp timeout at the
> > master
> > > > property level, and we are now getting the same error. I have
checked
> > the
> > > > RSWebApplication.config and it matches the server name.
> > > > >
> > > > > I have gone through the other posts around this issue, but haven't
> > been
> > > > able to resolve the issue. I am at the point of reinstalling
Reporting
> > > > Services and setting up all of our reports again.
> > > > >
> > > > > Any help would be appreciated!!!
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||What is the URL in RSWebApplication.config ?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:78F9C232-00B0-4611-9048-7D40CD3D9399@.microsoft.com...
> Tudor,
> Here is a copy of the ReportServerWebApp__08_04_2004_08_56_18.log from
this morning when I tried accessing http://myservername/reports:
> <begin ReportServerWebApp log file>
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Central Daylight Time</TimeZone>
> <Path>D:\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__08_04_2004_08_56_18.log</Path>
> <SystemName>myservername</SystemName>
> <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> <OSVersion>5.0.2195.0</OSVersion>
> </Header>
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: The underlying connection
was closed: Could not establish secure channel for SSL/TLS.
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
establish secure channel for SSL/TLS. -->
System.ComponentModel.Win32Exception: The function completed successfully,
but must be called again to complete the context
> -- End of inner exception stack trace --
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
> at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
> </end ReportServerWebApp log file>
> Here is the IIS log from this morning:
> <begin IIS log>
> #Software: Microsoft Internet Information Services 5.0
> #Version: 1.0
> #Date: 2004-08-04 13:56:18
> #Fields: date time s-port cs-method cs-uri-stem cs-uri-query sc-status
cs(User-Agent)
> 2004-08-04 13:56:18 80 GET /reports - 401
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/ - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/Home.aspx - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 GET /reports/Pages/Folder.aspx - 500
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/js/ReportingServices.js - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/styles/ReportingServices.css - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/blank.gif - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/48error.jpg - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> </end IIS log>
> Please let me know if you need any other information. I didn't see a
place to upload files, so that is why I am just putting the information in
here. Also, if you search this newsgroup for the "Could not establish
secure channel for SSL/TLS" error, you will find some other posts with users
with this same problem when the SecureConnectionLevel Value = 0.
> Thanks,
> Aisha
>
> "Tudor Trufinescu (MSFT)" wrote:
> > The error in the title of this post is "Could not establish secure
channel
> > for SSL/TLS". You should never get this error if you are not using SSL,
are
> > you saying you are getting it? What is the exact request that fails with
> > this error?
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> > > Tudor,
> > >
> > > That has already been established per RSReportServer.config , <Add
> > Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we
are
> > NOT USING SSL.
> > >
> > > What books online are you talking about? Can you provide more details
on
> > this? Seems like several others have the same issue, like Tiago, and he
> > never found a resolution and ended up moving Reporting Services to
another
> > server? Is that the resolution? What if it starts happening on the new
> > server?
> > >
> > > Please provide more helpful information on this issue. Most of these
> > threads with this issue have been started since May and no resolution
posted
> > thus far?
> > >
> > > Aisha
> > >
> > > "Tudor Trufinescu (MSFT)" wrote:
> > >
> > > > SSL is not a requirement for Reporting services. Try setting
> > > > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
> > details
> > > > about it in the books online.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > > > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > > > Tiago,
> > > > >
> > > > > Did you ever get a resolution or a workaround from MS on this
issue?
> > We
> > > > are having the same problem, and IIS on the report server is NOT
> > configured
> > > > for SSL! Do you know if SSL is a requirement for Reporting
Services?
> > > > >
> > > > > Thanks,
> > > > > Aisha
> > > > >
> > > > > "Tiago Andrade e Silva" wrote:
> > > > >
> > > > > > I found no solution ... and try to uninstall Report Services to
> > make a
> > > > new
> > > > > > installation. Also was not able to uninstall ... had to move to
a
> > new
> > > > Server
> > > > > > :(
> > > > > >
> > > > > > Tiago Andrade e Silva
> > > > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
> > wrote in
> > > > > > message
news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > > > We are getting the same error. We changed the asp timeout at
the
> > > > master
> > > > > > property level, and we are now getting the same error. I have
> > checked
> > > > the
> > > > > > RSWebApplication.config and it matches the server name.
> > > > > > >
> > > > > > > I have gone through the other posts around this issue, but
haven't
> > > > been
> > > > > > able to resolve the issue. I am at the point of reinstalling
> > Reporting
> > > > > > Services and setting up all of our reports again.
> > > > > > >
> > > > > > > Any help would be appreciated!!!
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
I have gone through the other posts around this issue, but haven't been able to resolve the issue. I am at the point of reinstalling Reporting Services and setting up all of our reports again.
Any help would be appreciated!!!I found no solution ... and try to uninstall Report Services to make a new
installation. Also was not able to uninstall ... had to move to a new Server
:(
Tiago Andrade e Silva
"kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> We are getting the same error. We changed the asp timeout at the master
property level, and we are now getting the same error. I have checked the
RSWebApplication.config and it matches the server name.
> I have gone through the other posts around this issue, but haven't been
able to resolve the issue. I am at the point of reinstalling Reporting
Services and setting up all of our reports again.
> Any help would be appreciated!!!
>|||SSL is not a requirement for Reporting services. Try setting
SecureConnectionLevel to 0 in RSReportsErver.config - there are more details
about it in the books online.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> Tiago,
> Did you ever get a resolution or a workaround from MS on this issue? We
are having the same problem, and IIS on the report server is NOT configured
for SSL! Do you know if SSL is a requirement for Reporting Services?
> Thanks,
> Aisha
> "Tiago Andrade e Silva" wrote:
> > I found no solution ... and try to uninstall Report Services to make a
new
> > installation. Also was not able to uninstall ... had to move to a new
Server
> > :(
> >
> > Tiago Andrade e Silva
> > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com> wrote in
> > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > We are getting the same error. We changed the asp timeout at the
master
> > property level, and we are now getting the same error. I have checked
the
> > RSWebApplication.config and it matches the server name.
> > >
> > > I have gone through the other posts around this issue, but haven't
been
> > able to resolve the issue. I am at the point of reinstalling Reporting
> > Services and setting up all of our reports again.
> > >
> > > Any help would be appreciated!!!
> > >
> >
> >
> >|||The error in the title of this post is "Could not establish secure channel
for SSL/TLS". You should never get this error if you are not using SSL, are
you saying you are getting it? What is the exact request that fails with
this error?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> Tudor,
> That has already been established per RSReportServer.config , <Add
Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we are
NOT USING SSL.
> What books online are you talking about? Can you provide more details on
this? Seems like several others have the same issue, like Tiago, and he
never found a resolution and ended up moving Reporting Services to another
server? Is that the resolution? What if it starts happening on the new
server?
> Please provide more helpful information on this issue. Most of these
threads with this issue have been started since May and no resolution posted
thus far?
> Aisha
> "Tudor Trufinescu (MSFT)" wrote:
> > SSL is not a requirement for Reporting services. Try setting
> > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
details
> > about it in the books online.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > Tiago,
> > >
> > > Did you ever get a resolution or a workaround from MS on this issue?
We
> > are having the same problem, and IIS on the report server is NOT
configured
> > for SSL! Do you know if SSL is a requirement for Reporting Services?
> > >
> > > Thanks,
> > > Aisha
> > >
> > > "Tiago Andrade e Silva" wrote:
> > >
> > > > I found no solution ... and try to uninstall Report Services to
make a
> > new
> > > > installation. Also was not able to uninstall ... had to move to a
new
> > Server
> > > > :(
> > > >
> > > > Tiago Andrade e Silva
> > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
wrote in
> > > > message news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > We are getting the same error. We changed the asp timeout at the
> > master
> > > > property level, and we are now getting the same error. I have
checked
> > the
> > > > RSWebApplication.config and it matches the server name.
> > > > >
> > > > > I have gone through the other posts around this issue, but haven't
> > been
> > > > able to resolve the issue. I am at the point of reinstalling
Reporting
> > > > Services and setting up all of our reports again.
> > > > >
> > > > > Any help would be appreciated!!!
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||What is the URL in RSWebApplication.config ?
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray" <Ray@.discussions.microsoft.com> wrote in message
news:78F9C232-00B0-4611-9048-7D40CD3D9399@.microsoft.com...
> Tudor,
> Here is a copy of the ReportServerWebApp__08_04_2004_08_56_18.log from
this morning when I tried accessing http://myservername/reports:
> <begin ReportServerWebApp log file>
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Central Daylight Time</TimeZone>
> <Path>D:\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__08_04_2004_08_56_18.log</Path>
> <SystemName>myservername</SystemName>
> <OSName>Microsoft Windows NT 5.0.2195.0</OSName>
> <OSVersion>5.0.2195.0</OSVersion>
> </Header>
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: The underlying connection
was closed: Could not establish secure channel for SSL/TLS.
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The underlying connection was closed: Could not
establish secure channel for SSL/TLS. -->
System.ComponentModel.Win32Exception: The function completed successfully,
but must be called again to complete the context
> -- End of inner exception stack trace --
> at System.Net.HttpWebRequest.CheckFinalStatus()
> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
asyncResult)
> at System.Net.HttpWebRequest.GetRequestStream()
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
> at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> aspnet_wp!ui!20c!8/4/2004-08:56:18:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
> </end ReportServerWebApp log file>
> Here is the IIS log from this morning:
> <begin IIS log>
> #Software: Microsoft Internet Information Services 5.0
> #Version: 1.0
> #Date: 2004-08-04 13:56:18
> #Fields: date time s-port cs-method cs-uri-stem cs-uri-query sc-status
cs(User-Agent)
> 2004-08-04 13:56:18 80 GET /reports - 401
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/ - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /reports/Home.aspx - 302
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 POST /ReportServer/reportservice.asmx - 403 -
> 2004-08-04 13:56:18 80 GET /reports/Pages/Folder.aspx - 500
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/js/ReportingServices.js - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/styles/ReportingServices.css - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/blank.gif - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 2004-08-04 13:56:18 80 GET /Reports/images/48error.jpg - 304
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> </end IIS log>
> Please let me know if you need any other information. I didn't see a
place to upload files, so that is why I am just putting the information in
here. Also, if you search this newsgroup for the "Could not establish
secure channel for SSL/TLS" error, you will find some other posts with users
with this same problem when the SecureConnectionLevel Value = 0.
> Thanks,
> Aisha
>
> "Tudor Trufinescu (MSFT)" wrote:
> > The error in the title of this post is "Could not establish secure
channel
> > for SSL/TLS". You should never get this error if you are not using SSL,
are
> > you saying you are getting it? What is the exact request that fails with
> > this error?
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > news:10AC1BA4-4429-455E-B6A6-3EF528A8536D@.microsoft.com...
> > > Tudor,
> > >
> > > That has already been established per RSReportServer.config , <Add
> > Key="SecureConnectionLevel" Value="0"/>. The value is set to 0 and we
are
> > NOT USING SSL.
> > >
> > > What books online are you talking about? Can you provide more details
on
> > this? Seems like several others have the same issue, like Tiago, and he
> > never found a resolution and ended up moving Reporting Services to
another
> > server? Is that the resolution? What if it starts happening on the new
> > server?
> > >
> > > Please provide more helpful information on this issue. Most of these
> > threads with this issue have been started since May and no resolution
posted
> > thus far?
> > >
> > > Aisha
> > >
> > > "Tudor Trufinescu (MSFT)" wrote:
> > >
> > > > SSL is not a requirement for Reporting services. Try setting
> > > > SecureConnectionLevel to 0 in RSReportsErver.config - there are more
> > details
> > > > about it in the books online.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > > "Ray" <Ray@.discussions.microsoft.com> wrote in message
> > > > news:F9012D1C-5D5D-4348-84AA-3C88A88C8EAA@.microsoft.com...
> > > > > Tiago,
> > > > >
> > > > > Did you ever get a resolution or a workaround from MS on this
issue?
> > We
> > > > are having the same problem, and IIS on the report server is NOT
> > configured
> > > > for SSL! Do you know if SSL is a requirement for Reporting
Services?
> > > > >
> > > > > Thanks,
> > > > > Aisha
> > > > >
> > > > > "Tiago Andrade e Silva" wrote:
> > > > >
> > > > > > I found no solution ... and try to uninstall Report Services to
> > make a
> > > > new
> > > > > > installation. Also was not able to uninstall ... had to move to
a
> > new
> > > > Server
> > > > > > :(
> > > > > >
> > > > > > Tiago Andrade e Silva
> > > > > > "kbunch@.gapac.com" <kbunch@.gapac.com@.discussions.microsoft.com>
> > wrote in
> > > > > > message
news:1C5176BE-6741-4758-9B6D-FA583E84B26C@.microsoft.com...
> > > > > > > We are getting the same error. We changed the asp timeout at
the
> > > > master
> > > > > > property level, and we are now getting the same error. I have
> > checked
> > > > the
> > > > > > RSWebApplication.config and it matches the server name.
> > > > > > >
> > > > > > > I have gone through the other posts around this issue, but
haven't
> > > > been
> > > > > > able to resolve the issue. I am at the point of reinstalling
> > Reporting
> > > > > > Services and setting up all of our reports again.
> > > > > > >
> > > > > > > Any help would be appreciated!!!
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Subscribe to:
Posts (Atom)