Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
davidfossil
Starting Member
1 Post |
 Posted - 2009-06-17 : 11:01:22
|
| I am trying to setup SSRS 2008 on Windows Server 2008. It seems to work asexpected when I access the web interface through HTTP, but when usingHTTPS the following error is what I get: "The underlying connection wasclosed: An unexpected error occurred on a send." From a look at the log files, it is revealed that the inner exception is"System.Net.Sockets.SocketException: An existing connection was forciblyclosed by the remote host". This makes me think, that the error occursduring a service call from the Report Manager to the web service. I have configured both the web service and the Report Manager with anSSL-binding on a non-default port (8091), using a certificate signed usingmy own CA certificate. The server certificate is installed in (and usedby) IIS7, and the CA certificate is added to "Trusted Root CertificateAuthorities" on the "Local Computer" certificate store. Searching the net for the specific error message(s) gives me a lot ofinformation on how to deal with the problem, if the client application ismy own .NET application. The most prevalent solution seems to be aboutsetting the property "ServicePointManager.SecurityProtocol" to"SecurityProtocolType.Ssl3", but I guess that is not possible for me to dowhen the client is a precompiled web application (Report Manager). Any ideas? |
|
|
|
|
|
Report Manager fails when trying to force SSL