MyDashboard on Root TFS Instance

Question

We've just set up TFS 2010 with Sharepoint 2010, and all the individual Project Collection Dashboards in Sharepoint 2010 look fine.  i.e. http://tfs/<ProjectCollectionName> looks and works great.

But if you go to http://tfs it automatically takes you to http://tfs/Dashboards/MyDashboard and all of the web parts there are broken and say that "This site doesn't have a default Team Foundation Server instance.  You can explicitly select a Team Foundation Server. "

How do I do that?  I'd like to make the top level Dashboard show the user all of their tasks and some other reports across all project collections and projects, but I am not sure this is possible.  Short of deleting all the web parts off this page and starting from scratch, is there an easy way to do this?

Thanks

 

Answer 1

Hi Joe,

To resolve this issue, you will need to register the internal URL for the SharePoint site using Alternate Access Mappings. Please follow these steps:

1. Log into the SharePoint Central Administration site (a link can be found under Control Panel > Administrative Tools)
2. Click on the “Operations” tab at the top
3. Under “Global Configuration”, choose “Alternate Access Mappings”
4. On the menu bar, select “Add Internal URLs”
5. Choose the web application that hosts your Project Portals (usually Default Web Site)
6. In the “URL protocol, host and port” text box, enter the alternate URL that can be used to access the Project Portals (must include http:// or https://).
7. Click Save.

Hope it helps! If you have any concern, please feel free to let me know!

Best Regards,

Cathy Kong

Answer 2

Hi joe,

I am changing the issue type to "Mark As Answer" because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to "Unmark As Answer" by clicking the option at the bellow of the post window. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and use by other community members having similar questions.

Best Regards,

Cathy Kong.

Answer 3

Hi Cathy

Unfortunately, our IT department has been tied up for the past couple of days, so they haven't been able to try this fix yet.  I'll let you know how it goes when they get back to me.

Thanks

Joe

Answer 4

I work with Joe, the OP of this thread. The issue in our situation wasn't the AAM (as it was already registered), but rather that the various web parts on the page didn't have a default Project Collection and Project associated with them. Editing each web part and pointing it to the appropriate Project Collection and Project (via the URL of the Application Tier TFS server) resolved the issue. Regards, Richard

Answer 5

Hi Richard,

Thanks for sharing your experiences!

Best Regards,

Cathy Kong

Answer 6

I fumbled around this for a while - the following blog post was a little harder to find, but had the solution. 

http://msmvps.com/blogs/vstsblog/archive/2010/04/09/how-to-set-the-default-team-project-for-a-sharepoint-site.aspx

Solution

You have to configure the project portal using Visual Studio Team Explorer 2010 using Team Project Settings » Portal Settings…

Answer 7

Hi;

 

there are 2 problems with MyDashboard.aspx page:

a. the tfs webparts which are on the page don't have reference to the project.

b. there are 2 tfs webparts missing, which are used by NewWorkItem and GoToWorkItem DelegatesControls.

To fix it You have to:

- open MyDashboard.aspx in Sharepoint Designer

- edit all tfs web parts and set Project, ProjectCollection and TfsName fields

- add Tfs web parts: GoToWorkItem & NewWorkItem

- configure them as other tfs web parts.

I have no idea, why all these actions are not performed from SharePoint when sites are generated, on when one sets the parameters for Team Portal.

Regards

bp

---

Bartosz

Answer 8

Hi Joe,

    I found the solution two be a combination of items posted here.

    1) First, follow the suggestions posted by Cathy and make sure the URL you are using to access the portal sites has been added to SharePoint as an Alternative Access Mapping.  I replaced the default zone with my URL as we also plan on adding a second web front end.

    2) Second, follow the steps posted here http://msmvps.com/blogs/vstsblog/archive/2010/04/09/how-to-set-the-default-team-project-for-a-sharepoint-site.aspx

        In my case we were migrating our databases to a new server and this included migrating the SharePoint Databases.  As a result we had some reconfiguring to do between SharePoint and TFS 2010.  Somewhere along the way we lost the portal configuration but step reset that.

Note: Make sure the account you are running Team Explorer (User Account) has access to the SharePoint Portals.  An easy cheat is to login to SharePoint Central Admin --> Application Management --> Policy for Web Applications and add your account with full controls.  This has often been referred to as an Adminstrator Back Door.

Thanks,

---

Dennis Bottjer | Follow Me: @dbottjer | Blog: Dennis Bottjer.com