Team Project Portals missing after Upgrade from TFS 2008 to TFS 2010 Beta 2 - How do I recreate them?

Question

We upgraded TFS from TFS 2008 (with SP1) to TFS 2010 Beta 2.  This is a single server deployment for a small team, with TFS, WSS and SQL all on the same Windows 2003 (with SP2) server.  As part of the process, we upgraded WSS 3.0 to 3.0 SP1, and SQL 2005 to SQL 2008 with SP1.

The TFS 2010 Beta 2 install ran normally.  The Upgrade Configuration tool ran normally as well, however it ended with a few warnings:

[
Warning TF205018: An error occurred when attempting to save the mapping from the SharePoint Web application to Team Foundation Server. The SharePoint Web application is: http://SERVERNAME/. The error is: TF250067: No connection could be made to Team Foundation Server at the following address: http://SERVERNAME:8080/tfs. Either the specified URL does not point to a server that is running Team Foundation Server, the server is not available, or the service account for SharePoint Products does not have sufficient permissions on that server. The service account for SharePoint Products might not have been added to the required group in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=161206)..

Warning TF252014: A SharePoint site could not be created at the following location: http://SERVERNAME/sites/DefaultCollection. The server returned the following error message: TF250034: An access grant could not be found between Team Foundation Server and the SharePoint Web application that you specified. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. The SharePoint Web application is: http://SERVERNAME/sites/DefaultCollection. You must grant access for the Web application in the Team Foundation Administration Console.. To address this error, open the Team Foundation Administration Console and make sure that the settings for the SharePoint Web applications that supports this team project collection are correct.

Warning Failed to attach to the portal for project OldTfsProjectName. Portal address: http://SERVERNAME/sites/OldTfsProjectName. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://SERVERNAME/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.
]

All our old TFS 2008 projects show up after the upgrade to TFS 2010 Beta 2 within Team Explorer.  The Work Items, Source Control Tree, and the shared documents all seem okay.  (Sweet relief).

Note that:
* WSS Central Administration site comes up fine
* the new TFS Web Access site comes up fine
* the default WSS site comes up fine

The missing part however is that none of the old project portals can be found.  The old sites are completely gone from SharePoint.

Do you have any advice on how to recreate the Team Project Portals for the existing TFS projects that were migrated from TFS 2008 to TFS 2010 Beta 2?

Best regards,
Joe

Answer 1

Joe, this appears to be caused by the SharePoint service account not being granted access to the TFS deployment. Can you do the following.
- Open the Team Foundation Server Administration Console from the TFS Appllication Tier.
- Click on SharePoint node (You will see a two pane window appear on the right)
- View what accounts are listed in the the lower pane (This is a list of all the SharePoint service accounts that have been granted access to TFS)

What accounts are there? It should be the same service accounts that are running the SharePoint application pools.

Can you verify this and post back?

Also, if you could attach the log of the installation, that would be very helpful in figuring out what happened.

---

Team Foundation Server

Answer 2

Greg,

Thanks for the response.  I'm thinking the following is what happened:

1.  Sharepoint Central Admin App Pool was set to run under LocalSystem

2.  TFS was configured to run under a custom service account (lets call it TfsService)

3.  The Upgrade was unable to create the top level site for DefaultCollection and for each of the TFS2008 projects it was upgrading

Subsequently:

1.  I changed the Sharepoint Central Admin App Pool to run under TfsService

2.  Added TfsService to the Service Accounts for Sharepoint Web Apps

3.  I created a new Team Project, and it was able to create a Team Portal successfully.

Regarding the info you requested, under TFS Admin Console -> Application Tier  -> Service Accounts for Sharepoint Web Apps, I currently have the following accounts:

TfsService, LocalSystem,NetworkService,SsrsService

So the question at the moment is this - How do I recreate the Team Portals manually for the TFS 2008 projects that were migrated over but for whom the team portals were not created by the upgrade?

I've looked but can't find the full log.  The one I found has the Sharepoint warnings that came up during the upgrade.  I'm including that at the end of this post.

