Skip to main content

Error while activating feature - SharePoint 2010






Hi all,
While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily.

Error:
Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope.








Solutions:
I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :(

I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you about the exact error.


-Vighnesh Bendre

Labels:

Comments

Unknown said…
Hi,

I have the same problem but copied and pasted the ID in the Features.xml didnt solve the issue...
February 1, 2011 at 1:56 AM
Vighnesh said…
Hi Alex,
You have to paste the id in the template.xml file. Please cross check once again. It should work.

All the best.
February 2, 2011 at 12:06 PM
Gaurav Gat said…
HI,
Thanks it's working fine for me now.
February 2, 2011 at 5:38 PM
Rupesh Tarwade said…
Does this require Scope to be mentioned??

My template.xml looks like this

Feature Id="7b100902-1522-4da5-9b2e-b8403ca65e01" xmlns="httpXXXXXXXXXXXXXX"

I still get the same error.
February 23, 2011 at 1:18 PM
DFelix said…
I followed your steps, but found the same ID found in Feature.feature1 file in Feature1.Template.xml file too. So replacing it doesn,t make any sense. Kindly advice.
April 12, 2011 at 12:41 PM
Samuel said…
I encountered a similar issue after developing and attempting to deploy a webpart solution...

I found that the solution had deployed, but never activated.

To resolve, I browsed to the Central Administrator webpage > System settings > Manage Farm Solutions - found that the solutions had been added but not deployed.
I clicked on deploy solution (and chose the website that want the solution to be available on).

I then went to the website and activated the solution and added it as a webpart to my page.

hope this help.

--samuel
May 26, 2011 at 4:42 PM
KansasCoder said…
Samuel Thanks for sharing your experience. I checked our Farm Solutions and discovered it had been deployed...odd though. it owuld be nice to find a solution as to why this happened. I wonder if the folks having this situation aren't fully patched on SP2010 or VS2010...maybe?
October 7, 2011 at 7:02 AM
KansasCoder said…
This is also happening when trying to deploy a list definition! Curious that this such a hard bug to squash!
April 18, 2012 at 6:57 AM
Unknown said…
"I encountered a similar issue after developing and attempting to deploy a webpart solution...

I found that the solution had deployed, but never activated.

To resolve, I browsed to the Central Administrator webpage > System settings > Manage Farm Solutions - found that the solutions had been added but not deployed.
I clicked on deploy solution (and chose the website that want the solution to be available on).

I then went to the website and activated the solution and added it as a webpart to my page.

hope this help.
"
Samuel
You answer saved us good time after spending the whole day searching solution.
February 22, 2017 at 9:18 PM
usman said…
there is no feature id tag in my template.xml file???
March 4, 2020 at 5:30 PM
Post a Comment

Popular posts from this blog

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...
3 comments
Read more

Custom People Picker (Editor) in SharePoint 2010

[Modified:11 Oct 2010] Now you can find the source code for this example in CodePlex The out-of-the-box SharePoint people picker allows users to select users, SharePoint groups, Distribution Lists & Security groups . Users may accidentally add large AD groups to SharePoint groups and send notifications to hundreds of people. The administrator may want more control over the security of the people picker control. In some scenario the administrator may want to restrict the user to only select ‘users’ or ‘SharePoint Groups’. This can be achieved by creating a custom people picker control which inherits from SharePoint people editor. In below example, we are going to explore creation of custom people picker control, replace the OOTB people editor control, provide a people picker settings page in central administration and create menu to access the settings page in Central Administration. 1. Create custom people picker For creating a custom control (which inherits from SharePoint PeopleE...
4 comments
Read more