TFS gives permission error when trying to check out file

Sometimes, when I try to check out a file, Visual Studio gives me the following error:

---------------------------
Microsoft Visual Studio
---------------------------
Error

TF204017: The operation cannot be completed because the user (TLR\u0057716) does not have one or more required permissions (Use) for workspace U0124429-W7A;TLR\U0124429.

I am user U0124429, not user u0057716, so it is getting me confused with someone else, then telling me I don't have access to my own workspace. u005716 is a developer who is not on my team, has never worked on my machine, and to my knowledge never worked on this code base.

Restarting Visual Studio resolves the issue, but it is annoying. Has anyone else seen this? Is there a way to get it to stop happening?

Find more posts tagged with

refinitiv-internal

Accepted answers

Ryan Morlok

An update from CM about helping track when this is happening:

TFS Users,

CM continues to work with Microsoft to resolve the TFS access denied issues and we are at a stage where we need your input. Moving forward, if you see the ‘TFS Access Denied error message’, kindly capture the details and share them with us

Two possible ways to share the details:

1. [Fill out this online form][1] **_OR_**
2. Email [CM][2] (Co\_CM\_Tech) with the same details:
1. Error message
* Example: Operation cannot be completed because user (TLR\Random_Userid) does not have one or more required permissions (Use) for workspace Workspace_Name;TLR\Actual_Userid
2. Version.config @ C:\users\userid\AppData\Local\Microsoft\Team Foundation\3.0\Cache\Version.config
3. What is the IDE that is open at the time of the error
* Visual Studio
* Eclipse
* Other
4. Do you have more than one sessions to TFS on your machine (Visual Studio/Eclipse)
5. Did you recently create the workspace that you are using at the time of error?
6. Did you select the workspace to be Private, public limited or Public (if you have used the default, it will be private)
7. Did you share the workspace name with anyone that has viewed/checked-in files to your workspace
8. Any other information you'd like to share

[1]: http://tfsnpt.int.thomson.com/Lists/TFS Access Denied Issue Tracker/AllItems.aspx
[2]: mailto:West.Co_CM_TECH@thomson.com

All comments

James Greene

This occasionally happens during the actual builds as well. I've talked to CM about it before, and I believe they said they were aware of the issue and working to integrate a fix. That, however, was maybe 2 months ago so I'm not sure of its status today (clearly not fixed, I guess).

I do not know of any way to resolve it other than either trying again (this sometimes works) or else restarting Visual Studio.

Greg Bender

Doesn't look entirely related, but might be worth taking a look at: http://techoverflow.int.westgroup.com/questions/490/authentication-issues-accessing-tfswt-instance-from-command-line

I had tons of authentication issues until I told TFS to not use my proxy for connections.

Lavanya Gundamaraju

CM is working with Microsfot on this one. It is a server side error. Hopefully SP2 will be all what we need. When is that coming? no ETA from Microsoft.

Ryan Morlok

Lavanya, any update on this issue? I'm seeing it again.

James Greene

Looks completely **un**related. :-\

Ryan Morlok

James Greene

**Latest update:** According to CM (via an email from Kelly Hein), these TFS permissions issues have been resolved as of today, 2012-09-04.

Lavanya Gundamaraju

We have taken below steps to fix the access denied issues with the TFS.

1) We configured PROD setup account to have “Managed Build Resources’ permission in the TFS Collection Level.

2) Updated Service pack 2 in all the Build controllers that has Windows 2008 Enterprise Operating System.

3) Updated latest Proxy settings on all build controllers.

4) Disabled “OneConnect’ BigIP feature for http://tfsnpt.int.thomson.com <../../../../../> (Port 8080 and 80) that reuses persistent connections to the pool servers, in order to save processing by not having to continually open/close connections.

If you see below error message when you “Get Latest” from TFS through Visual Studio or Eclipse, please let us know.

The operation cannot be completed because the user (TLR\RANDOM-USERID) do not have one or more required permission (Use) for workspace ACTUAL-USER-COMPUTERNAME\TLR-ACTUAL-USERID”

Note: According to the TFS design, If the build controller have performance issues or TFS build host service (tfsbuildservicehost) hangs/not working then you will see the following error message in the event viewer and in the build log.
TF215106: Access denied. TLR\USER-ID needs Update build information permissions for build definition (BUILD DEFINITION NAME) in team project (COBALT PROJECT NAME) to perform the action. For more information, contact the Team Foundation Server administrator.
Details of the issues

Issue 1: Access denied issues in the build log when updating build information using PROD setup account.

Error: TF215097: An error occurred while initializing a build for build definition (\Team Project\Build Name): TF215106: Access denied. Domain\User needs Update build information permissions for build definition (Build Name) in team project (Team Project) to perform the action. For more information, contact the Team Foundation Server administrator.

Fix: PROD setup account was missing "manage build resources' permission and that caused access denied issue. Enabled the ‘Manage build Resources’ permission for the “AppWestTFNPRODSetup” account in the collection level and fixed the issue. The reason TFS using setup account for the build update because it is part of “Project Collection Administrator”.

Root Cause: Missing permissions

Issue 2: Users are receiving permission denied error message on the workstation when they "Get latest" action through Visual Studio and Eclipse. The same permission issues with temporary build workspace causing “coreget” failed in build process with random user id and the issue is intermittent.

Error: The operation cannot be completed because the user (TLR\RANDOM-USERID) do not have one or more required permission (Use) for workspace ACTUAL-USER-COMPUTERNAME\TLR-ACTUAL-USERID

Fix: Worked with network team and disabled oneconnect feature in BigIP (for http://tfsnpt.int.thomson.com:8080) that reuses persistent connections to the pool servers, in order to save processing by not having to continually open/close connections.

Root Cause: The pooled connections feature (“One connect –feature in Big-IP load balancer) was not disabled and that why we were seeing the workspace errors. TFS cache a user’s credentials in IIS, also for performance reasons. If a user had their credentials cached, and then that connection was ‘re-used’ then TFS would see the valid user coming in as someone else but know the workspace identified by the local cache on their workstation did not belong to that user.

Note: In future, when create BiGIP request for any new TFS URL please make sure persistent should be set to "Yes". By default it will be "No" in BANANA Request

Issue 3: Report URL is not working when accessing through browsers like (IE, Firefox and Chrome).

Error: On accessing TFS reports, when the user clicks the direct report link (below link) first time, they get “Internet Explorer cannot display the webpage” message. If they hit refresh button it takes them to the page correctly.

Fix: Worked with BigIP network team and disabled one connect for TFS Reports that’s run on port 80 ( http://tfsnpt.int.thomson.com/Reports/ ). This resolved the issue.

Root cause: One Connect Feature in Big-IP: Oneconnect is a feature that reuses persistent connections to the pool servers, in order to save processing by not having to continually open/close connections. This is a very common configuration in our environment, and very rarely causes any issues (Thanks to Price Jason).

Referenced: http://www.f5.com/pdf/deployment-guides/oneconnect-tuning-dg.pdf

Additional steps taken towards access denied issues:

1) Updated Service pack 2 for all Windows 2008 Enterprise servers.

2) Updated Proxy settings on all build controllers.

James Greene

**Latest update:** According to CM (via an email from Kelly Hein), these TFS permissions issues have been resolved as of today, 2012-09-04.

EXPLORE OUR SITES