Best regards,

Joe

[2009-10-23 17:50:23Z][Warning] TF205018: An error occurred when attempting to save the mapping from the SharePoint Web application to Team Foundation Server. The SharePoint Web application is: http://denivs011/. The error is: TF250067: No connection could be made to Team Foundation Server at the following address: http://denivs011:8080/tfs. Either the specified URL does not point to a server that is running Team Foundation Server, the server is not available, or the service account for SharePoint Products does not have sufficient permissions on that server. The service account for SharePoint Products might not have been added to the required group in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=161206)..

[2009-10-23 17:50:24Z][Warning] TF252014: A SharePoint site could not be created at the following location: http://denivs011/sites/DefaultCollection. The server returned the following error message: TF250034: An access grant could not be found between Team Foundation Server and the SharePoint Web application that you specified. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. The SharePoint Web application is: http://denivs011/sites/DefaultCollection. You must grant access for the Web application in the Team Foundation Administration Console.. To address this error, open the Team Foundation Administration Console and make sure that the settings for the SharePoint Web applications that supports this team project collection are correct.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TSS-ScrumTest1. Portal address: http://denivs011/sites/TSS-ScrumTest1. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TSS-Master. Portal address: http://denivs011/sites/TSS-Master. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TestProject1. Portal address: http://denivs011/sites/TestProject1. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TSS-VS2008. Portal address: http://denivs011/sites/TSS-VS2008. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TSS-Studio. Portal address: http://denivs011/sites/TSS-Studio. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

[2009-10-23 17:50:25Z][Warning] Failed to attach to the portal for project TSS-Rel-5. Portal address: http://denivs011/sites/TSS-Rel-5. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://denivs011/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

Answer 3

Let's back up just a bit.

Are you saying that after the upgrade that the SharePoint sites for the upgraded projects are not even in SharePoint?  What URL were they at before the upgrade?  What SharePoint settings did you specify during the upgrade?

The TFS upgrade certainly will not delete sites, but it won't move them either.  So you should specify the same base URL as before (unless you have moved them to a different SharePoint server manually).

Are the TFS 2010 beta 2 extensions for SharePoint installed on the SharePoint server?  if TFS and SharePoint are on separate machines, you have to install the SharePoint extensions before doing the TFS server.

Is the TFS service account in the Farm Administrators group in SharePoint before doing the TFS upgrade?  All those warnings may simply be because of that.  This should happen automagically if TFS and SharePoint are on the same machine.  We know this happens for install.  We are double checking to ensure it happens for upgrade as well.  However, if they are on separate machines, you have to add the TFS service account(s) to the Farm Admin group manually.

The upgrade process does not create new sites for upgraded projects.  It should create a top level site for the project collection (where new project sites for the TPC will be created).  The sites for upgraded projects should be "hooked" up to their old sites as long as the settings you give in the upgrade wizard point to the same location.

I hope this helps,
  Mary Ellen Chaffin

Answer 4

Hi Mary,

This is a single-server deployment, TFS 2010 Beta 2, SQL 2008 with SP1 and WSS 3.0 with SP2 are on the same server.  This was the case before and after the Beta 2 upgrade (except for the version nos).

The url for the TFS 2008 project portals were the defaults, something like:

http://TfsServer/sites/TfsProject2008

I just get an "HTTP 404 not found" now on trying to reach any of the urls for the old TFS 2008 projects.  I tried looking for the old sites in both the root WSS site as well as the Central Admin site, but no dice.  Is there some other way of searching for the old team portals?

I created a test 2010 Beta 2 team project, and that gives me normal access to its portal:

http://TfsServer/sites/TfsProject2010Test

Is it possible that either of the following deleted the old TFS 2008 sites (if its not the TFS 2010 Beta 2 upgrade):

1. Upgrade from WSS 3.0 SP1 to SP2

2. Upgrade from SQL 2005 SP2 to SQL 2008 and then to SQL 2008 SP1

In any case, is there a way to recreate the team portals for the TFS 2008 projects that are now in TFS 2010 Beta 2?

