32000 Error creating datasource

Just like many others have posted, I'm getting a 32000 error almost at the end of installing VS TFS. The error is occuring with the createds.exe which it looks like is what is supposed to set up the Reporting Services Datasource for Team Foundation Server. And before anybody tells me to try Bruce's link, that's no help, just like Gwyn said (http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=10564) and never got any further response.

Just for kicks, I tried running the same command from the command line to see what happened. Here is the actual error, with a bit more detail then "non-zero value: 3"

C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\uninstall>createdshttp://myserver/reportserver/reportservice.asmx TEST "Data source=myserver;initial catalog=BisDWDB" "MYDOMAIN\admin" "adminpass" 0 0

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The operation you are attempting requires a secure connection (HTTPS).
> Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The operation you are attempting requires a secure connection (HTTPS).
at Microsoft.ReportingServices.Library.RSService.EnsureHttpsLevel(HttpsLevel level)
at Microsoft.ReportingServices.WebServer.ReportingService.CreateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property[] Properties)
End of inner exception stack trace
at Microsoft.ReportingServices.WebServer.ReportingService.CreateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property[] Properties)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.VisualStudio.ELead.ReportManager.RosettaProxy.ReportingService.CreateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property[] Properties)
at Microsoft.VisualStudio.ELead.Tools.createds.Program.Run(String[] args)

Reporting Services doesn't let the call execute because it's not over a secure connection (https). But according to the installation guide, TFS doesn't support https. So, you can't create the datasource _without_ a secure connection, but you also can't run TFS _with_ a secure connection. I'm not exactly sure where this leaves the end user, but maybe someone else has suggestions?

[3462 byte] By [jcorra] at [2007-12-16]
# 1
The exception is coming from the server. It seems that the server (Report Server) or at least http://localhost has a certificate and has "Requires HTTPS" checked. Try to turn off the certificate on the server
BruceTaimanaMSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Setup...
# 2
I'm getting the exact same error. I checked to see if "requires http" was checked on the 2 virtual directories of "Reports" and "ReportServer" under the Properties/Directory Security/Secure communications....and it wasn't.

Any other ideas?

brassringMike at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Setup...
# 3

You may be getting the same message but experiencing a completely different error. I think this is just a general error message that you get if the call to the Reporting Services Web Service to create a data source fails for any reason. Try opening up a command prompt and running the command manually to see what the actual error message is that you're getting. Also, can you access the ReportServer Web Services page (http://myserver/reportserver/reportservice.asmx - where myserver is the name of the server where Reporting Services is installed, or localhost for a single-server installation)?

It also looks like the default paths for the SharePoint, ReportServer, and ReportManager web apps are pretty much hardcoded into the VSTS installation, so if you're in single-server installation mode, http://localhost MUST be a SharePoint site, http://localhost/reports MUST be the ReportManager, and http://localhost/reportserver MUST be the path to the ReportServer. If you're using the dual-server installation, http://localhost must still be a SharePoint site, and http://remote-hostname/reports must still be the path to the ReportManager and http://remote-hostname/reportserver must still be the path to the ReportServer. I don't know for sure if the Default Website id (1) is hardcoded into the installation scripts as well, but it's probably safer to only use that just in case.

Hopefully the final release will offer a little bit more flexibility on the installation paths, like if you want to tie VSTS into an existing SharePoint installation.

jcorra at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Setup...

Visual Studio Team System

Site Classified