Unable to create new TFS 2010 project w/ SharePoint site

Question

When attempting to create a new TFS 2010 team project with a SharePoint portal, I get the following message:

TF218017: A SharePoint site could not be created for use as the team project portal. The following error ocurred: TF250044: A SharePoint site cannot be created at the following location: http://XXXX/sites/DefaultCollection/XXXXXX. The following user account does not have the required permissions in SharePoint Products to create a site at that location: DOMAIN\USER. The user account must have sufficient permissions to create a sub-site on the following site: http://XXXX/sites/DefaultCollection/XXXXXX.

I read a suggestion somewhere that mentioned adding my account to the Site collection administrators of the DefaultCollection. Step 1 was navigating to http://XXXX/sites/DefaultCollection... well, that failed with a big ol' "Error: Access Denied"

I have access to the TFS Administration Console and have been told I am an administrator w/ full privileges. Unfortuneately, the consultant that setup TFS is no longer with us.

Any suggestions for troublehsooting this?

Thanks!

Answer 1

I too had thus trouble, and after some rather arcane searching with google found the following: http://lifeaccordingtoabel.blogspot.ca/2009/08/create-team-project-failure-and.html

Essentially, you have to add your user as having Full Control in the DefaultCollection share point site first, then add your user as having full control in the Sharepoint Central Administration tool as well.

Answer 2

You can use the Team Foundation Server Administration Console, navigate to "%Server%\Application Tier\SharePoint Web Applications" and add your domain account to the "Service Accounts for SharePoint Web Applications". This should grant you access to the SharePoint sites.

Answer 3

you have to go the site collection and add the user as site collection administrator. each new team project will create a sub site under the root so the user must have the permissions on it. neither the service account or farm admin will solve this problem.