The Iron Yuppie
Thought[ful|less] coverage of news, politics, technology and anything else that catches my fancy.Thursday, December 01, 2005
Continuing Log of Errors I Find
Here's my story:
I just did an install of SQL Server 2005 and ran into a weird problem. Actually, I first started doing an install of Visual Studio Team Foundation Server Beta 3 (VSTF) and ran into a weirdo dialog box saying that the reporting server that couldn't be started. THANKFULLY, the dialog could be copied and restarted, and so I copied the text and tried to run it from the command line. So when I ran it, here's what I saw:
C:\>"d:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools\createds.exe" /setup /install "http://Localhost/ReportServer/ReportService.asmx" TfsReportDS "Data source=COMPUTERNAME;initial catalog=TFSWarehouse" "DOMAIN\SERVICEACCOUNT" "VERYLONGSTRING"
Unable to connect to the Yukon Reporting Server. Please check that the Yukon Reporting Web and NT services are running and you have sufficient privileges on the data tier: The request failed with HTTP status 404: Not Found.Data source creation failed.
Upon trying to open the Sql Configuration Manager and tried to connect to the Reporting Server, I got hit with this.
TITLE: Connect to Server
------------------------------
Cannot connect to Localhost.
------------------------------
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)
------------------------------
The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)
------------------------------
Turns out that I had previously done an install (SUS) and it turns out that it was installed on port 80. When SQL Server did the Reporting Server install, it did it in the default webserver which was also on port 80, and stopped. Changing the SUS port to 85 and starting up the default web server solved the problem.
No big insight here, just wanted to log it for the search engines.
D
I've forwarded this to our setup team and they're going to repro it internally and figure out what the best approach is. It'll probably be something like block the Team Foundation server install until that app is moved to another port (like you did), but I don't know for sure.
Thanks again!
<< Home
Archives
10/01/2003 - 11/01/2003 11/01/2003 - 12/01/2003 12/01/2003 - 01/01/2004 01/01/2004 - 02/01/2004 02/01/2004 - 03/01/2004 03/01/2004 - 04/01/2004 04/01/2004 - 05/01/2004 05/01/2004 - 06/01/2004 06/01/2004 - 07/01/2004 07/01/2004 - 08/01/2004 08/01/2004 - 09/01/2004 09/01/2004 - 10/01/2004 10/01/2004 - 11/01/2004 11/01/2004 - 12/01/2004 12/01/2004 - 01/01/2005 01/01/2005 - 02/01/2005 02/01/2005 - 03/01/2005 03/01/2005 - 04/01/2005 04/01/2005 - 05/01/2005 05/01/2005 - 06/01/2005 06/01/2005 - 07/01/2005 07/01/2005 - 08/01/2005 08/01/2005 - 09/01/2005 09/01/2005 - 10/01/2005 10/01/2005 - 11/01/2005 11/01/2005 - 12/01/2005 12/01/2005 - 01/01/2006 01/01/2006 - 02/01/2006 02/01/2006 - 03/01/2006 03/01/2006 - 04/01/2006 04/01/2006 - 05/01/2006 05/01/2006 - 06/01/2006 06/01/2006 - 07/01/2006 07/01/2006 - 08/01/2006 08/01/2006 - 09/01/2006 09/01/2006 - 10/01/2006 10/01/2006 - 11/01/2006 11/01/2006 - 12/01/2006 12/01/2006 - 01/01/2007 01/01/2007 - 02/01/2007 02/01/2007 - 03/01/2007 03/01/2007 - 04/01/2007 04/01/2007 - 05/01/2007 05/01/2007 - 06/01/2007 06/01/2007 - 07/01/2007 08/01/2007 - 09/01/2007 10/01/2007 - 11/01/2007 11/01/2007 - 12/01/2007 12/01/2007 - 01/01/2008 01/01/2008 - 02/01/2008 02/01/2008 - 03/01/2008 06/01/2008 - 07/01/2008 07/01/2008 - 08/01/2008 08/01/2008 - 09/01/2008 10/01/2008 - 11/01/2008
Subscribe to Posts [Atom]