Using Version control wizard to setup Team Foundation Server 2010 gave the error
Microsoft.TeamFoundation.VersionControl.Client.MappingConflictException
The path <workspace path> is already mapped in workspace <workspace>.
Stack Trace:
at Microsoft.TeamFoundation.VersionControl.Client.InternalCache.CheckForMappingConflicts(WorkspaceInfo workspace)
at Microsoft.TeamFoundation.VersionControl.Client.InternalCache.CheckForMappingConflicts(Workspace workspace)
at Microsoft.TeamFoundation.VersionControl.Client.Client.UpdateWorkspace(Workspace workspace, String newName, String newComment, WorkingFolder[] newMappings, String newComputer, Boolean fixMappingErrors)
at Microsoft.TeamFoundation.VersionControl.Client.Client.InternalSetWorkingFolder(Workspace workspace, WorkingFolder workingFolder, Boolean isDelete)
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.CreateMapping(WorkingFolder mapping)
at Microsoft.TeamFoundation.VersionControl.Client.Workspace.Map(String serverPath, String localPath)
at Quest.VersionControl.TFS.TFSProvider.SetVCFolderWorkingFolder(String folder, String workingPath, IProviderSetting settings)
at Quest.Toad.VersionControl.RepositoryManager.SelectWorkingFolder(String workingFolder, String folder)
at Quest.Toad.VersionControl.SetupWizard.SetupWizardForm.beWorkingFolder_ButtonClick(Object sender, ButtonPressedEventArgs e)
at DevExpress.XtraEditors.Repository.RepositoryItemButtonEdit.RaiseButtonClick(ButtonPressedEventArgs e)
at DevExpress.XtraEditors.ButtonEdit.OnClickButton(EditorButtonObjectInfoArgs buttonInfo)
at DevExpress.XtraEditors.ButtonEdit.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m)
at D
You cannot create a new workspace name and map it to a local work folder path that is already being used to a an existing workspace. See screen shot SOL94655_Fig_1.jpg.
RESOLUTION 1: Choose to use a workspace that already exist and is already mapped to the desired local work folder.
RESOLUTION 2: Un-map the desired local work folder from the existing workspace and map it to the new workspace.
RESOLUTION 3: Map the new workspace to a new local work folder.
