404 response when trying to connect to team server

• Ben Is Lost

  Thank you again Dennis.

  I didn't find ant backup of the original web.config so I just renamed the file web_2006_4_12_12_43.config to web.config. It seems to solve the problem - at least at the first glance. I'm now able to start the process of creating a new team project. However, somewhere towards the end of the process I get an error message... Below is the exception log and I hope you'll be able to save me again:

  4/21/2006 12:32:08 PM | Module: Engine | Thread: 11 | Running Task "" from Group ""
  4/21/2006 12:32:08 PM | Module: Engine | Task "" from Group "" completed with success | Completion time: 0 seconds
  4/21/2006 12:32:08 PM | Module: Engine | Thread: 6 | Running Task "SharePointPortal" from Group "Portal"
  ---begin Exception entry---
  Time: 4/21/2006 12:32:09 PM
  Module: Engine
  Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
  Exception Type: Microsoft.TeamFoundation.Client.PcwException
  Exception Message: Unable to connect to the Windows SharePoint Services at coderepository
  Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
  at coderepository. The reason for the failed connection cannot be determined at this time.
  Because the connection failed, the wizard was not able to complete creating
  the Windows SharePoint Services site.
  Stack Trace:
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
  at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
  at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
  -- Inner Exception --
  Exception Type: Microsoft.TeamFoundation.Client.PcwException
  Exception Message: Unable to connect to the Windows SharePoint Services at coderepository
  Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
  at coderepository. The reason for the failed connection cannot be determined at this time.
  Because the connection failed, the wizard was not able to complete creating
  the Windows SharePoint Services site.
  Stack Trace:
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.ValidateSite(ProjectCreationContext context, XmlNode site)
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Validate(ProjectCreationContext context, XmlNode taskXml)
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
  -- end Inner Exception --
  -- Inner Exception --
  Exception Type: System.Net.WebException
  Exception Message: Unable to connect to the remote server
  WebException: Status : ConnectFailure
  Stack Trace:
  at System.Net.HttpWebRequest.GetRequestStream()
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at Microsoft.TeamFoundation.Proxy.Portal.Admin.GetLanguages()
  at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
  -- end Inner Exception --
  -- Inner Exception --
  Exception Type: System.Net.Sockets.SocketException
  Exception Message: No connection could be made because the target machine actively refused it
  Stack Trace:
  at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
  at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
  at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
  -- end Inner Exception --
  --- end Exception entry ---

  4/21/2006 12:32:09 PM | Module: Engine | Thread: 6 | TF30202: Task "" from Group "" will not be run because a prior task failed.
  4/21/2006 12:32:09 PM | Module: Engine | Thread: 6 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed.
  4/21/2006 12:32:09 PM | Module: Engine | Thread: 6 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed.
  4/21/2006 12:32:09 PM | Module: Engine | Thread: 6 | TF30202: Task "" from Group "" will not be run because a prior task failed.
  4/21/2006 12:32:09 PM | Module: Engine | Thread: 7 | Attempting to delete MSF folder "C:\Documents and Settings\DKT\Local Settings\Temp\TPW_tmp2E.tmp"
  4/21/2006 12:32:10 PM | Module: Engine | Thread: 7 | The temporary folder C:\Documents and Settings\DKT\Local Settings\Temp\TPW_tmp2E.tmp used to store the process template was removed.
  ---begin Exception entry---
  Time: 4/21/2006 12:32:11 PM
  Module: Wizard
  Event Description: TF30002: The New Team Project Wizard encountered an error deleting the project test
  Exception Type: System.Net.WebException
  Exception Message: Unable to connect to the remote server
  WebException: Status : ConnectFailure
  Stack Trace:
  at System.Net.HttpWebRequest.GetRequestStream()
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at Microsoft.TeamFoundation.Proxy.Portal.Admin.GetLanguages()
  at Microsoft.TeamFoundation.Client.TeamProjectDeleter.Delete()
  at Microsoft.VisualStudio.TeamFoundation.PortfolioProjectForm.TryDeleteProject()
  -- Inner Exception --
  Exception Type: System.Net.Sockets.SocketException
  Exception Message: No connection could be made because the target machine actively refused it
  Stack Trace:
  at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
  at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
  at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
  -- end Inner Exception --
  --- end Exception entry ---

  Thank you,

  Ken

  
  

• Agalab

  Thank you Dennis. It worked! Thank you for your support through the whole process!

  Ken

  
  

