Menu
I'm noticing this repeatedly with VS2022. Everything starts off well but eventually it seems to lose my authorization on my Azure DevOps project.
I open a solution and VS 2022 connects to Azure Devops. Maybe I make a commit or two and type the little hashtag ('#') symbol in the comment box and sure enough, the list of available work-items appears for me to associate with the checkin. Things are great.
But eventually, that stops working. Nothing appears when I hit the hashtag. So I go to the Team Explorer window and I see this message at the top:
TF30063: You are not authorized to access dev.azure.com/<mycompanyname>.
I try reconnecting through Team Explorer but it doesn't do anything. But if I restart Visual Studio, I'm all connected again. For a while until it happens again.
Anyone have this or know how to fix it? It does not happen to me with VS2019
544
Fix/Solution: Generate a new PAT token that has “Full” access instead of the custom access . The reason here is when you try to run an agent the PAT token needs full access instead of custom access only to builds and code!
I'm noticing this repeatedly with VS2022. Everything starts off well but eventually it seems to lose my authorization on my Azure DevOps project. I open a solution and VS 2022 connects to Azure Devops.
Recently I was working with Microsoft Visual Studio 2017 and got the following error with TFS, which says, “You are not authorized to access Team Foundation Service”. The error code was TF30063.
You should contact Microsoft if you are still having it. File Feedback through the Help Menu on Visual Studio 2022 item, click "Other" button, then "Repair". that's all. At first I thought this actually works. Then after few hours the issue returned, so this is not a solution unfortunately.
This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different server, click ‘Connect To Azure DevOps Server’ in Team Explorer or the Team menu.
Experienced the same problem was well. By accident I switched VS 2022 from the embeded to the system browser (Options->Accounts) and after restarting VS 2022 it worked well, however it can be a coincidence:
110
Just to put a bookend on this, Dan Schulte of Microsoft has officially responded in this thread (see his Dec 14 reply) that they've found the root cause of this problem and have created a fix for it but that the fix won't be released until January.
Apparently it was pretty low level and very hairy and affected not just VS2022 but also previous version. It was something that none of the lists workarounds could truly fix. So I wouldn't bother running repair on your VS install or any of that. It won't fix it.
43
I had same problem and solved by following this:
that's all.
3
after updating the version to 17.0.5 its problem was solved.
3
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