Thanks,
Joe

Answer 5

I'm not that familiar with the upgrades for SharePoint or SQL, but its possible that they did it.

Can you look in "c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs" to see if there is a log for the upgrade.  Its possible that it created a new content database... and didn't hook up the old content database.  When you upgraded SharePoint, what options did you specify.

Could you get to the project sites after upgrading SharePoint, but before upgrading TFS?

Go to the http://server:17012/_admin/applications.aspx page on your Central Admin site.  Then click on Site Collection list.  What is the database name that is listed for the site collections?  Do you have any other Wss_Content* databases in SQL Server?  If so, it might be the old content database.  You might be able to get the sites back using the "addcontentdb" command on Stsadm.exe.

Mary-Ellen

Answer 6

Hi Mary-Ellen,

Thanks for the response.  I checked the http://TfsServer:11208/_admin/SiteCollections.aspx site, and lo and behold all the project portals are in there, including the old TFS 2008 projects as well as the new TFS 2010 project.

The urls all follow the standard format http://TfsServer/sites/TfsProjectName.  The Database Name for all the site collections is STS_Content_TFS.

The url for the TFS 2010 project portal takes me to the dashboard.  However the urls for all the old TFS 2008 projects just gets me a 404.

Prior to the upgrade, we had created other top level sites on http://TfsServer and they all remained unchanged after the TFS 2010 Beta 2 upgrade.

We don't have the SharePoint log, as trace logging had been disabled.

Any thoughts on why the site collections list shows up in the admin site, but can't be accessed directly?  Any option to restore them or to recreate them?

Thanks!

Joe

Answer 7

Also, I would like to point out something in the original warning I got during the TFS upgrade (in my initial post):

[

Warning Failed to attach to the portal for project OldTfsProjectName. Portal address: http://SERVERNAME/sites/OldTfsProjectName. Use the Portal Settings dialog to attach manually. The following exception occurred: TF250057: No access rights were found for the following SharePoint Web application: http://SERVERNAME/. The Team Foundation Server ID is: 0a842b58-29c7-4862-b96e-b81a00885d85. You must grant access for this SharePoint Web application before you can use it.

]

It could have been an access issue that was fixed by my later actions (which was probably why I was then able to create the TFS 2010 project and portal successfully).

The line I want to point out is "Failed to attach to the portal for project OldTfsProjectName ... Use the Portal Settings dialog to attach manually."  How do I do this?

Thanks,

Joe

Answer 8

The error about the access rights means that the SharePoint web application doesn't know about that TFS server.  This should have been hooked up during the upgrade process.  I would love to see the configuration logs from the upgrade.  Can you send it to me at mchaffin ( at ) microsoft . com?

-- Open the TFS Admin Console (tfsmgmt.exe).
-- Click on the Application Tier node.
-- Click on the SharePoint Web Applications node.
-- Select the web application from the right side.
-- Click the Repair Connection button.
-- Click Repair on the dialog that comes up.
-- It'll show you status as it goes... and will log to a new log that you can get to using the Logs node of the admin console.
-- When its done repairing, close the dialog.


To change the portal settings for a particular project, right click on the project in Team Explorer.  Then select, Team Project Settings... and then Portal Settings.  You can specify a SharePoint site or a plain ol' URL for our portal and for the process guidance using that dialog.

