Thursday, May 2, 2013

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.

Looking at the logs I would see this when trying to launch the Report URL:

D:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles

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 wasn't 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 didn't 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:
  1. In Windows Explorer, locate the ReportServer directory. The following path is the default path of this directory: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
  2. Right-click RSReportServer.config, click Open With, click Notepad and then click OK.
  3. Locate the following Add Key entry: <Add Key="SecureConnectionLevel" Value="2"/>
  4. Change the Value setting from 2 to 0.
I did stop and restart the SQL Reporting Services Service and checked my URL.  It worked.