To have a successful SSL Certificate binding to Reporting Services, it must have the 4 following properties:
|1. The certificate has to have a valid expiration date|
|2. The certificate has to have a Private Key|
|3. The certificate has to be Trusted|
|4. The certificate need to be created for Server Authentication|
Often times, people fail to check these things before trying to bind their certificates to Reporting Services, and it would fail. The above is 1 of the 2 reasons it would fail. The second reason would be because your Report Server is not clean of it’s URL or SSLCert reservations.
Perform the below steps before binding your SSL Certificate again, and if it fails to bind again, check with your Security Administrator on the certificate properties needed for Reporting Services.
You can also use the below steps if you are having trouble setting up HTTP URLs for Reporting Services, minus the portion about SSL Certificates.
How to clean the system of Reporting Services URLs, and rebind the URLs
If you have followed those steps from beginning to end, you should have a clean installation of Reporting Services to work with. If your certificate is failing to bind after this, you have an issue with your certificate. I hope this helps!