CODEWITHSUNDEEP
tfsvisual-studio-2017
AndySousa
AndySousa

Reputation: 1122

Clear stored TFS credentials in Visual Studio 2017

I had to change my password for my account which is not the same account i log into my machine with. When connected to the local tfs server, I supplied my password to VS2017 and checked remember password. Now that the password has changed, I cannot connect.

I have tried to remove the tfs in credential manager and also deleted the .IdentityService. Neither have helped. Anyone know if they changed something with VS 2017 and they are cached or stored somewhere else?

Upvotes: 50

Views: 83751

Answers (9)

MarianoC
MarianoC

Reputation: 31

Other answers didn't work for me.

Goto File->Account Settings->All Accounts remove the account you want.

Upvotes: 0

mhy
mhy

Reputation: 1

In our case, we had to change the user account to log into TFS on the same machine.

None of above solutions did not work for us except changing the computer name.

Upvotes: 0

Anand
Anand

Reputation: 31

These Steps worked for the issue : The V2 feed returned an unexpected status code '403 Forbidden' for configured nuGet package through Artifactory

Remove the TFS related credentials from Credential Manager 1)In Credential Manager add the new updated Generic Credentials for the TFS account. 2)Generally, this would overwrite the cached credentials. Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService as you did.

Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache

Clear all the browser caches especially for the stored password

Restart Visual Studio > Team Explorer > Manage Connections to check if the Enter credential dialog popup. Just try this several times. Based on my test the dialog will popup the first time, but if you cancel it, then you have to restart VS to popup it again.

Upvotes: 1

A K
A K

Reputation: 71

Clear the config from the following path:

C:\users\<user>\AppData\Roaming\Microsoft\VisualStudio\15.0_????\Team Explorer\

Upvotes: 7

Abdurakhmon
Abdurakhmon

Reputation: 3070

In Windows search for Manage Your Network Passwords, from there you can delete and modify saved credentials

Upvotes: 0

Wizou
Wizou

Reputation: 1907

I had an issue where TFS kept connecting with the wrong credentials. The solution that worked for me was to run the following command line:

tf vc workspaces /login:MY_USERNAME /collection:http://TFS_SERVER_PATH

Upvotes: 1

Sapnandu
Sapnandu

Reputation: 642

I had face a typical problem with Visual Studio 2017. I was using VSTS. First time i had connected With one credential, later on i was trying to change credential. But it was not taking. Then after a long effort finally i found there have a folder.

C:\Users\ {your user name} \AppData\Local\GitCredentialManager

just delete all the file inside this folder and try. Hope it will work.

Upvotes: 0

Andy Li-MSFT
Andy Li-MSFT

Reputation: 30372

Please try below items to narrow down the issue:

  • Remove the TFS related credentials from Credential Manager

  • In Credential Manager add the new updated Generic Credentials for the TFS account. Generally, this would overwrite the cached credentials.

  • Close all Visual Studio instances, delete %LOCALAPPDATA%\.IdentityService as you did.

  • Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache

  • Clear all the browser caches especially for the stored password

  • Restart Visual Studio > Team Explorer > Manage Connections to check if the Enter credential dialog popup. Just try this several times. Based on my test the dialog will popup the first time, but if you cancel it, then you have to restart VS to popup it again.

  • Run Visual Studio as another user:

    cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE

    runas /netonly /user:<account> devenv.exe

    Enter the user possword, then Team Explorer > Manage Connections

Upvotes: 90

Simme Nilsson
Simme Nilsson

Reputation: 143

I tried to follow the steps listed in the other answer. But on first step I decided to try just editing the password in credentials manager. It worked for me.

So if anyone else is having the same problem you might want to try that first.

Upvotes: 12

Related Questions