Friday, June 29, 2018
Reporting Services ConfigMgr 2012 Secure Socket errors
Reporting Services ConfigMgr 2012 Secure Socket errors
I was setting up a single primary site for testing and kept hitting a wall with Reporting Services.
Web page would have this error:
| The underlying connection was closed: An unexpected error occurred on a send. |
D:Program FilesMicrosoft SQL ServerMSRS11.MSSQLSERVERReporting ServicesLogFiles
ui!ReportManager_0-2!d10!05/02/2013-13:00:41:: e ERROR: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
library!ReportServer_0-1!25c!05/02/2013-13:04:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: , Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The
operation you are attempting requires a secure connection (HTTPS).;
Exempt I wasnt running in SSL mode.
The web page would simply show "Connection not established" or several other errors as I poked around.
So after poking around, checking configuration settings of Reporting Services didnt reveal anything.
I looking up the error and found this post for 2008, since I had nothing to lose I tried it out.
http://support.microsoft.com/kb/2011889
Update the RSReportServer.config file using the following steps:
- In Windows Explorer, locate the ReportServer directory. The following path is the default path of this directory: C:Program FilesMicrosoft SQL ServerMSRS10.MSSQLSERVERReporting ServicesReportServer
- Right-click RSReportServer.config, click Open With, click Notepad and then click OK.
- Locate the following Add Key entry: <Add Key="SecureConnectionLevel" Value="2"/>
- Change the Value setting from 2 to 0.
