Tag Info

New answers tagged

0

Try to access the direct link like changing the value of ctype= with the right value of your content type. server:port/yoursite/_layouts/ManageContentType.aspx?ctype=0x010082D2F7E6BD173D4DA0CF8C68A9EEA477 Check in advanced settings if the content type es marked as read only and change it back to non read only. Then you can delete it.


1

Looks like it is a DLL caching issue. When you start Powershell command line window, it loads all DLLs available in the GAC. So, if you have updated DLL for the feature receiver, and deploying it within the same PS session then it will not reload updated DLL. I had experienced similar behaviour before. To tackle it, I created two seperate PS1 files. First ...


0

This error usually occurs when you deploy a feature to a multi server as it cannot activate the solution. The quickest way it to build the solution in vs 2013 and install manually with powershell - this is the same for SP2010 ...


1

In this scenario you can actually use the -force attribute on Enable-SPFeature, since it will reenable the feature. But I normally uses your approach, but I use the ID of the feature and not the actual $Feature object: $FeatureId = $Feature.Id Disable-SPFeature $FeatureId -URL $oneweb.URL -Confirm:$False Enable-SPFeature -$FeatureId -URL $oneweb.URL ...


2

There are two ways, one is powershell and other is 3rd party(codeplex) solution as Malin Mentioned. Using the powershell script, check this link CodePlex solution SharePoint Feature Administration and Clean Up Tool How to remove Feature from site?


3

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.



Top 50 recent answers are included