Team Explorer shows four directories in a single project: "Work Items", "Documents", "Reports" and "Team Builds". But there're always red cross on "Documents" and "Reports", even I've set the user as an Administrator.

Many thanks!

Jeffrey,

Sorry you are seeing this issue.

In TFS V1 there is no co-ordination of permissions across TFS, Sharepoint and Reporting Services. Being an Administrator in TFS has no bearing on being authorized to use Sharepoint or Reporting Services. You'll need to add the user as a reader or contributor on the Sharepoint site (through Sharepoint site administration) and as a reader or contributor in Report Manager.

One way to get around the lack of co-ordination (and to manage users more easily) is to create an AD security group and add it in 3 places (in TFS, Sharepoint and Reporting Services). Then when you want to add a new user to the system, just add them to the security group.

Please let me know if this helps, or if you have a different problem here.

Thanks,

Thanks for your reply, Dan.

I've check what you said but I found it still has the same problem, even I use the Administrator (of all the services).

(For some reason, I'm using local account of the server to login, but it means nothing to this problem, right?)

Thanks.

Another route is to use the "TFS Admin Tool" to sync the permissions between TFS, Sharepoint, and Reporting.

http://www.gotdotnet.com/codegallery/codegallery.aspx?id=cea30722-cd0a-4ef4-9c75-a5a5e4932b05

You can also just browse directly to the sharepoint and reporting sites and they should give the same error as the Team Explorer interface (the permissions problem, most likely) which should at least help clarify exactly the problems that's going on (maybe it's not actually permissions, but something else).

Even I have assigned all user rights to my account in TFS , share portal site and reporting site, I have still red cross on my documents folder, on my client machine. I have noticed that on other client machine I haven't red cross!?.

Following instructions by Dan Kershaw (provided in msdn forum), I have cleared the client side cache and run "devenv /resetuserdata".

These actions, didn't solve the problem.

Thanks

Janko

From the client machine that's failing, you may want to try loading up the WSS and Reporting URL's in IE to see how that goes (http://server/ and http://server/Reports/)

Hopefully that will give some insight into what's going on (bad proxy, network problem to that machine, credentials, etc.)