Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error connecting to existing server Workspace
See original GitHub issueEvery time I open any solution in Rider, and then try to get latest version, this error occurs:
com.microsoft.alm.plugin.external.exceptions.ToolAuthenticationException: KEY_TF_AUTH_FAIL at com.microsoft.alm.plugin.external.commands.FindWorkspaceCommand.throwIfError(FindWorkspaceCommand.java:133) at com.microsoft.alm.plugin.external.commands.FindWorkspaceCommand.parseOutput(FindWorkspaceCommand.java:91) at com.microsoft.alm.plugin.external.commands.FindWorkspaceCommand.parseOutput(FindWorkspaceCommand.java:26) at com.microsoft.alm.plugin.external.commands.Command$1.completed(Command.java:178) at com.microsoft.alm.plugin.external.ToolRunner$ListenerProxy.completed(ToolRunner.java:295) at com.microsoft.alm.plugin.external.ToolRunner$ProcessWaiter.run(ToolRunner.java:333)
Workspace I’m working in was created in Visual Studio.
I tried to update credentials here:
but nothing has changed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’re looking into it, see #325 for the current progress.
@DdarkSideE,
Then this is another issue. Please check you’re using the latest version of the plugin, and then open a new ticket, and attach IDE logs. Also, some details on your TFVC server would help.