IIS Default Web Site - Reports + ReportServer missing

Question

IIS Default Web Site - Reports + ReportServer missing

2Tall

SSChampion

Points: 14632
More actions
September 8, 2014 at 5:13 am

#310704

Hi to all, its been a while 🙂
I am in the process of testing migration of our ERP system from Windows 2003/SQL 2005 Standard to Windows 2008R2/SQL 2012 Standard.
The SQL 2012 server is hosting multiple databases which in turn require sites in IIS (ports 80 / 443 / 8080/8443 are all used by other apps).
I have used 'Reporting Services Configuration Manager' as follows:
Web Service URL
TCP Port = 8081
SSL Port = 9443
Report Manager URL
Virtual Directory = Reports
URLS
http://ServerName:8081/reports
https://ServerName:9443/reports
If I browse to http://ServerName:8081/reports I receive error below.
"The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. "
I note in IIS (IIS Manager v6.1) that expected folders Reports and ReportServer do not exist. I thought these were created during installation?
Any tips/advice very much appreciated.
Thanks,
Phil.
-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."
Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '
Tommy Cooper

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

2Tall SSChampion Points: 14632 More actions · Answer 1

Hi. Has anyone else come across error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." when browsing the reporting manager URL?

Thanks,

Phil.

-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."

Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '

Tommy Cooper

happycat59 One Orange Chip Points: 29387 More actions · Answer 2

Not sure what your error is but I would start with checking the SSL certificate that you are using .

Also, SSRS does not use IIS so you will not see anything to do with reporting services when you are using the IIS manager.

2Tall SSChampion Points: 14632 More actions · Answer 3

Thanks for the heads up on IIS, that explains that! As far as I am aware I am not using SSL or a certificate for SSRS? Reporting Services Configuration Manager > Web Service URL >

IP Address > All assigned

TCP Port > 80

SSL Certificate > (Not selected)

SSL Port > blank

Report Manager URL

If I click url http://ServerName/Reports I receive the error.

Thanks,

Phil.

-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."

Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '

Tommy Cooper

2Tall SSChampion Points: 14632 More actions · Answer 4

I am CONFUSED! I am unclear how Web Service URL and Report Manger URL interact and how SSRS uses certificates.

I managed to get past error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." by selecting a different TCP port (9443) and SSL Certificate within Web Service URL settings.

Even though I can now access SSRS 'Home' the icon from another hosted application is displayed before https://

Also https requested automatically redirect to https//

So http://server-name/Reports redirects to https://server-name/Reports. A certificate error is displayed even after installing the cert into Trusted Root Certification Authorities folder.

So to conclude:

I modified Web Service URL which removed/recreated bindings (a bit hit and miss, sometimes errors were generated regards not being able to create the binding)

Web Service URL now uses a different SSL certificate and SSL port (9443)

Report Manager URL uses the defaults (SSL cert and ports 80/443).

I can access SSRS 'Home' but only over https.

I still feel there is some sort of conflict with existing co-hosted applications + IIS web sites using the same certs/ports.

Kind Regards,

Phil.

-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."

Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '

Tommy Cooper