TFS 2015 and Sharepoint integration; TF30063 error

0
votes

Both TFS 2015 and Sharepoint 2013 Foundation are on-premise installations. They are on separate servers. Sharepoint is being configured post TFS installation - although I am not currently updating any existing projects.

Account being used to access the sharepoint site is a full admin on both sharepoint collection as well as TFS too.

TFS Extensions are installed, and configured on the Sharepoint server.

Can successfully create a new TFS 2015 project, and see it create the Sharepoint site - however upon accessing the Sharepoint portal site I see a number of TF30063: You are not authorized to access http://app-p-tfs01:8080/tfs errors.

I note that the collection is not listed on the url; I am looking to use the root web application of the sharepoint site as the root location.

Nothing appearing in Security event logs nor the TFS _oi audit.

Any pointers on where to look next?

Sharepoint Dashboard Screenshot

2
sharepointtfs
It's worth noting that the Sharepoint integration is largely unnecessary these days -- teams can have customized dashboards that far exceed what's present in Sharepoint. Sharepoint also commonly represents a major pain point when upgrading TFS. – Daniel Mann
Yup - we're being asked to set this up by our PM team for linked documentation storage etc. – Andy Neillans

2 Answers

1
votes

The "TF30063" error message indicates that your account doesn't have permission to access TFS. As this blog described, it is caused when some permissions are denied somewhere because deny takes precedence over any other permission.

So, you can run the tfssecurity /imx command to check which group the account belongs to. Then check these group one by one to see the required permissions are not denied.

For the reporting service error, seems that the report doesn't run correctly. Firstly, go to the report server and ensure the data source can be connected successfully.

0
votes

After discussing this with Microsoft Support today, it transpired the account Sharepoint was running under (which oddly is the same as TFS), did not have the relevant access - even though it WAS listed under the relevant Services group.

This was added to the Administrators group and all was well.

Very strange.