Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. TFS 2010: SharePoint extensions configuration fails with error TF255481 or TF205021

TFS 2010: SharePoint extensions configuration fails with error TF255481 or TF205021

Symptoms

While configuring the SharePoint extensions on a MOSS 2007 instance, you hit an error:

TF255481: The following solution could not be upgraded in SharePoint Products: TswaWebPartCollection.wsp. The error is: Solution "tswawebpartcollection.wsp" is not deployed. To upgrade the solution in the configuration database, omit the -time, -immediate, and -local flags. To then deploy to the front end, use the deploy solution command.

Note: on a SharePoint 2010 instance, the configuration wizard throws the following message:

TF205021: A feature could not be activated in the following Web application: http://<server name>/. The feature is Tswa. This feature is part of the following solution: TswaWebPartCollection.wsp. Without this feature, project dashboards will not function correctly. Verify that the solution had been deployed to the SharePoint farm, and that the feature has been deployed in the SharePoint Central Administration.

↑ Back to the top

Cause

A .wsp file in SharePoint is the solution file. A solution file has a .CAB-based format but a .WSP extension. A solution is a deployable, reusable package that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually.

tswawebpartcollection.wsp is the solution file for "Team system Web access", This solution file has to be in deployed state inside SharePoint central administration, for the solution to function properly, but the solution file is not in the deployed state.

↑ Back to the top

Resolution

In MOSS 2007 and WSS 3.0:

Close the SharePoint extensions configuration wizard

1) Open IE as Administrator and Launch "SharePoint central administration" page

2) Browse to the "operations" tab, Select "Solution Management"

3) Along with other solutions you will find the TSWA solution named "tswawebpartcollection.wsp", the Status would show "not deployed"

4) Click on the file name, and on the next page select "Deploy Solution"

5) Select 'Now' for "deploy When?" and for the "Deploy to" section select the Web application that is hosting the TFS project portal. Click OK.

6) Once the solution is deployed, the list shows up as "deployed". Now run the SharePoint extensions from the TFS admin console on the SharePoint server.

In SharePoint 2010:

Close the SharePoint extensions configuration wizard

1) Open IE as administrator and launch the Central administration page

2) In central administration, select "System Settings" and under "Farm Management" select "Manage farm solutions" 

3) Along with other solutions you will find the TSWA solution named "tswawebpartcollection.wsp", the Status would show "not deployed"

4) Click on the fille name, and on the next page select "Deploy Solution"

5) Select 'Now' for "deploy When?" and for the "Deploy to" section select the Web application that is hosting the TFS project portal. Click OK.

6) Once the solution is deployed, the list shows up as "deployed". Now run the SharePoint extensions from the TFS admin console on the SharePoint server.

 

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2026072
Revision : 1
Created on : 1/8/2017
Published on : 4/28/2010
Exists online : False
Views : 280