I was working with a colleague of mine, and ran into a Reporting Services exception when accessing Report Manager. We were trying to get a wildcard SSL certificate set up on the machine, and ran through all the basic checks in my previous articles, but still threw this error: ERROR: System.Net.WebException: The underlying connection was […]
You are browsing archives for
Month: March 2017
The client and server cannot communicate...
This is a 3rd installment of the error “The client and server cannot communicate, because they do not possess a common algorithm“. You can find the first 2 blogs here: Part 1 Part 2 In Part 1, I alluded to another cause of the SCHANNEL error, and it boils down to issues with the Ciphers […]
What client provider am I using to conne...
In my previous post, I discussed the following error, and how to resolve it. The client and server cannot communicate, because they do not possess a common algorithm In this post, I’m going to answer some common questions about the provider you are using to connect to SQL Server, and which updates you should apply […]
The client and server cannot communicate...
Let’s talk about TLS 1.2 Support for SQL Server. You may have seen the errors below when trying to start SQL Server after a reboot, or trying to connect to SQL Server: The client and server cannot communicate, because they do not possess a common algorithm A connection was successfully established with the server, but […]
What to do when you get errors binding S...
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, […]
Using Wildcard Certificates with Reporti...
I wanted to clear up an issue I see time to time with users trying to install a wild card certificate on their Report Server, and get the following error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel Consider the following scenario: You have successfully bound your wild […]