I have created a Team Project in TFS 2010 and the Project Portal in SharePoint 2010.
Now I need to create a WebPart to deploy in the SharePoint Site (Project portal) that connects to the TFS to get some information.
Where I can get the TFS Url that is associated with the Project Portal in SharePoint?
Any clues?
Thanks in advance.
The url of TFS is not stored in the Project Portal. It is the other way round. In TFS the WSS url is stored.
TfsRedirect can be used to determine the TFS Web Access URL from within SharePoint. Although it's not exactly what you want, and it's a little hacky - you can pass the parameter tf:Test=1 to get the TFS team project that is associated with the site that your web part is being displayed on.
See John Socha-Leialoha's blog post on Using TfsRedirect to Display Reports in TFS 2010 Dashboards
What is TfsRedirect?
Here’s the scenario. You had TFS create a dashboard site in SharePoint
when you created your team project (or you added it later as described
here). There are several items on this dashboard that point to other
locations that are potentially on other servers:
Team Web Access
Process Guidance
Reports shown on the dashboard pages
TFS itself know where to find these assets. And the locations can
change if, for example, the TFS administrator moves the reports to a
different server.
Rather than hard-code the locations of these assets into the
dashboard, the TFS team created a web page called TfsRedirect.aspx
that knows where these different assets are located, and will redirect
to that page.
Shouldn't you be able to go in to TFS2010 -> Team Explorer -> Right-Click on your Team Project -> Portal Settings?
Related
I just moved my tfs 2013 in one server to tfs 2015 update 1 on another server, and I also changed the DB server behind.
Everything worked perfectly fine on the migration except for the sharepoint integration, unfortunately during the migration, the sharepoint content database where it was pointing to had physical errors on its content database (wss_content).
However I created another webapplication http://portaltfs, where I want to make the integration with tfs.
However, when I click on change or add, I get this error
Check this blog to see whether your upgrade process is correct. And try try to remove SharePoint extension and re-configure it.
Also, since you would attach the content database which migrated from TFS 2013, after creating new web application with the web site name and port number, go to
Manage Content Database from Central Administrator site, and select the web application created and check Remove content database. Then open SharePoint 2013 Management shell and use Mount-SPContentDatabase to attach the old content database. Refer to the blog for more details.
Problem summary:
I have just built a new TFS 2013 environment for my organization. On my first attempt\test creating a new team project using Visual Studio 2013, I receive the following error at the final stage (Finish button):
"TF218017: A SharePoint site could not be created for use as the team project portal. The following error ocured: Server was unable to process request. ---> The user does not exist or is not unique.---> The user does not exist or is not unique."
I have found several other posts with folks encountering this same error but the proposed solution seems to always be to change the authentication mode in SharePoint to classic which is not available in SharePoint 2013.
The error message implies that this is permissions related. However, it is a little baffling due the fact that when I created a new TFS Project collection using the TFS Admin console it created a new site collection in SharePoint with no issues. I don't understand how my permissions would allow me to create a site collection but not place sites under the site collection.
Here are some details about my setup:
TFS 2013 running on Windows Server 2008 R2 Enterprise
SharePoint 2013 Foundation (separate server within same domain as TFS
server)
TFS Service account is a Site collection admin on the SharePoint site
collection
My AD account is a Site Collection admin on the SharePoint site
Collection
TFS Service account is a Farm Admin in SharePoint
My AD account is a Farm Admin in SharePoint
The TFS2013 Server is also a Farm Admin in SharePoint
No problems were encountered during installation of TFS 2013
TFS Server is used solely for TFS - nothing else is hosted here.
TFS Extensions For SharePoint have been installed on all servers in
the SharePoint 2013 Farm
TFS Server fully updated as of 1/17/2014
workstation fully updated as of 1/17/2014
Details on what I have attempted/researched so far:
Confirmed with my networking staff that there are no firewall\blocked ports
issues between TFS Server and SharePoint Servers
For the time period in which I was trying to create the new team
project there are no errors\warnings in the event viewer on my local
machine, SharePoint servers, or the TFS Server
When running Fiddler on the TFS server while trying to create the new
Team Project - I am seeing no traffic at all between the TFS server
and the SharePoint server.
my workstation has no open connections to any of the servers in question when trying to create the Team project
Cleared cache on my workstation at: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\4.0\Cache and C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\5.0\Cache
Verified nothing in cache on TFS Server at: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v12.0
Performed IIS reset on TFS Server
Re-start on TFS Server
Team Foundation Server Best Practices Analyzer (it says "SharePoint products is not installed", I'm suspecting this is because SharePoint is installed on another server)
Installed Visual Studio 2013 Update 1.
I apologize if this is in bad form but I have also posted this on the msdn forum: http://social.msdn.microsoft.com/Forums/vstudio/en-US/0758f52d-bf03-44e4-96aa-b60468395914/tf218017-cannot-create-sharepoint-2013-site-from-tfs-2013?forum=tfsgeneral
I am reaching the bounds of my skill set on this one. Any help\ideas would be greatly appreciated. Thanks!
Update:
Well, unfortunately I had to break down and call tech support from an un-named large tech company for assistance on this. Some changes were made to our SharePoint environment in the process which coincided with the SharePoint farm "going down". I am not sure if the problem on the farm was a coincidence or related to my changes but the end result is that my SharePoint people are now skeptical of my TFS integration etc... so I was forced to do a default install of SharePoint on the TFS box. I will leave this post up for others with similar issues to discuss unless that is in bad form. Thanks to all who tried to help with this.
Here are some additional items I would check:
Make sure you start VS 2013 elevated (Right-click when opening and choose 'Run As Administrator') when creating a team project.
If possible, see what happens if you try from a different computer or the server itself using Team Explorer.
Ensure that the user that you are attempting to create the team project with has enough permissions in SharePoint (you can make the account a site collection admin on the site collection in question).
The user should be a TFS Server Administrator or Team Project Collection Administrator.
Make sure that user account has Content Manager rights in the related Reporting Services folder as well, just in case.
Go to the your SharePoint site collection and attempt to create a site in it manually as the account that you are trying to create the Team Project with; when you perform this, make sure you create it with one of the team site templates that TFS installed (like the Agile or CMMI); If you encounter errors this way it may help you narrow down the problem.
Don't forget to review the event logs on the machines involved.
Okay, I finally go to take another crack at this against my SharePoint enterprise environment and got it to work: The key was to simply remove Anonymous Authentication from the SharePoint web application and it worked!
Access the SharePoint web site collection (for example server/site/DefaultCollection) and add your user or group on Site Collection Administrator.
I have a couple of reports that are sitting on a Sharepoint site that I need to make available to users outside of the organisation that I'm working in. So they will need to login in a .com portal etc to view these reports. at the moment we only have the Sharepoint reporting services running.
How I'm looking for the easiest way to achieve this. Could be depoly the reports needed on native mode server and have the native portal front end accesible for appropriate users, or should we be looking to build a tailored frontend to pull the specified reports directly from their sharepoint location.
any recomendations be greatly appreciated
mark
So, my client wants a customer dashboard integrating all information related to a project in a common sharepoint site.
So we have something like this
http://tdg-srv-006/ <------- Sharepoint site (SP)
http://tdg-srv-006/PWA/ <--- Project Web Access site (PWA)
http://tdg-srv-tfs2/ <------ Team foundation Server (TFS)
He wants the following requirements:
Burn down Chart: this one is located in the TFS server inside the company.
Total count of bugs: this one is located in TFS too
Open Issues and Risks: This one is located in PWA
Team names and roles: this one in TFS.
My question is, how do I communicate Sharepoint with TFS database and with PWA information? any comments, suggestions or clues?
There are two ways to do this. Use the project dashboard site created from Project Server, or the one created by Team Foundation Server.
Project Server
The standard way of setting up such a dashboard with Project Server is to enable project workspaces. This means that when a project is first published it would have a URL such as http://tdg-srv-006/PWA/My%20Project. This is where the project 'dashboard' site will reside, containing both your integration with Project Server and with TFS.
These workspaces are created from templates. They can be extended with your own design and web parts so they will always be created exactly as you'd like. For example, integration with Reporting Services reports that query the Project Server reporting database or Team Foundation Server is a popular idea.
Note that project workspaces already come out of the box with risks and issues. (These can also be linked to tasks and other risks and issues for a richer experience.)
For aggregation, within Project Web Access it is possible to create a view which sums the risks and issues from across all project workspaces and displays them in Project Center. When connecting to PWA, users are also prompted with the risks and issues outstanding that are assigned to them.
Team Foundation Server
Team Foundation Server also creates its own SharePoint site which you may prefer to use. This article on SharePoint Magazine should give you all you need to know. Again, you can set up Reporting Services reports that point to a TFS data source and display the results in your workspace. It just depends on whether you prefer to start with a TFS workspace or a Project Server workspace.
Caution
Both Project Server and TFS only install the free Windows SharePoint Services (WSS) by default. This means functionality such as the content query web part provided in SharePoint 2007 (MOSS) is not there. You can add SharePoint 2007 without any issues but it will cost you more.
The template approach that Project Server uses to create workspaces (and perhaps TFS as well) has problems. Firstly, Project Server will allow you to change columns and fields on the Risks and Issues lists but this will cause errors. There is a safe method outlined in the link earlier on my blog. Secondly, assuming you decide to change the template you will need to programmatically update every workspace within Project Server, including the template to make the changes. Not a big deal but a hassle nonetheless.
Other integration
Finally add the Project Server / Team Foundation Server connector into the mix. This will ensure work item data in TFS is kept in sync with project plan data in Project Server. Note that it has nothing to do with creating a dashboard/workspace.
I'm creating a PerformancePoint (henceforth PP) Dashboard that contains a web report to be deployed to the a SharePoint web application that I had created. I followed the instruction in the link below.
Deploy a PerformancePoint dashboard to a SharePoint site
In summary, following the instructions in the link, I published the Dashboard to the PP site. Then, I added my account in PP as Creator in the Application level, Editor in both the Dashboard and the Web Report. In the SharePoint site, I added my account under Contributor. I even added the PerformancePointDefault.master just to be sure.
Now, when I deploy my Dashboard to a Report Library, I was able deploy the folder for the Dashboard, but not the Dashboard Page file.
I googled for this, but I could not find any article helpful.
UPDATE 2009-09-30:
I was able to resolve the issue by creating another site collection. Maybe the first site collection is messed up.
I had the EXACT same problem. I was about to take the best advice I could find and delete my site collection and create a new one from scratch, but by the grace of God, I had one final thought.
In our case, the site created was originally http://ServerName but we later added a host header (i.e. http://BiSite). I had been deploying the dashboard using the host header the entire time, so I decided to try using the original name of the site using the server name and viola, the dashboard finally deployed correctly, pages and all.
When you publish a dashboard in MOSS, you have to make sure that you select Publish a Major Version in the dashboard page's drop-down in the report library.
Why is this a community wiki? Seems like there should be a right answer to this question...