22. April 2010 05:22
When I installed a brand new TFS 2010 instance, I was encountered with the following error message
[ Reporting ] TF255455: SQL Server Reporting Services is configured to require a secure connection. However, no HTTPS URL is configured with a valid certificate. Use the Reporting Services Configuration Manager to configure or remove HTTPS support. For more information see http://go.microsoft.com/fwlink/?LinkId=179982
The link that was provided did not work for (maybe it has been already fixed), however I found the solution on the MSDN Forums provided by Ed Holloway:
This issue is happening due to the way SQL RS enables (and enforces) HTTPS on a machine. If the SQL installer finds any certificates on the machine with the purpose set to * (anything) or server authentication it will set the SQL RS SecureConnectionLevel to 2, which requires HTTPS. (This can happen in a few other scenarios too, but this is the common one) So even though you may not have intended for RS to use SSL in this case, it is trying to enforce it.
NOTE: These directions will disable SSL for SQL RS.
To work around this
C:\Program Files\Microsoft SQL Server\MSRS10.<ServerInstance>\Reporting Services\ReportServer\rsreportserver.config
<Add Key="SecureConnectionLevel" Value="2"/> (Change from current value to 0)
Here is what the values mean:
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all.