TFS 2012 - Issue: TF30063: You are not authorized to access and can’t trace permissions

TL;DR

Explains how a global "deny" permission in TFS 2012 can block SharePoint 2010 access, causing TF30063 errors, and highlights where to check for inherited permission issues.

30 August 2012
Written by Martin Hinshelwood
2 minute read
Comments
Subscribe

No matter what permissions you set or what permissions you have you get a “TF30063: You are not authorized to access /Services/v3.0/LocationService.asmx” in SharePoint 2010.

image

Figure: Errors on the TFS components

And you have checked all of the usual suspects and even use the new TFS 2012 permission tracing features to no avail.

image

Figure: Cannot trace permissions on this item

Applies to

  • Visual Studio 2012 Team Foundation Server
  • Microsoft SharePoint 2010

Findings

I don’t know how unique my case is, but if you have searched the heck out of “TF30063: You are not authorized to access LocationService ” and you still can’t find the issue then it is simple.

You do not have permission to read items in TFS from SharePoint!

tearing_hair_out-300x271

Figure: Ahhhhhhhhhh

But I am logged in as the TFS Service account, TFS Administrator account and a SharePoint Farm Admin… how many more permission do I need! Here is the deal… you have a “deny” in your permission list somewhere. Deny takes presidence over any other permission. So if you have a deny high up but an allow lower down then this is just tough… denied. And if it is doing this for all of your users regardless of permissions or groups then I have a suspension that there is some deny high up in TFS. There are only two groups that apply to everyone…

image

Figure: [TEAM FOUNDATION]Team Foundation Valid User

There are two places to look for global deny’s and that is the “Valid User” groups at either the server or at the collection level.

image

Figure: [DefaultCollection]Project Collection Valid Users

In this case we upgraded from Team Foundation Server 2008 to 2012 so any permissions carried over would be at the Collection level, so lets start there…

image

Figure: Really… denied at the Project Collection Level

I can’t imagine what was trying to be achieved by this… so I will leave you with…

ImpliedFacePalm

Smart Classifications

Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.

Comments
Subscribe

What to read next

Article

TFS 2012 - Issue: Manage Group Membership missing from admin after TFS 2008 to TFS 2012 Upgrade

Explains how to restore missing group membership management in TFS 2012 after upgrading from TFS 2008 by manually adding permissions using …

Read article
Article Engineering Excellence

Access denied for orchestration plan on Build

Explains how to resolve TFS build errors caused by missing write permissions for the Project Collection Build Service on orchestration …

Read article