When I was at a customer last week, I had a situation that SharePoint Foundation 2010 was installed as a local instance on the TFS application tier. The TFS extensions for SharePoint were already installed using the TFS installation. Now the SharePoint Foundation 2010 instance had to be changed to a farm installation. So the SharePoint Content and Configuration databases had to be located on a data tier (SQL Server 2008 R2). After the re-install of SharePoint Foundation 2010 in a farm mode, the TFS extensions for SharePoint had to be installed again.
When I went to the Team Foundation Administration Console, the ‘Extensions for SharePoint Products’ were still there (as it was previously connected to our local SharePoint Foundation 2010 instance). The problem was that the TFS extensions were not available anymore on our new SharePoint instance. When I click on the ‘Extensions for SharePoint products’, I got the error:
“TF249063: The following Web service is not available: http://abc:17012/_vti_bin/TeamFoundationIntegrationService.asmx. This Web service is used for the Team Foundation Server Extensions for SharePoint Products”
That’s correct, that TFS integration service asmx was not available anymore. The first thing I did was an un-install from the extensions (using the TFS installation media). Then I did a re-install of the extensions, but without any result. I hoped those steps could solve my problem, but they didn’t.. Time for the next step.
stsadm to the rescue
To resolve the issue, you have to install the TFS extensions manually to the SharePoint solutions store, and then deploy them. To do this, you need the stsadm tool from SharePoint. That’s the command-line administration tool from SharePoint. You have to add 3 .wsp files to your SharePoint farm.
- Go to the directory: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin\
- Open a command window (Shift + right-click -> Open Command Window here)
- Be sure that you run the command window with a user who has the right credentials (SharePoint Farm Administrator and have rights to the Central Admin Content Database on SQL server)
- Run the following commands:
- stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\Microsoft.TeamFoundation.SharePoint.wsp”
- stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\ TswaWebPartCollection.wsp”
- stsadm -o addsolution -filename “C:\Program Files\Microsoft Team Foundation Server 2010\Tools\Templates\Microsoft.TeamFoundation.SharePoint.Dashboards.wsp”
- Open your SharePoint Central Administration (http://server:17012 or something equal)
- Go to system settings and click ‘Manage farm solutions’
- You should see the 3 TFS wsp files
- Click on the first one, and click ‘Deploy Solution’
- Deploy the solution by clicking ‘Ok’
- When you deployed the 3 solutions, you should see
- All you have to do now is grant access for your TFS instance to SharePoint using the TFS Administration console.
That did the trick for me. Thanks for reading!
I couldn’t get the SharePoint Extensions Config Wizard to pass the Readiness Checks before I did this manually.
Implemented on TFS 2013 / SP 2013
Thanks, you saved my day 🙂