I am trying to configure SSRS 2008 on Windows Server 2008. It seems to work as expected when I access the web interface via HTTP, but when using HTTPS I get the following error message: "The main connection was closed: an unexpected error occurred while sending .
When viewing the log files, it turns out that the internal exception is "System.Net.Sockets.SocketException: existing connection was forcibly closed by the remote host." This makes me think that an error occurs when a service is called from Report Manager to a web service.
I configured both the web service and the report manager with SSL binding on a non-standard port (8091) using a certificate signed with my own CA certificate. The server certificate is installed (and used) by IIS7, and the CA certificate is added to the "trusted root certificate authorities" in the "Local Computer" certificate store.
A web search for a specific error message gives me a lot of information on how to deal with the problem if the client application is my own .NET application. The most common solution is to set the "ServicePointManager.SecurityProtocol" property to "SecurityProtocolType.Ssl3", but I think this is not possible for me when the client is a pre-compiled web application (report manager).
Any ideas?
UPDATE: Requests now fail with HTTP status 401: Unauthorized. "The stack trace in the log file tells me that an exception occurs in SoapHttpClientProtocol.ReadResponse, which I would expect" later "in SOAP processing than the previous error.
Any new ideas?
source share