Hot answers tagged

59

I have had this problem, too. The reason why they don't show up in PowerShell is the missing Scope, those feature are orphaned, indeed. We cannot use -Site parameter. What you can is to list it in PowerShell without -Site parameter and filter out those without Scope: Get-SPFeature | ? { $_.Scope -eq $null } This will give you a complete list of orphaned ...


52

Welcome to SharePoint Stack Exchange! In your Visual Studio 2012 SP Solution: Enable Always Force Install to True in for your feature. See example below: By default, it is set to False. You can configure that to be set to True.


14

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 have two web applications, A and B on the same SharePoint farm. You want to deploy solution S which contains a visual web part to web application B, but it is ...


13

You can do it via the XML editor as well! Steps: Go to your Features in your project. Open the feature.template.xml file add AlwaysForceInstall="TRUE" to the below tag <Feature xmlns="http://schemas.microsoft.com/sharepoint/" AlwaysForceInstall="TRUE"> Now try to deploy the code.


8

within your solution click on feature.feature and goto its properties, you should now see somthing on the lines of Always Force Install just set that to true and you dont need to do the force attribute anymore! looks like a feature wasnt retracted properly and has become a phantom! ybs has a similar issue here! Visual studio Both site collections ...


8

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, resources, etc. One .wsp package can contain multiple features Feature id is identity of particular single feature which is web/site/web application/farm scoped ...


7

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


7

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 - files to the other hostdir folders then the solution must be installed to specific web application(s) by either specifying web applications like: Install-...


7

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 classes for the event receivers (both inheriting from SPItemEventReceiver) Add a feature event receiver on the feature (inheriting from SPFeatureReceiver) In the ...


6

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 with the path of the wsp file you just added to deploy, it should also deploy itself after the update. Update-SPSolution -Identity "name wsp" -LiteralPath "path ...


6

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 after that check this link for another possible cause


5

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 can use the powershell to get this done. http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html


4

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 { /// <summary> /// Ensure SPFolder /// </summary> /// <param name="web"></param> /// <param name="listTitle"></param> ...


4

make sure the solution deployment job was finished before you activate the feature. have a look at this blog: Programmatically waiting on SharePoint Solutions to deploy


4

Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms. However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.


4

function Deactivate-SPFeature { param ($FeatureID, $SiteUrl, $WebApplicationUrl) $Feature = Get-SPFeature -Identity $FeatureID -ErrorAction SilentlyContinue $IsActiveFeature If ($Feature -eq $null) { Write-Warning "The specified feature ($FeatureID) was not found." return } If ($Feature.Scope -eq [Microsoft....


4

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 occurred features through it.


4

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.Parent; foreach (SPJobDefinition job in webApp.JobDefinitions){ if (job.Name == List_JOB_NAME) job.Delete(); }


4

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 changes in package file. Retract and remove your solution then add and install your solution. Remember if new feature added then you have to retract and add the ...


4

Make the feature scope in Visual Studios be "Site" instead of "Web". https://msdn.microsoft.com/en-us/library/ee231541.aspx


3

An easy way would probably be to create a timerjob which: Iterate through your webs and find Doc Libraries with specific name. Iterate through the documents to find an column with expired date, use lambda. Mail targeted groups/users for the specified document. As long as the timerjob doesnt run all the time you can minimize the workload.


3

Double click on the feature.... then in the properties window make ALWAYS FORCE INSTALL = true... and there u go.....


3

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 with -Force. Hope this will be helpful.


3

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 be found in View Source of page.


3

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 deleted properly. this feature will not be listed in your powershell also when you try to search which features are available in your farm. So better way to ...


3

Feature stappling simply means having a list of features to activate everytime a certain site definition is used (or in natural language stating "Do activate these features when any of the Site definition ID is created"). Basically there is always a Stappler (the actual feature linking one or more site definion ID with the actual features) and a Staplee (...


3

Technical Details Feature stapling is implemented through a Feature that is specifically designed to staple other Features to one or more site definitions. Feature stapling allows a Feature to be stapled to any new sites created from any site definition or from specific site definitions based on the template name identified in the appropriate WEBTEMP.xml ...


3

You can use feature stapling to achieve this. You just deploy a simple element file in a feature and activate it at the web application level. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <FeatureSiteTemplateAssociation Id="the guid of the feature to staple to new sites" TemplateName="...


3

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 in features that have an event receiver. I fixed it by including the BDC module in one feature, and then creating an empty feature with an event receiver with ...


3

If I remember correctly the flow is: Site Collection Scoped Features Web Scoped Features Lists Modules Your stapled features would be shot in after Site collection scoped features or Web scoped features (depending on scope) and hence the lists is not guaranteed to be created before the lists. Found a source here: http://blogs.msdn.com/b/chrischiaro/...


Only top voted, non community-wiki answers of a minimum length are eligible