-
Notifications
You must be signed in to change notification settings - Fork 449
Extension thinks TFVC workspace is a Server workspace, when it's clearly Local #325
Comments
same problem, posted a issue 2 weeks ago on here, no response at all |
I'm having the same issue and have verified in VS 2017 that the Workspace is a "Local Folder". I will follow up if I find anything. I'd also like to point out that this error shows up for me when I open a folder that is not in source control. Here's the log:
|
I have exactly the same issue... |
I have the same issue too. Tried all the tricks. Updated VS. Still thinks it’s a server workspace. Does anyone have any ideas ? |
Have the same issue. Looks like something got updated either in Code of in TFVC which broke this. Need this to be fixed soon :( |
Same thing here. It was working a few days ago. |
I tried something and It Worked! Can't say for sure if this is a good solution or THE solution. Still don't understand what messed it up in the first place but here's what I did. Went to Visual Studio and connected to Team server then opened workspaces and as I knew it was Local. But then I changed it to Server and then again changed it back to Local. Only TFS knows what it did but now Code is able to connect to team services properly. Hope this works for others! |
Same here. Just chipping in to show the urgency. Tried everything I could find online |
@prasannawagh I tried this, it did not work for me. |
I was having the same problem, and now it works! I think is what @prasannawagh said, but with a important step to follow. I have Visual Studio 2015 and Visual Studio Team Explorer 2017 installed.
Let me know if this works for you. |
@mqueirozcorreia your method is not working for me :/ |
How was the log after the process? Does It make any difference? |
the log? |
Yes |
any update on this, I'm having the same issue. |
The main point is to use VS Team Explorer 2017. The generate the log, please see the Logging info at readme.md |
I started receiving this error after I updated to the latest version of VS Code today. I also changed my network password yesterday which is stored in ADFS so I don't know if maybe that would have anything to do with it or not. I tried following @mqueirozcorreia directions, but without success. I also tried signing out and signing back in, as well as changing my Microsoft Password to match my network password, but without any luck. The error I am receiving in my log is:
This doesn't seem to make any sense since just yesterday it was working and I am still able to access the repository from Visual Studio 2017 Team Explorer & the web interface. |
Have you tried to create a new local repository? Do you have VS 2015? Don't use it! |
Nothing of the above works for me. Here's my log: 2017-11-30T15:34:36.228Z - error: [11008] Could not find a workspace with mappings (e.g., not a TFVC repository, wrong version of TF is being used). Unable to determine the source control server. 2017-11-30T15:38:22.303Z - error: [12560] Could not find a workspace with mappings (e.g., not a TFVC repository, wrong version of TF is being used). Unable to determine the source control server. |
I just installed this today and have run into the same issue. Attached is my logfile and screen shot from VS 2017 |
Had a dabble in the source code. See line 77 of commandhelper.ts I'll continue to investigate and re-post here if I find anything..... |
process as described by @mqueirozcorreia worked for me. VS2017 did some scrubbing when switching from Local to Server and then resets workspace when setting back to Local. After this the error goes away and so far so goo. |
I found a solution that might help other as well. Obviously, I referenced an older tf.exe version in the .vscode/settings.json file. I just changed |
@markusmauch that is step is important too. I have update my answer adding this as step 8 |
I had same issue. No above suggestion works for me under VS 2017 Community. I had to install VS 2015 Community, create new local workspace and point tf.exe from there and now it works. |
For me this issue stemmed from improperly checking out the repository. We had just moved our stuff to Azure so I did the first repo incorrectly. Where I went wrong: I cloned the repo manually by going to the project page and copying the repo url and checking out with git. How I found a solution: I checked out the project using the Team Services panel in Visual Studio. Once I did that, everything worked automatically once I opened the newly cloned project in Code. I was also able to get the original repo working by trying different things in this thread, but I'm not sure what finally fixed it. One key for me getting it to work manually was to turn debug on. I also have the tfvc.location flag set. {
"team.logging.level": "debug",
"tfvc.location": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\Common7\\IDE\\CommonExtensions\\Microsoft\\TeamFoundation\\Team Explorer\\TF.exe"
} |
For anyone else with a similar setup to mine, I have two projects (one is the vs code project) sharing the same workspace and was getting this error. Additionally to the |
After much struggling myself, I finally made it to work.
Finally it works now. |
That seems to have worked for me NanFengCheong! Thanks for the tip. |
Thank you @NanFengCheong |
Goes someway to mitigating microsoft#325
Thanks @NanFengCheong So if I've understood it right, Visual Studio Team Services extension uses the Personal Access Token, but tf.exe still needs the username/password. If not, then misleading errors are produced. The reason it probably didn't work for me was that I have different Microsoft accounts for my local TFS and remote VSTS, so it's likely tf.exe was using the wrong credentials, although this is just speculation. |
@NanFengCheong you are the man. Just spent 3 hours trying to fix this problem and you've solved it |
@NanFengCheong s solution worked for me with a slight difference. When I ran the command So I ran tf workspaces /collection:https://myworkspacename.visualstudio.com. Then it prompted me to login and then it all worked. Thanks @NanFengCheong NOTE: I did have to restart vscode |
Thanks @billyjacobs2014 your solution worked for me. |
Working fine... Thanks |
I have to do this every so often, is there a more permanent solution? |
I ditched VS Code for Visual Studio Pro... I got tired of the fooling around with the tools instead of writing the bloody code! Who has time for this!?!?! |
I code using VS Code and do all my checkins using Visual Studio Pro. Checking in, especially to a task or PBI, is super annoying with VS Code but super easy with VS Pro. |
agreed, VS Code is too slow. |
I tried the above solutions and none worked, VSCode still thinks my workspace is set on server. Whenever I try to run the tf workspace command in the root folder of the workspace I don't get a login prompt just the workspace window to make modifications to the workspace and that's it, even making changes from there doesn't fix it. |
These are my notes on the steps I use to resolve this when it breaks every so often. When VSTS is not working for source control login is likely expired. |
Nope I still don't get any log in prompt after typing "tf vc workspace" I get taken directly to the window to edit the workspaces I have and that's it, editing from there does nothing as well, the error persists. |
@ParadiseCircus You can find help for login credentials here like this |
Viewing the workspace through Visual Studio shows it as a local, workspace, like the README's instructions. However, after authenticating in VSCode, I get an error popup "(team) It appears you are using a Server workspace. Currently, TFVC support is limited to Local workspaces."
The workspace is to our VSTS account.
How does the extension determine the workspace type?
Update after some quick digging - it looks like the extension views "Unauthorized" errors as indicators of a Server workspace. I've tried using both PAT and browser auth flows, neither of those resolved the issue.
The text was updated successfully, but these errors were encountered: