I recently upgraded from Team Foundation Server 2010 to Team Foundation Server 2012, after the database was restored and the Team Foundation Server 2012 was running on the new machine, i recognized that my new TFS 2012 is linking to my old TFS 2010 Sharepoint, so i installed the Extensions for Sharepoint on my new machine and Linked the TFS 2012 with the new Sharepoint.
To be sure that it doesnt link to my old machine, i shut it down. So my new Sharepoint is reachable on tfs:8080/tfs but I can't add a Team Project, and if I want to add a new collection, it adds it on tfs:8080/sites/DefaultCollection.
On adding a new Team Project to a upgraded Project, i get following Error Messages:
TF218017,TF250044
To upgrade I used http://blog.damianbrady.com.au/2012/06/03/upgrading-tfs2010-tfs2012-rc-done/
Does anyone know how I'm able to configure the Sharepoint site on tfs:8080/tfs?
Thanks for your help!
Those specific errors occur when the user who is creating the TFS Team Project does not have the appropriate permissions on that SharePoint site collection to create sites. Add the user who is trying to create Team Projects as a Site Collection Administrator on the Site Collection you are using for TFS.
Related
in my setup each project in tfs 2015 has own project portal. But group permissions are different in tfs and sharepoint. Is there some approaches to synchronize them?
There isn`t standard tools to synchronize users and permissions between TFS and SharePoint. I think you may try to use next ways:
Common active directory groups. Create separate group for readers and contributors (for each project), add them to SP and TFS. Then add and remove users from these groups.
Use Team Foundation Server Administration Tool as centralized tool. This tools was created for TFS 2013. But TFS 2015 supports TFS 2013 object model. You have to (on your local workplace) install Team Foundation Server 2013 object model, download archive, rename last release to TFS AdministrationTool.zip and install it.
I have TFS 2015 Update 3 configured with SharePoint 2013 integration. I am planning to upgrade to TFS 2018 in new hardware, which does not support SharePoint integration.
According to MS documents I should upgrade and disable the SharePoint integration post upgrade.
In my case I am upgrading and moving to new hardware at the same time. When I am moving to a new set of hardware, I do not want to bring the OLD SharePoint along.
So before even upgrading to TFS 2018 I want to decouple SharePoint sites from the existing TFS 2015 Update 3 configuration.
Is there a way to achieve this? or my approach is wrong?
If you don't need SharePoint anymore, you could remove SharePoint extension in your TFS 2015 by going to TFS Administration Console, click SharePoint Web Applications, click Modify against your server connection and choose Remove.
If you still need TFS SharePoint sites, you should follow the document you mentioned to disable SharePoint integration.
It's suggested have a full backup of your database, and do a dryrun upgrade before using in production environment.
We upgraded a site from TFS 2010 to TFS 2017 to new infrastructure including the TFS, SQL, SharePoint and Reporting Services.
Everything is working ok except for old SharePoint portal sites.
They initially appeared to be working but were in fact being redirected to the old Reporting Services site. We did tell TFS about the new SharePoint and Reporting using instructions here: https://msdn.microsoft.com/en-us/library/dd386320(VS.100).aspx
However, that still didn't resolve. So we tried to add &tf:ClearCache=1 to the TFSRedirect URL thinking that maybe it was caching the old URI. However, now whenever we try to access that portal all the webparts are broken and when we try to access anything with a TFSRedirect it gives an error.
Error=TF250008: This SharePoint site is not currently associated with a team project in Team Foundation Server. However, we have done what we thought was requried (URL above). What are we missing?
Looking at this for setting up SharePoint extension for TFS 2015:
https://www.visualstudio.com/zh-tw/docs/setup-admin/tfs/install/sharepoint/setup-remote-sharepoint
I have remote SharePoint servers. I'm just looking to update the extension installed from the TFS 2013 version to the TFS 2015 version.
It mentions the following, but I can't find the EXE:
Tip:
If you don't want to install all of Team Foundation Server on the server that is running SharePoint Products, launch the tfs_sharePointExtensions.exe file from the SharePoint Extensions folder to install only the Team Foundation Server Extensions for SharePoint Products.
Really don't want to install the Full TFS Admin console if I can just install the extension alone.
This is not work with TFS2015 any more.
With TFS 2015 the installation media no longer includes the
SharePoint installation bits nor a separate
tfs_sharePointExtensions.exe installer.
To integrate your Team Foundation Server with SharePoint, you must
run the Team Foundation Server installer on the SharePoint server and then configure TFS Extensions for SharePoint. The integration
process itself remains the same.
More details you can refer the Scenario 2: [TFS integrated with remote SharePoint Server.] in this blog Team Foundation Server (TFS) 2015 – SP integration.
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.