Our TFS was crashed, and we setup a new TFS with the same name, but with another defaultcollection name.
After setting up the new tfs, i want to connect using the same mapping. Our workspaces are not local, but server side.
The strangest thing is that i keep getting the error:
The path d:\teamfs is already mapped in workspace [myname] [http://teamfs:8080/tfs/defaultcollection].
But this defaultcollection does not exist anymore, the new one is called 'dotnet'.
Locally there is no workspace with this name.
Using the tf.exe also does nothing:
tf.exe workspace /owner:*
does reply:
TF400324: Team Foundation services are not available from server teamfs\DefaultC
ollection.
Technical information (for administrator):
Page not found.
How to get rid of this workspace from my local machine? Because the teamfs\DefaultCollection does not exist.
Related
I have folders within both Azures VSTS (a TFVC repository) and TFS that I needed to permanently delete. On TFS this was quite easily done using the tf destroy $/<MyProject>/<Folder_To_Delete> command in a command window on the server on which the TFS is running. The web page in learn.microsoft.com that describes the "tf destroy" command (Https:// learn.microsoft.com/en-us/vsts/tfvc/destroy-command-team-foundation-version-control) shows that this command is also available for VSTS however I have been unable to get the command to work within a Developer Command Prompt window running on my local box.
tf destroy $/<MyProject>/<Folder_To_Delete> /collection:https://<MyTeamService>.visualstudio.com/<MyProject> /login:<userid>,<password>
The error I receive back is
TF31002: Unable to connect to this Team Foundation Server:
Team Foundation Server Url:
Possible reasons for failure include:
- The name, port number, or protocol for the Team Foundation Server is incorrect.
- The Team Foundation Server is offline.
- The password has expired or is incorrect.
Technical information (for administrator):
The remote server returned an error: (404) Not Found.
However if I put the URL into a browser my VSTS instance shows up. So the 404 looks to me like azure is blocking outside efforts to permanently delete on VSTS. I have logged onto the Azure portal expecting to find something like the Advanced tools option you would find on Web App Services, But the Team Services / Team Projects has nothing like this. Can someone explain to me how to properly execute the "tf destroy" command on Azure Team Services? Or does Azures VSTS just lack the support to permanently delete individual folders and files?
The tf destroy command requires a collection URL. In VSTS, there is no concept of a collection, only team projects. All team projects are created under the Default Collection.
To use the tf destroy command with VSTS, your collection URL must be in the following format:
https://accountname.visualstudio.com/DefaultCollection
By putting a collection URL of https://accountname.visualstudio.com/Project Name, the command was looking for a collection called Project Name in the VSTS account, which does not exist.
This command works:
Open a Developer Command Prompt in administrator mode and issue the following command and supply your credentials.
tf destroy $/Project Name/Folder To Delete /collection:https://accountname.visualstudio.com/DefaultCollection
To Permanently destroy an item/folder in VSTS is also using Destroy Command (Team Foundation Version Control)
tf destroy [/keephistory] <itemspec1>[;<versionspec>][<itemspec2>...<itemspecN>]
[/stopat:<versionspec>] [/preview] [/startcleanup] [/noprompt] [/silent] [/login:username,[password]] [/collection:TeamProjectCollectionUrl]]
/collection which specifies the team project collection. However, in VSTS you only have one collection. There is no collection name like TFS in the url. And multiple collections under user voice:
Let us create multiple collections on Visual Studio Team Services
https://developercommunity.visualstudio.com/idea/365419/let-us-create-multiple-collections-on-visual-studi.html
So, when you specify /collection for VSTS in tf command line, you just need to enter https://xxx.visualstudio.com
Also pay attention to the /login:<userid>,<password>, you are using the wrong format, it should be /login:userid,[password], add a /preview for test first(When tf destroy runs in the preview mode, the files are not actually destroyed.)
Finally the result will be
When you remove the /preview and perform the really destroy, you will also get a prompt info:
Do you want to destroy $/Scrum/NugetTest/Capture1025.PNG and all of
its children? (Yes/No/All)
Select Yes to delete folder and files in it, All with all of its children.
https://<MyTeamService>.visualstudio.com/<MyProject> is the wrong URL. It should just be https://<MyTeamService>.visualstudio.com/.
The parameter is asking for a project collection, not a team project within the collection.
Reading this doc I got an impression that I should be able to use git-tfs to get the contents of a TFS repo in order to clone some branches: https://github.com/git-tfs/git-tfs/blob/master/doc/usecases/manage_tfs_branches.md
Tried these commands:
C:\Workspace.Git\Corp>git tfs list-remote-branches https:/scm.domain.com:8443/tfs
Given tfs name is not correct URI and not found as a registered TFS instance
C:\Workspace.Git\Corp>git tfs list-remote-branches https:/scm.domain.com:8443/tfs/DefaultCollection
Given tfs name is not correct URI and not found as a registered TFS instance
C:\Workspace.Git\Corp>git tfs list-remote-branches scm.domain.com
Given tfs name is not correct URI and not found as a registered TFS instance
where https:/scm.domain.com:8443/tfs is the server address which I use in Visual Studio 2012 to connect to TFS. It has DefaultCollection with several projects.
What is wrong with the server name I am supplying?
You are using the wrong url, lack of / and the collection name. Try this:
git tfs list-remote-branches https://scm.domain.com:8443/tfs/DefaultCollection
Will get the info like below screenshot
We are using TFS2010 (for source control only), and until recently everyone was using VS2010. Our developers just installed VS2012.
Pulling down code works fine in Visual Studio. When you go to "Pending Changes" in Team Explorer, we are seeing TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have been added to Team Foundation Server., twice, at the top. We can still check-in code from VS - seems this error is ignored.
However, we are unable to shelve changes - when you attempt to shelve, the same error comes up in a popup, and the shelveset is not saved.
We can shelve using the command prompt (tf shelve), and can still shelve using VS2010, so it doesn't seem to be a permission issue. Also, the TFS administrator is not seeing the error message, and can shelve from VS2012 with no error.
Any thoughts as to what could be causing VS to error out here? We've tried clearing out the TFS cache, creating a new workspace, and gone over every option we could find in Visual Studio.
I had the same issue. Tried many different stuff from web sites and non of them helped. Finally find the solution for this. Follow these to make it work:
1) Create temporary AD User
2) You will need to transfer all old user configuration into a new temporary account. If you are OK with using the temporary account you may just keep it and get rid of old account. Go into the machine that TFS is installed and Run this command: TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:oldAccount /toaccount:temporaryAccount
(TFSConfig is in C:\Program Files\Microsoft Team Foundation Server XX.0\Tools\)
3) If you don't want to use temporary account you will need to convert from temp account to your old account. To do that run the same command wit changing the user names:
TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:temporaryAccount /toaccount:oldAccount
That's all you need to do.
Here is the setup:
We had a one server TFS solution previously. We split each part out so the DB, TFS and the Build Service each have their own server now.
I manually restored the TFS DBs to the new server. I installed the app tier on the app server and the Build Service on another server. As usual, everything works fine on my computer. However, about half of my team has an issue where the team explorer shows just one project. Most of the team doesn't even have permissions to view this project yet it is all they see.
I had each of them run the tf workspaces ... command to sync up their workspaces to the new server location. I verified permissions. I had one of the affected delete his workspace and create a new one. Same issue. Team explorer only shows one project... that he doesn't even have permission to view. Source control explorer seems to operate fine.
Also, this only seems to affect one project collection. I have not heard anyone on another project collection having this issue.
Suggestions?
Hmm, I'm wondering if you need to do a ChangeServerID.
Up until yesterday, my connection to Team Foundation Service was working perfectly.
A separate requirement caused me yesterday to rename my computer. After that, there were some errors about the workspace which I was able to fix with the TF command, but I can't find anything about this new error, which arose after I renamed the workspace:
Please note that the blacked-out email addresses are all three identical.
I have no idea how to "specify one of the following workspace specs" from a MessageBox! Any ideas?
TFS for years has been among the worst user experiences I've ever seen.
For me it helped to just sign out from TFS via the "Configure Team Projects" window, and then log in again.
Connect to TFS DB and refer DefaultCollection db.
[dbo].[tbl_Workspace] this table is used to store workspace info
[tbl_WorkspaceMapping] this table is used to store mapping created above.
[dbo].[tbl_WorkingFolder] this table is used to store working folder mapping.
Exit your tfs client and perform below steps.
delete your workspaces causing issue from table [dbo].[tbl_Workspace] and [tbl_WorkspaceMapping] and start accessing your tfs client by configuring new workspace.
I had to guess at a "tf" command line argument set, but, I found that the workspace carried the same name as the computer, after renaming both. So I did this to myself.
After using "tf" to change the workspace name from "WIN8DEV" to "WIN8DEVWORKSPACE" this particular problem vanished.