I installed TFS 2008 Workgroup Edition a while back, and everything was running fine.
Recently I tried opening TFS to a couple of friends so that we can collaborate on a project. The Source Control portion is working correctly, but the Documents and Reports folders are not available (they have red crosses on them).
When I looked at the properties, I noticed that the URLs were using my internal machine name, not the external address (e.g. http://INTERNALNAME/Sites/MyProject instead of http://www.EXTERNAL-NAME.com/Sites/MyProject).
My preference would be to somehow use relative paths, so that if I ever decide to stop exposing TFS to the outside, I don't have to do anything.
I realize this may not be possible because TFS cannot make the assumption that Reporting Services and Share Point are on the same machine.... so is there at least an easy way to assign a new server name?
Yeah, relative paths cannot be used due to the way that TFS works - it sends back the full URL's to the Sharepoint and Reporting Services servers to the client machine.
To update the URL's that are used for sharepoint and reporting services to match your fully qualified domain name you want to use TFSAdminUtil. Remote desktop to the TFS server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.
At the command prompt, type the following command (all on one line):
TfsAdminUtil ConfigureConnections /SharepointUri:BaseSiteURL
/SharepointSitesUri:SharePointSite
/SharepointAdminUri:SharePointAdministration
/ReportsUri:ReportsUri
/ReportServerUri:ReportServer
Replacing the following strings
SharePointSite is the new URI for the SharePoint Products and Technologies site collection.
SharePointAdministration is the new URI for the SharePoint Central Administration Web site (used for new team project creation)
ReportsUri is the new URI for SQL Server Reporting Services.
ReportServer is the new URI for the ReportsService.asmx Web service.
BTW - If you have installed SP1 for Visual Studio Team System 2008 Team Foundation Server, the ReportServer parameter will not function correctly and you have to stick /ReportService.asmx on the end. For more information about this problem and its resolution, see this KB: Team Foundation Server 2008 SP1 TfsAdminUtil.exe 'ConfigureConnections' fails to properly set ReportServerUri.
For example, the following command would work with TFS 2008 SP1:
TfsAdminUtil ConfigureConnections /SharepointUri:http://tfs.external-name.com /SharepointSitesUri:http://tfs.external-name.com/Sites /SharepointAdminUri:http://tfs.external-name.com:17483 /ReportsUri:http://tfs.external-name.com/Reports /ReportServerUri:http://tfs.external-name.com/ReportServer/ReportService.asmx
One last thing to note is that if you are accessing your TFS server externally, then it is recommended that you do this using HTTPS to encrypt the TFS traffic. For more information on this configuration see the post on the MSDN site: Walkthrough: Setting up Team Foundation Server with Secure Sockets Layer (SSL) and an ISAPI Filter
Related
I tried out the TFS Service with a project of mine. After I experienced some problems (probably misuse) I used VSUnbindSourceControl.exe (see: http://vsunbindsourcecc.codeplex.com/) to detach the project (locally) from the TFS, but it looks as if on the server side, the project that was uploaded, is still bound to my computer.
See image:
and the error message in the output window:
Failed To Create Mapping
The working folder G:\Quant tool DotNet4 is already in use by the workspace USER-PC;myemail# somedomain dot com on computer USER-PC.
(I now use a different email address than the one above)
I've tried to delete the project from the server via the Source Control Explorer in VS, but the delete option is disabled. (also when I login with mldz at hotmail dot com.
I was also not able to delete the project or change it's settings via the TFS web interface.
Anyone experience with this problem and how to solve it with the new TFS in the cloud? i saw some similar problems with a normal TFS and some solutions could be done via the the team foundation administration tool, but that cannot be applied to the TFS in the cloud (AFAIK)
Some info about trying to install TFS integration tool
Hi,
I use VS2012 express and although I installed vs_teamexplorer.exe,
I'm not able to install Microsoft Team Foundation Server Integration Tool.
Already restarted the computer after installation and tried again. Doesn't work. Missing something?
regards,
Matthijs
You can use the same admin tools for tfs.visualstudio. See examples. At end of http://msdn.microsoft.com/en-us/magazine/jj130558.aspx article which show deletion of workspaces, for example.
I am working with Odata and TFS. I was able to get the OdataTFS file downloaded and working. I am trying to write a client console application that will access TFS so I can run queries againest it. I am trying to figure out this line
var tfsData = new TFSData.TFSData(new Uri("https://codeplexodata.cloudapp.net");
The way I usually access information on TFS is to into visual studio 2010, click connect to TFS Server, type in the server name and thats it. But here I am unsure how to do it. I haven't found any materials on how to connect to a server rather than to a codeplex. Where would I find the uri for this? Any help anything at all would be great, i have read the first 15 google searches on odata and still a little lost.
TFS does not have any OData services included in the installation.
You need to install the OData Service for Team Foundation Server on your local TFS server in order to use OData against your on-premises TFS.
I have a group of students connecting to Team Foundation Server. When they connect from school, when their computers are physically on the network, they can successfully access TFS and perform get operations, checkout, checkin, etc.
The same users go home, install VS 2010, connect to TFS, get the code, but the solution will be opened offline from TFS.
Why is this?
When the students are at home, do they access the server from a different name than they do at school? Often, users will use a short (not fully qualified) name to access a server internally. For example:
http://tfsserver:8080/
However, this will not work from outside of the network, the name will need to be fully-qualified. For example:
http://tfsserver.mycompany.com:8080/
The Visual Studio solution contains version control bindings that point to your Team Foundation Server. If the users cannot access the server by name in the bindings, the solution will be opened offline. The users should connect to Team Foundation Server and then select "Change Source Control" in the file menu. This will cause the solution file to point to the fully-qualified domain name of the Team Foundation Server which should allow access from within your internal network or from the outside world.
There seems to be a fault with my access to directories on Team Foundation Server.
See the image below.
I'm the only one with this problem. All of the other clients can connect to the server fine, so it must be my local copy of Team Foundation Server thats gone haywire.
Any ideas?
This is usually a permissions problem. Use the TFSAdmin Tool to check permissions on the SSRS and Sharepoint systems (which are separate from TFS itself, unfortunately). Check that the settings are working the way you intend by browsing directly to the Reporting website & the Team Project Portal from inside IE.
There are other possibilities, however.
Check the Application event log on the server to see if your attempts to connect generate any exceptions.
If you're using SQL Server 2008, make sure you have Team Explorer fully patched up to 2008 SP1. (you'll need to re-run SP1 if you installed Team Explorer afterward)
Make sure you're connecting to TFS using the same URI as other people. If you're using a fully-qualified domain and they aren't (or vice versa) you could be exposing a server configuration problem in TFS's Registration database. Details here: http://blogs.msdn.com/buckh/archive/2007/03/31/configuring-team-foundation-server-to-use-fully-qualified-domain-names.aspx Also, there is a known bug in the admin util: http://support.microsoft.com/default.aspx/kb/959126
Check, recheck, and re-recheck your proxy settings. Both software configuration (TFS inherits them from IE / Control Panel) and at the network level (whether you're on some LAN segment that gets proxied differently). Use an HTTP protocol analyzer on a good & bad machine to be certain.
I had the same issue after trying to connect to alternative address of our TFS server.
In my case it seemed that it just cached the previous TFS address although I changed it back to the original address.
What fixed it for me was to delete this folder:
C:\Users\<user>\AppData\Local\Microsoft\Team Foundation
We have TFS installed in a US server. We need to login into VPN to access the TFS server. TFS is configured to use with company's domain user account. However my system is part of the domain. Hence I couldn't access the TFS. I have Visual Studio Team System Developer edition. Can someone here help how to access TFS server installed with different domain?
Regards,
Krish
TFS uses the domain information of the current logged in Windows account, it's part of the TFS API.
If you're logging into the machine with an account which is on a different domain (Note: Local users are also on a different domain) you will not get single-sign-on.
As far as I'm aware there isn't a way around the authentication model which VSTS uses. You could write your own VSTS-style extensions using the existing VS API which say, uses a config file for the authentication credentials as the TFS API does support authentication through a manually-created user (we have an external application at work which authenticates against our TFS server and is used by employees of our many offices on different domains).
For codeplex you have to connect to TFS using 'SND\username_cp', maybe you can use 'DOMAINNAME\username' as well.