To hook up an upgraded TFS 2008 project to its old site,
-- On the Project Portal tab,
-- -- Check the "Enable team project portal" check box.
-- -- Select "Use this SharePoint site"
-- -- Click on the "Configure URL" button.
-- -- Select the web application from the combo box (http://server).
-- -- Enter the relative path for the project site (sites/ProjectName).
-- -- Click OK.
-- -- Now, check the "reports and dashboards..." check box.
-- On the Process Guidance tab,
-- -- Check the "Enable the link to process guidance" check box.
-- -- Select "Link to a SharePoint document library"
-- -- Click on the "Configure URL" button.
-- -- Select the web application from the combo box (http://server).
-- -- Enter the relative path for the project site (sites/ProjectName).
-- -- Click the Refresh button to get the list of doc libs.
-- -- Select the one named "Process Guidance"
-- -- Click OK.
-- Back on the main portal settings dialog, click OK to save it all.


I hope this helps,
  Mary Ellen

Answer 9

YOu can always point a team project at a project portal by doing the following:
- Open up Visual Studio / Team Explorer. Open up the team project you want to connect.
- Right click on the Team Project name, and select Portal Settings.

In that dialog, you can select which SharePoint server your portal is on, then specify the path to the portal.
Be sure to check the box that says: "Reports and Dashboards show data for this team project". That will tell the portal that it "belongs" to this team project, and should present data for that team project.

You'll need to do this for each team project.

Make sense?

---

Team Foundation Server

Answer 10

Mary,

Thanks for the response and for the detailed steps.

I can email you the logs.  I'm seeing two in "C:\Program Files\Microsoft Team Foundation Server 2010\Microsoft Team Foundation Server 2010 Beta 2 - ENU\Logs":
dd_install_tfs_stdserver_100.txt / About 1/2 MB
dd_VSMsiLog466D.txt / About 6 MB

Would you like to see both or just the smaller one?  Is there another log file somewhere that could help?  Let me know and I'll get them to you.

Regarding the steps to "Reconnect SharePoint Web Application" within the TFS Administration Console, I followed all the steps.  The Reconnect dialog completed its steps successfully.  However, it did not recreate the old team portal.

I also followed the steps in Team Explorer 2010 -> Team Project Settings -> Portal Settings.  (This also applies to Gregg's response).  Everything already looks good in there.  It shows the Team Portal as http://SERVERNAME/sites/Old2008TfsProjectName, and has the correct url for the Process Guidance as well.

I think the basic problem is on the SharePoint side, so let me repeat this.  http://SERVERNAME/sites/OLD2008TfsProjectName gives me a 404 Not Found.  http://SERVERNAME/sites/NEW2010TfsProjectName works flawlessly.  I don't think the problem is on the TFS connection side.  I believe somehow the content itself got dropped on the SharePoint side when TFS 2010 Beta 2 was migrating the old TFS 2008 project.  The site collections themselves are there (I see them in http://TfsServer:11208/_admin/SiteCollections.aspx) - but actually trying to browse to them gives me a 404.

I do appreciate all the help, but feel somehow that my orginal question is not getting an answer (in bold, in my first post above):
Do you have any advice on how to recreate the Team Project Portals for the existing TFS projects that were migrated from TFS 2008 to TFS 2010 Beta 2?

Is this even possible?  We know that when we create a new Team Project, it automatically creates a new Portal with all the right links (to reports, web access, etc).  Can this be done for an existing Team Project whose portal is somehow (due to the upgrade in this case) missing?

Best regards,
Joe

Answer 11

The reconnect steps will not create any sites.  It will just make sure that the mappings between TFS and SharePoint are correct.  Then it makes sure that each project that has a site that it "owns" (see the "reports and dashboards" checkbox on the Portal Settings dialog) is actually hooked up to the site (meaning that the SharePoint site knows about the project).

Did you install a new SharePoint server with the new TFS server?  Before the upgrade did the  http://SERVERNAME/sites/OLD2008TfsProjectName site work?  If it didn't work in that location before the upgrade, it won't work after.  We do not move the sites for you.  If you change SharePoint servers during the upgrade, we expect that those sites exist in the new location (the one you specify in the upgrade wizard) already.

If you still have the old site up and running somewhere, you can use SharePoint's stsadm.exe to export it from that server and then import it to the new server.  That's going to be the only way to "recreate" it with all of its content.

If you just want a site at that location, then you can create it with the SharePoint user interface.

There is not currently a way to create a project site after the project is created in the same way that PCW created it (with all the files and such from the process template).  We are looking for a better solution, but for beta 2, you'll need to create the site manually or export/import from the old site.

I hope this helps,
  Mary Ellen Chaffin