• Ranj

  Hi Ken,

  This looks like your configuration is no longer valid. At the point where this is occuring we are attempting to access the WSS server for the very first time. In this case, we are trying to access the 'Admin' web service, which is on its own port (http://<server>:<adminport>/_vti_adm/Admin.asmx. The problem is that <adminport> can be re-generated by WSS, so it isn't constant (this usually happens during re-install or the installation of patches). However, when TFS is initially provisioned it stores this admin port in the database. If they get out of sync (which may to be the case here), then you will end up with the problem that you are seeing.

  You should go to your Application Tier, start the 'SharePoint Central Admin' site and look at the URL. It should contain the correct port number. Also, verify that you can get to SharePoint Central Administration for a separate client machine, just to verify that there isn't a firewall problem.

  Now open SQL Server Management Studio and connect to your Data Tier. Expand the tfsIntegration database and open the dbo.tbl_service_interface table. You will see an entry for WssAdminService in the table. This will have a url associated with it, make sure that the port number in this url is the same as the SharePoint Central Admin port number. If it isn't, change the port number in the database so it matches. Also, copy/paste the url into IE and verify that you can reach the web service.

  Let me know what you find...

  -Dennis

  
  

• Meerc

  This is likely caused by the accidental extension of the TFS web site to WSS. WSS will rename the existing web.config file and replace it with its own version. The web.config file needs to be restored to its original state. Take a look in C:\Program Files\Microsoft Team Foundation 2005\Web Services and see if there is a backup of the original web.config file. If so, rename the existing web.config file (generated by WSS) and replace it with the backed up version.

  -Dennis

  
  

• Tobias Zimmergren

  Hi Dennis,

  Thank you again! :) This worked. I had to change the SharePoint port to 17012 and so I'm passed this problem but encounter the next one (log is below). I tried to change the connection time out of the sharepoint centrat administration to 500 seconds but it didn't make a different.

  Thank you,

  Ken

  Exception log:

  4/21/2006 3:50:19 PM | Module: Engine | Thread: 10 | Running Task "Site" from Group "Reporting"
  4/21/2006 3:50:19 PM | Module: Rosetta | Thread: 10 | Creating site: test 4
  ---begin Exception entry---
  Time: 4/21/2006 3:50:57 PM
  Module: Engine
  Event Description: TF30162: Task "Site" from Group "Reporting" failed
  Exception Type: Microsoft.TeamFoundation.Client.PcwException
  Exception Message: Unable to connect to the specified SQL Reporting Services at coderepository.
  Exception Details:
  The Project Creation Wizard was not able to connect to the SQL Reporting Services at coderepository.
  The reason for the failed connection cannot be determined at this time.
  Because the connection failed, the wizard was not able to complete
  creating the SQL Reporting Services site.
  Stack Trace:
  at Microsoft.VisualStudio.TeamFoundation.RosettaReportUploader.Execute(ProjectCreationContext context, XmlNode taskXml)
  at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
  at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
  -- Inner Exception --
  Exception Type: System.Net.WebException
  Exception Message: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
  WebException: Status : KeepAliveFailure
  Stack Trace:
  at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
  at Microsoft.TeamFoundation.Client.TeamFoundationSoapProxy.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at Microsoft.TeamFoundation.Proxy.Reporting.ReportingService.CreateFolder(String Folder, String Parent, Property[] Properties)
  at Microsoft.VisualStudio.TeamFoundation.RosettaReportUploader.HandleCreateSite(ProjectCreationContext context, XmlNode node)
  at Microsoft.VisualStudio.TeamFoundation.RosettaReportUploader.Execute(ProjectCreationContext context, XmlNode taskXml)
  -- end Inner Exception --
  -- Inner Exception --
  Exception Type: System.IO.IOException
  Exception Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
  Stack Trace:
  at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
  -- end Inner Exception --
  -- Inner Exception --
  Exception Type: System.Net.Sockets.SocketException
  Exception Message: An existing connection was forcibly closed by the remote host
  Stack Trace:
  at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
  at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
  -- end Inner Exception --
  --- end Exception entry ---

  
  

• Alino

  Hi Ken,

  What page do you get when you go to http://localhost:8080/default.aspx I didn't think we put anything there, I would expect an error. If you are getting a SharePoint page then you probably extended the TFS virtual server which would certainly cause this problem.

  -Dennis

  
  

• vinaymishra

  Hi Denis,

  Thank you for clearing that one. I truly appricaite it. I followed your advise and remove the extension from the TFS. Now when I try to connect I get the following error:

  Server Error in '/services' Application.

• JHG JetLane

  Hi Ken,

  The error you are seeing is from SharePoint, it doesn't seem to be configured correctly or a site that used to exist was deleted. Where are you getting this error

  In SharePoint you need to make sure that only the 'default web site' is extended, not the TFS web site. When you 'extend' a site what you are doing is telling WSS to manage the contents of that site. WSS puts all of site data in a database on the selected SQL server (the 'content' database). You can extend multiple sites with WSS, each with their own content database(s). WSS also has a 'config' database, one per server farm, which stores server farm-wide information (site templates, web parts, etc). The TFS site contains all of the web services and cannot be extended since WSS will get in the way at that point (the services won't exist, which is why you were getting the 404).

  -Dennis

  
  

• wkimes369852147

  Hi Ken,

  At least we are making some progress! We are now past the point of creation the WSS site and uploading the files (etc). Now we are trying to create a new reporting site in SQL Server Reporting Services. When this problem occurs we are trying to access the SQL Server Reporting Service web service at the following URL:

  http://<servername>/ReportServer/ReportService.asmx

  Can you browse to this url Can you get to http://<servername>/reports and http://<servername>/reportserver If not, your report server on the Application Tier may not be running. You may need to manually start the 'SQL Server Reporting Services' service.

  There is one other thing that needs to be verified. Since the 'reports' web service runs from the same url as the SharePoint sites you need to exclude the 'reports' and 'reportserver' paths from the paths that SharePoint manages. Otherwise, SharePoint thinks it is a page that it should manage and it doesn't exist in the database. To do this you will need to do the following:

  1. Start a command prompt

  2. cd /d %programfiles%\common files\microsoft shared\web server extensions\60\bin

  3. stsadm -o addpath -url http://<servername>/reports -type exclusion

  4. stsadm -o addpath -url http://<servername>/reportserver -type exclusion

  -Dennis

  
  

• SDeen

  Thank you Dennis and sorry for my late response. I did extend the TFS virtual server as I had another problem. I red in somewhere in this newsgroup that extending the server would solve it.

  Anyway, I delted the extension by using the sharepoint "delete site collection" so now when I browse to http://localhost:8080/default.aspx I get 404. Now when I try in Visual Studio to connect to a team server of to add a team project I get the error:

  "The web site that is referenced here is not in the configuration database". Any ideas where this is coming from

  Thanks,

  Ken

  
  
• 404 response when trying to connect to team server