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

Create list view - Conditional Formatting in SharePoint Designer 2010

In this example, we are going to format a column based on certain condition. Here I already have a list called Projects. I also have workflow associated with it. So whenever I create a new item in the list, workflow status column shows ‘In Progress’. Subsequently when the workflow in completed, the workflow status column shows ‘Completed’. For demonstration purpose, I will set the background color of workflow status column to yellow when the status is ‘In Progress’ and to green when the status is ‘Completed’. In SharePoint Designer open the site on which you are working. Click on ‘Lists and Libraries’ link. Choose the ‘Projects’ list. In SharePoint Designer Navigation, choose ‘Lists and Libraries’. In the list settings page, click on ‘New’ in ‘Views’ section. Provide appropriate name for the view and click OK. After choosing list, click on ‘New’ in the Views section. Give appropriate name to the list. Now click on any column, then in the ribbon, click on List View Tools-&g
1 comment
Read more

Upgrade and Migration for SharePoint Foundation 2010

      1.1 Introduction Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements. There are 3 major steps while upgrading. 1. Plan and Prepare 2. Perform a database attach upgrade 3. Verify upgrade 1.2 Plan and Prepare   Before we run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, we have to determine which upgrade approach to take. In our scenario, Database Attach Upgrade seems to be appropriate approach to follow. We can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users. 1.2.1 Upgrade Approach A database attach upgrade enables you to move to new hardware or a
4 comments
Read more