15
votes
Feature has already been installed. Use the force attribute to explicitly re-install the feature
This error happens if you deploy a solution which contains a visual web part to a different web application on the same farm as the web application where it is already installed. In other words, you ...
- 2,082
8
votes
Accepted
Difference between Feature ID and Solution ID
Solution id is identity of Solution package (.wsp file). If you are deploying wsp file, it will check solution id. If exists, it will update solution.
Solution contains all the features, assembly, ...
- 1,659
7
votes
Accepted
SharePoint feature deployment and scope via PowerShell
No, the solution dictates if it's global or per web application.
WebApp Scope
If the solution contains resources that's web application specific like:
- Dll deployed to bin
- Dll with SafeControls
- ...
- 32.4k
7
votes
How to remove orphaned features
To my surprise this worked for me:
stsadm -o uninstallfeature -id <id-of-feature-missing> -force
Found in this blog post Sharing Minds - by Anthony Butcher
- 181
7
votes
Accepted
Deploy/bind event receivers to lists in single feature
Your plan is good, and respects good practices (at least the practices I've been following for ages).
Your approach is to:
Create the solution in VS
Create one feature (scope: Web)
Create two ...
- 9,686
6
votes
Feature has already been installed. Use the force attribute to explicitly re-install the feature
A better way to solve this without adding force is after the error happens, just leave the wsp there with the error in CA, open the SharePoint Management Shell and use the update-SPSolution command ...
- 61
6
votes
Accepted
What features do I have to activate to get Content search web part (CSWP)
This webpart requires Enterprise features to be enabled in your environment. If this is not enabled the webpart will not be available.
Here's a guide on how to do that
If you still have problems ...
- 24.6k
5
votes
Accepted
How can I identify missing features in a SharePoint site that has been restored from a different farm?
there are couple of ways.
Run the Test-spcontentDatabase command against the content DB to get the list
use this SharePoint Feature Administration and Clean Up Tool to identify and remove them
You ...
- 56.7k
4
votes
When I create a folder programmatically get the error "Invalid item data -- missing FileRef"
Yet another version how to create a folder including nested folders using SharePoint SSOM.
How to create nested Folder using SharePoint SSOM
internal static class SPFolderExtensions
{
/// <...
- 42.1k
4
votes
Accepted
Sharepoint is keeping a record of un-installed solutions
I have faced the same situation many times. I used a tool called Feature Admin. It shows any features that are isolated and cannot be used including error occured. You can delete the unwanted or error ...
- 2,392
4
votes
Accepted
Error when activating feature that installs a timer job
I guess your mistake is that SPSite is not the properties.Feature.Parent when your Feature has Scope Webapplication. Try this instead:
SPWebApplication webApp = (SPWebApplication)properties.Feature....
- 1,224
4
votes
Accepted
Feature is not displaying
If it's a newly added feature you have created then how you deployed your solution. I had also faced same problem.
If you have updated your solution than it probably not be there. because there are ...
- 86
4
votes
Accepted
How to move a feature from "Manage Site Features" to "Site Collection Features"
Make the feature scope in Visual Studios be "Site" instead of "Web".
https://msdn.microsoft.com/en-us/library/ee231541.aspx
- 12.2k
3
votes
Accepted
Proper method of localizing aspx pages
In the SharePoint projects I have worked on I have used a few different ways to localize page content. I think the simplest way for you will be with an EncodedLiteral:
<SharePoint:EncodedLiteral ...
- 11.9k
3
votes
Accepted
How do you decide the scope of a feature when creating timer job?
As a TimerJob has to be associated with either a WebApplication or Service, the most scope of the feature would be common would be either WebApplication or Farm.
But as always with scoping features ...
- 32.4k
3
votes
"Feature has conflicting event reciever settings" error
I had this problem. I was including the BDC module inside a feature that had an event receiver. It seems that the BDC module references its own event receiver and this means that it can't be included ...
- 182
3
votes
Feature has already been installed. Use the force attribute to explicitly re-install the feature
I had this same issue and found that it was because of Orphaned Feature.
There are chances that whenever you remove wsp from farm and redeploy it, then Feature associated with that wsp might not got ...
- 125
3
votes
How to remove orphaned features
You can try this and second Reference, this one I have refered fist time.
For this you need the add the Feature Id and then -Force is important.
Without force it works sometimes but definitely works ...
- 2,444
3
votes
How to remove orphaned features
I used following command to remove feature from Site Collection Administration : Features interface
stsadm -o uninstallfeature -id <GUID> -force
GUID of feature (which you want to remove) can ...
- 39
3
votes
How to remove Feature from site?
There are couple of ways to remove it.
Using Powershell
First, using this Powershell script by Phil Childs:
To use the script, run these functions in a PowerShell console with the SharePoint 2010 ...
- 56.7k
3
votes
How to remove Feature from site?
What you are seeing are references in your database after a solution/webpart that was not removed correctly.
I assume that you just uninstalled and removed the solution? If you know in which site och ...
- 9,501
3
votes
Accepted
Programatically identifing feature for activation
Well. It really depends on which feature you have to activate.
The id of a feature does not change during its life. This means that if you can find out the id you will be sure it stays the same, ...
- 6,854
3
votes
Accepted
Active then deactivate "SharePoint Server Publishing Infrastructure" inside my team site
This is by design. SharePoint will not remove those libraries.
You can manually remove those and it will not cause any problems.
Later if you activate the Publishing feature will create those if it ...
- 28.2k
3
votes
Accepted
List creation on installation NOT activation for a feature?
No if you use List Definition with List Instance element, you can set the list instance property Deployment Conflict Resolution=None and your list instance will not be deployed (or not replaced with a ...
- 14.5k
3
votes
Accepted
2013 - feature upgrade - add or modify Content Type
You cannot update existing Content Type (or list) definitions by installing updated feature that contains updated definitions. You need to add custom code that is run when feature is activated and ...
- 8,197
3
votes
Accepted
Error Importing Site using PowerShell
You can use PowerShell to identify the feature.
Get-SPFeature | Where-Object { $_.DisplayName -like "Excel*" }
You can disable feature using
Disable-SPFeature –identity "ExcelServerEdit" -URL http:/...
- 28.2k
3
votes
Accepted
Provisioning MySite with feature that creates library with content type from CT hub
I found the solution. Forgot to publish the content type and run the timer job (content type hub & subscriber). After that everything worked!
I don't have to run the timerjobs in the feature (...
- 2,250
3
votes
Accepted
Cannot resolve symbol 'GetFile'
You might be using a wrong 'Web' object. It shouldn't be System.Web or Microsoft.Web. It should be from Microsoft.SharePoint.SPWeb namespace. So first of all you need to get an 'SPWeb' object from '...
- 3,798
3
votes
Can I extract a Solution (WSP File) from my site level?
you can use the following powershell
$farm = Get-SPFarm
$wsp = $farm.Solutions.Item("customsolution.wsp").SolutionFile
$wsp.SaveAs("c:\temp\customsolution.wsp")
- 1,787
3
votes
Feature is not displaying
If you update a WSP package that contains a new feature, you have to install the feature. This can be done by PowerShell right after the solution update with:
Install-SPFeature -path "<...
- 9,686
Only top scored, non community-wiki answers of a minimum length are eligible