SQL Server 2000 & Reporting Services (Report Manager) SSL not working

Hi there!

My company is thinking about making the switch over from Crystal reports to RS and it's my job to install and test it over the next month. Unfortunately I seem to be stumbling at the first hurdle! The installation process went well together with the setup of the sample reports. At the moment I'm running this on my local development machine:

Windows XP
SQL Server 2000 SP4
Visual Studio.net 2003
IIS 5.1
RS 2000 SP2

Due to our company not having a CA for SSL I setup one on a windows 2003 server and generated a cert through here. This seems to work well (so I thought).

Access to the reports works excellent and I'm able to view and play around with these as well as deploy new ones. The problem lays in the Report Manager, for some reason I just can't access it. The error I'm getting is:

"The underlying connection was closed: Could not establish trust relationship with remote server." Which to me points towards a problem with SSL.

What I've done is to make sure it points tohttps://ianthomas/ReportServer in the configuration. The url gets tohttps://ianthomas/Reports/Pages/Folder.aspx and then displays the above error.

I've looked on google groups and it seems a lot of people have this error but the answers and solutions are vague or user specific.

There was a possible solution of moving the IIS host or Reports to the machine that generates the cert and host this from there, pointing back to my server, would this help at all?

I quote:
"But luckily there is another workaround that I discovered after many hours of trial and error - Reporting Services will use a certificate if it was generated on the SAME server where the IIS part of RS is running. So if you run into this problem, install the Certificate Authority component on the IIS server and use a certificate generated by that service." - SQLJunkies

Would this help me at all and how would I go about it? Just a matter or setting up another virtual dir in the other IIS and copying files over?

I appreciate any bit of Information anyone can give, I'm pulling my hair out here! Well.. what's left of it!

Thanks!

Ian Thomas
DBA in the working!

[2413 byte] By [IanThomas] at [2007-12-16]
# 1
Hi Ian,
Did you get around this? I dont particularly want to deploy a CA on the IIS server!
I guess the alternative would be to deploy a fully functioning CA that is visible to the Reporting Server. At this stage, not an option..
Brian:)
BrianSutherland at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Reporting Services...
# 2
hi Ian Thomas,
Did u solve the problem, if u solved the problem then tell me how did you sloved the problem
Thanks!
Jagan
RamaSatyaJaganK at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Reporting Services...
# 3

I just resolved the same issue.

Here are the dependecies:
-SSL Certificate
-rsreportserver.config ("UrlRoot")
-rswebapplication.config ("ReportServerURL")

Here's what happened to me.

My SSL Certificate was linked to a Virtual Server running Reporting Services. The 'url' of my certificate was 'reportserver.labdomain.com'. The SSL Certificate was valid.

When I looked in these configuration files, I noticed that these values were attached to the 'shortname' of my report server, i.e. 'reportserver', rather than the FQDN.

Instead of changing configuration, I just reissued a certificate to the 'shortname' and everything worked swimmingly.

Hope this helps.

Big SmileDylanBig Smile

DylanPhillips at 2007-9-9 > top of Msdn Tech,SQL Server,SQL Server Reporting Services...

SQL Server

Site Classified