This is an interesting error message that you might have seen while configuring TFS 2010 Beta 2 after you’ve installed SQL Server 2008 and have chosen to install and configure reporting services.
TFS 2010 deployment is broken down into two steps. In the first step, the product is simply “installed” – i.e. the files are copied to the destination location. The second step is the real deal: this is where the product is actually configured.
In the screenshot shown above, choosing the “Standard Single Server” option will result in default settings being chosen that are suitable for a simple, single-machine, deployment. After entering the account credentials, you will see the following message:
Notice the error message:
[ Reporting ] TFxxxxxx: 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.
Going to the Reporting Services Configuration Manager, you will notice that you have secure URLs on the “Web Service URL” (of the form https://myserver:443/ReportServer – you might see more than one, one for each of the IPv4 and IPv6 addresses) and “Report Manager URL” (e.g. https://myserver:443/Reports) panes.
Where did this come from?
Well, if you haven’t added them intentionally, chances are that you already had one or more self-signed certificates installed on your machine. The SQL Server 2008 installer seems to notice that and configure reporting services with both the non-secure (usually port 80) URL and secure URL(s) on port 443.
It does seem that having those secure URLs trips the TFS 2010 configuration wizard.
Can we remove HTTPS support (as the error suggests)?
You can try to remove HTTPS support by deleting the secure URLs, but that does not seem to have any effect, and the TFS 2010 configuration wizard will still complain about the secure settings.
I haven’t found a good way (yet) to resolve this other than deleting the self-signed certificate(s) that were present and re-installing SQL Server 2008… After that, Reporting Services is installed with no secure URLs added, and all seems to work fine; the configuration goes smoothly.
Unfortunately, binging around a little bit, I haven’t found a good explanation of this issue yet. I will update this post if I find anything more explanatory.
Finally, note that this is not something that is resolved by the first TFS 2010 Beta 2 patch that was released on December 8th and that resolved a few configuration-related issues. Brian Harry blogged about it back then in this post.
[Update – 1/4/2010]: ‘nuf said! The following thread has the _right_ solution:
http://social.msdn.microsoft.com/Forums/en-NZ/tfsprerelease/thread/2a77b1f7-7d47-4d61-aa9d-5839f384b2f3