how to fix Error TF30063: You are not authorized to access VS2017

Question

I changed my password for my TFS. But when I try to reconnect I receive the TF30063 unauthorized error.

There are many issues like this and I tried everything I coul

Answer 1

I will be facing this issue every six times a year. Because domain account password gets expired every 2 months 0 days or 8 weeks 5 days or 61 calendar days interval due to business security policy.

Follow these steps to change/set Password of TFS from IDE

1. Delete TeamExplorer.config from %AppData%\Microsoft\VisualStudio\15.0_xxxxxxxx\Team Explorer. (So after establishing a successful connection, it'll try to recreate again with the same data)
2. Add or change the TFS account Credential from Windows Credential Manager.
   So it won't prompt to enter a password again whenever when a connecting is established from IDE to TFS
3. If the above doesn't work close the Visual Studio IDE.
   Delete all the files inside %LocalAppData%\.IdentityService and %LocalAppData%\Microsoft\Team Foundation\7.0\Cache and
   on elevated prompt execute runas /netonly /user:<user domain account> devenv.exe navigating from "C:\Program Files (x86)\Microsoft Visual Studio\2017\<Professional>\Common7\IDE\"

Answer 2

Based on developer community there is a timing issue during visual studio start up that can cause the Source Control Explorer window to grab and then hang on to an invalid version of the connection to your team project. Details visit developer community.

https://developercommunity.visualstudio.com/content/problem/93366/tf30063-you-are-not-authorized-to-access-visualstu.html

Following work around steps help me to resolve the issue

1. Close all visual studio 2017

2. Start Visual studio 2017

3. If you see source control explorer at start up, then close source control explorer and Team explore and close visual studio 2017

4. Open visual studio 2017, ensure no source control explorer opened at start up

5. Go to View menu and click on team explorer

6. Then connect to TFS server.

Answer 3

It should be a Visual Studio 2017 credential cached token issue. You could try below ways to clear cache:

1. Close all Visual Studio instances.

2. Delete %LOCALAPPDATA%.IdentityService.

There are some identity related caching going on in there, deleting the folder will force the identity system to rebuild its cache.

• Also Clear TFS related caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache

• 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 password, then Team Explorer > Manage Connections

If the issue still exists, also take a look at this blog for more ways.

Answer 4

I had this same problem, and the solution I finally found was when VS asked if this was a "Work or school account" or a "Personal account" I chose "Personal account", and that fixed it even though it is a work account. This used to work fine, but it seems with some recent updates it causes an issue if you select "Work or school account"

Answer 5

I've gotten the above error (TF30063: You are not...) numerous times and the following three resolutions worked for me at different times:

1. Simplest: I've seen "Source Control Explorer" referenced numerous times, but I never leave that open. I resolved the above error by closing Team Explorer and reopening. I then loaded my solution, and then reopened Team Explorer. It opened without issues and I could contact the server (ie, I ran a code comparison in the Solution Explorer on a file I'd edited) -VS Pro 2017 v 15.8.0

2. Middle complexity: I was able to reconnect with the following steps: -Open Team Explorer (View menu => Team Explorer) -Click "Manage Connections" which is the plug shaped button at top -Click the text "Manage Connections" which is actually a drop down menu -Select "Connect to a Project" This brings up a new window that shows hosted repositories for your account. After several seconds the window displayed the desired projects. I just had to click the desired one and click the "Connect" button at the bottom. Once I did this, I was able to access all TFS features (ie I checked in some work) -VS Enterprise 2017 v15.9.3

3. Last resort: I loaded VS2017 Community onto another machine and logged in on that machine using my regular login. I'm not sure why, but as soon as I logged in on this new installation my other two computers had no problem connecting. No additional steps were needed, though I may have restarted VS on those machines.

Answer 6

I also had this problem with VS2017, version 15.9.4.

Common fixes are detailed here and here. And the majority of pages talking about this problem reference those solutions or sub-sets in some combination or another. (And often to fix login bugs introduced in one of the 15.5.* versions of VS2017)

None of those solutions worked for me either and after researching for 2 days, I found a couple of fringe-reasons why VS 2017 will not refresh/store credentials.

The 2 main "fringe" problems/fixes I've found are:

1. Connecting through certain proxy setups

2. Cryptography store not allowing for local storage, see also here

For myself it was the second problem, a good indicator of the issue is a log entry in %TEMP%\servicehub\logs with the error: "The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation."

It might also be a Windows 7/8.1 known issue carried over to Windows 10 upgraded machines. The problem only happened on a machine that joined the domain after doing the Windows 10 upgrade.

The fix is to add the following registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb]
"ProtectionPolicy"=dword:00000001

Setting that immediately fixed the issue with VS2017 connecting to the Microsoft Account. (And some other applications that would not persist credentials between launches)