Launching VS with Source Control Explorer open (TF30063: You are not authorized to access...) after upgrading to VS2017 15.3

We have updated the title to better describe the issue for which the fix was applied. Please see the following issues that are different, but result in the same error. Please vote on these issues and provide more information if you have any. If you are experiencing a problem that is not described by any of the issues below, please open a new ticket as that will allow us to collect all the necessary diagnostics.

Opening VS with Source Control Explorer open results in TF30063

Described by this issue and fixed in 15.3.4.

Microsoft Test Manager (MTM) cannot connect and results in TF30063

For connecting to TFS: https://developercommunity.visualstudio.com/content/problem/105499/tf30063-you-are-not-authorized-to-access-account-n.html

For connecting to VSTS: https://developercommunity.visualstudio.com/content/problem/114680/microsoft-test-manager-mtm-client-cannot-connect-t-1.html

Clicking on the Process tab of the XAML Build Editor results in TF30063

ADAL refresh token is stale but I'm not prompted to re-enter my credentials

It will likely be difficult for you to tell if your TF30063 error is the result of stale credentials. We are aware of a bug where your ADAL refresh token may be stale, and you're not being prompted to re-enter your credentials. We are currently working on a fix. In the meantime, a workaround is to:

I'm seeing the same issue, we've updated 5 users internall from 15.2 to 15.3 and all have this issue. You can temporarily solve it by removing the project from Team explorer and oping it again from manage-connections, but after closing VS and reopening it seems to come back.

One more comment on this, I've uninstalled, re-installed and still had the problem. If I close VS with the TFVC Source Explorer window open, then when reopening VS I always an the error:---------------------------Microsoft Visual Studio---------------------------Team Foundation ErrorTF30063: You are not authorized to access .visualstudio.com.---------------------------OK --------------------------- if I ensure I close the source explorer windows before closing VS then VS will restart without error, but if I go to the pending changes tab operations like 'Find Shelvesets' are disabled and if I try and check a file out I get the error:---------------------------Microsoft Visual Studio---------------------------ErrorTF204017: The operation cannot be completed because the user (Stephen Woolhead) does not have one or more required permissions (Use) for workspace DT-STEPHEN-03;Stephen I. Woolhead.---------------------------OK ---------------------------

Awesome. There is a timing issue during VS startup 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. I have a fix for that which I'm working on getting into the product.

If I close VS with the TFVC Source Explorer window open, then when reopening VS I always displays an error. If I ensure I close the source explorer windows before closing VS then VS will restart without error, but if I go to the pending changes tab operations like 'Find Shelvesets' are disabled and am unable to check out files.

I am still experiencing similar issues. The git client just says "Failed to fetch from the remote repository. See the Output window for more details." I upgraded 15.3.5 then reinstalled the git for windows client and remove the local appdata related to VS and .IdentityService, but no success.

Solutions

I was able to get this working with a workaround. I closed VS, deleted my VS appdata folder, then reopened VS. I could then connect without a problem. WARNING: This will reset all your settings and I lost a couple of my extensions that I had installed.

SOLVED: I ran into the same issue of TF 30063 on v15.3.5 right after changing my network AD password (enterprise policy). Previously you would be prompted to updated your user credentials for on-prem TFS, however at some point in one of the recent VS patches this appears to have stopped being the case. Even after deleting the connection, closing VS, and going back in and trying to add again the credentials wouldn't change.

The issue was that my previous credentials were cached by the Windows OS for the TFS server. While some people might have had success wiping out the AppData temp folders, that is not required.

You need to update the credentials through Control Panel on the Windows OS.

For me on Windows 10: Close VS. Go to Control Panel (with small icon view)-->User Accounts-->Manage your credentials (on the left column)-->Select "Windows Credentials"-->Scroll down to the "Generic Credentials" section and look for your TFS server connection. Expand the pull down and click "Edit". Enter in new network password. Reopen VS and everything should work again.

In my particular case under Generic Credentials I had to reset/edit MicrosoftAccount:user=username where username is the account you're currently logged into your windows 10 OS. After the reset I clicked Manage Connections under Team Explorer in VS, click Connect to Project and now you should be able to see your vs projects in your account, hit connect and done.

I simply changed the name of the VisualStudio folder to "VisualStudio - old", then when I started Visual Studio again it automatically generated a new folder. When it started up, I needed to log back into my account. I was then able to get access to my projects and the error disappeared.

Using 15.3.4 and I get TF30063 for on premise server. No way to add new server or enter credentials meaning the menus to enter credentials are gone. So re-adding a server is not possible. Please provide workaround while we wait for fix.

Are you having problems adding a new server or reconnecting to an existing TFS server you have on the Connect Page? If the latter, can you try removing your connection and reconnecting?

* Remove your connection to the server (remove whatever team projects are listed for it on the Connect Page)

* In the connect dialog (from 'manage connections' on the connect page) right-click the server and Remove.

* Exit and restart VS (to make sure nothing is cached in memory)

* Go back to the connect dialog and Add Server for the TFS server you're trying to reach. At this point you should be prompted to sign in if the user account with which you're signed in to Windows doesn't have access.

Once you add a non-hosted TFS server connection we should reconnect each time with whatever sign-in information was cached at the time of adding the server. It's possible that your cached info has gotten lost or we at some point cached the wrong identity so are now trying to use it and failing. Can you try:

* Removing your connection to the server (remove whatever team projects are listed for it on the Connect Page

* In the connect dialog (from 'manage connections' on the connect page) right-click the server and Remove.

* Exit and restart VS (to make sure nothing is cached in memory)

* Go back to the connect dialog and Add Server for the TFS server you're trying to reach. At this point you should be prompted to sign in if the user account with which you're signed in to Windows doesn't have access.