Friday, March 9, 2012

ReportManager and SSL

I have a Reporting Services installation where I first implemented Forms
Authentication. I am now implementing SSL and have run into a problem. I
can access the report server through https://<servername>/reportserver,
howerver I cannot access the report manager using
https://<servername>/reports. I keep getting "The underlying connection was
closed: Could not establish trust relationship with remote server." I have
verified that the <URLRoot> key in the RSReportServer.config file and the
<ReportServerURL> key in the RSWebApplication.config file are in the format
https://<servername>/reportserver. My certificate has also been issued to
<servername>. Does anyone have any additional suggestions on fixing my
report manager problem?
Thank you in advance.Our experience has been that you can't change from non-SSL to SSL in
the same Reporting Services installation and have things work. The
procedure we have come up with is:
On the report server
1) uninstall Reporting Services using the uninstall from the RS
installation itself, not Add/Remove Programs.
2) delete the file with name starting with 1aedd7b5699f3d... at
<root>:\Documents and Settings\<machinename>\ASPNET\Application
Data\Microsoft\Crypto\RSA\<Some SID>
3) In Administrative Tools | Component Services | Component Services |
Computers | My Computer | COM+ Applications | , right-click on each of
IIS-{Default Web Site//Root/ReportServer}
IIS-{Default Web Site//Root/Reports}
and select Properties. Click the Advanced tab and uncheck "Disable
deletion". Delete each item.
4) Delete the Reporting Services databases (and the AdventureWorks
database if you installed it) from SQL Server.
5) Reboot.
6) Make sure your web server certificate is valid and was issued for
EXACTLY the correct machine name, case sensitive. If you are using a
cert from your own Enterprise CA and your CA does not chain up to a
root CA (doesn't have its own valid certificate from a real root CA),
use SelfSSL available at
http://www.microsoft.com/windowsserver2003/iis/downloads/default.mspx
to generate a cert that will work. You should probably use a Fully
Qualified Domain Name rather than a NetBIOS name for the certificate.
7) If the cert is good, reinstall Reporting Services and make sure that
you have checked the SSL box during the installation procedure. If the
installation throws _any_ error during the options-picking phase, exit
the installation, fix the problem, reboot, and start the installation
over again.
If anybody knows a better way to switch from non-SSL to SSL on a report
server please let me know. Some of this procedure may be superstition
but it works. Takes about 15 minutes once you've done it 20 or 30
times.
hth, and genuinely
Highly Obscure
Jim W wrote:
> I have a Reporting Services installation where I first implemented
> Forms Authentication. I am now implementing SSL and have run into a
> problem. I can access the report server through
> https://<servername>/reportserver, howerver I cannot access the
> report manager using https://<servername>/reports. I keep getting
> "The underlying connection was closed: Could not establish trust
> relationship with remote server." I have verified that the <URLRoot>
> key in the RSReportServer.config file and the <ReportServerURL> key
> in the RSWebApplication.config file are in the format
> https://<servername>/reportserver. My certificate has also been
> issued to <servername>. Does anyone have any additional suggestions
> on fixing my report manager problem?
> Thank you in advance.|||this may also be helpful:
http://sqljunkies.com/WebLog/roman/archive/category/370.aspx

No comments:

Post a Comment