I'm using TFS Preview (Team Foundation Service) with one of my projects with Visual Studio 2012. I'm also using an on-premises TFS server with most of my projects. When I use my on-premises TFS after using TFS preview and go back to using TFS preview, I get this error:
TF30063: You are not authorized to access MyProject\DefaultCollection.
If I go to Team → Disconnect TFS and then connect to TFS preview again, I'm able to see a "Loading identifiers" loading screen coming up, but in the end I don't get to enter my credentials to TFS preview (my Microsoft account) and as a result, the TF30063 error still occurs.
I suspect this has something to do with my Microsoft account (i.e. Live ID). I'm logged in to Windows with the same Microsoft account that I use at TFS preview. I have logged in to other sites (Windows Development Center, MSDN, etc.) with other Microsoft accounts, but I verified that if I log out of these services and re-login with the correct Microsoft account, I still get the TF30063 error when I try to log in to TFS preview from Visual Studio.
None of the current answers worked for me. I found a solution here.
I have just removed the server from Team Explorer, then added again, and it worked =).
I got this error, after all fiddling work i could do .. found disk space full! clearing it fixed my issue. -pasha
Just restarting the visual Studio would do the job. As I did this and it worked like a charm
I tried the following to resolve this issue. Hopefully one of these will work for you
A - Close VS then start the VS Developer Command prompt as an administrator. Then enter:
devenv /resetuserdata
B - Clear the cache in IE (apparently VS uses this to access your account mentioned here)
C - Click
View -> Other Window -> Web browser (CTRL+ALT+r)
sign in to your old account, log out and sign in to your new oneD - Open the folder containing you solution, delete (backup if you want) the
Visual Studio Source Control Solution Metadata File
delete the.suo
file and open the .sln file in Notepad and delete the below sectionThe last step was required because, while I had managed to disconnect VS my solution was still trying to connect to the old source control account.