Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

OK. I have scoured the Internet for information on trying to fix this and found nothing that deals with my situation. I started here, that lead me to here, that lead me to looking at netsh commands for HTTP.

Understand: I have no problem what-so-ever accessing the Report Manager or Web Service using HTTP/80.

My problem is strictly getting HTTPS/443 to work and open up the exact same page that HTTP/80 uses. All I get is HTTP Error 404.

  • Build number for SQL and SSRS: 10.50.4270.0
  • My certificate is installed on the server
  • Windows Firewall is disabled, but I am just trying to bring HTTPS up locally on the server
  • I have configured everything as instructed by Microsoft in RSCM.
  • SSL configuration has been done through RSCM, and using that URL to attempt access
  • I have verified in netsh that the SSL certificate is binded on IP:port 443.
  • The registry keys under HKLM:\SYSTEM\CurrentControlSet\services\HTTP\Parameters\SslBindingInfo are present for 0.0.0.0:443.
  • In netsh show iplisten was not showing anything, so I add iplisten ipaddress=0.0.0.0, but that did not affect anything
  • Within my rsreportserver.config the SecureConnectionLevel is set to value="0"

I am stuck, what am I missing here to do or check?

EDIT
I just completed a fresh install on a brand new server, same result.

share|improve this question
    
Might be a stupid question, but have you told the reporting services config manager to use the certificate? –  mrdenny Feb 14 '13 at 20:59
    
Yes sir, sure did. –  Shawn Melton Feb 14 '13 at 23:29
    
I am installing it all on a second server that is supposed to be built the same way to see if I get the same results. –  Shawn Melton Feb 14 '13 at 23:30
add comment

1 Answer

up vote 3 down vote accepted

The problem has to do with the certifcate being used with SSRS. If your certificate is created with hostname.whatever.com, you can only access the Report URLs through that path, https: //hostname.whatever.com/Reports. If you were to try https:// 10.xxx.xxx.xxx/Reports (where the IP is the one on the server) you will receive the 404 errors.

So the fix for my situation:
I found the friendly name used to generate the certifcate on the server was dorked up. I am in the process of getting that fixed to be the correct fully qualifed DNS name of the server in use. I found this out by installing SQL Server Report Server on a server that had the certificate created with the correct name of the server being used.

Once I have that certificate corrected and verify will simply mark this as the correct answer.

EDIT Well another problem came up in trying to change the certificate. The admins of the server removed the certificate before I could properly remove it from RSCM. So now it will not bind to the new certificate because it already sees one binded. There is really no clean, easy way of fixing this since you don't have access to IIS (SSRS uses HTTP.sys). So following this KB, you have to go into NETSH to remove the binding(s). Which you will note in that KB article the link to NETSH does not provide much info, so use this one. I had to use the two following commands to delete the bindings on Window Server 2008 R2: WARNING: I am on a single, standalone server. If you are in a server farm or have multiple instances of SSRS running, be very careful with which SSL binding you delete.


This is after getting to the "netsh http>" prompt:
delete sslcert ipport=0.0.0.0.:443
delete sslcert ipport=[::]:443

I did that and then went into RSCM and selected the new certificate that was installed on teh server. That is not the end though, for some reason it kept removing the binding and showing "unknown" in the link. I stopped SSRS and then opened up the rsreportserver.config file and found the old ("bad") binding still was showing in the config file. I removed that went back into RSCM and started the service and it seemed to fix it.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.