6

I am creating and deploying Visual Web Part on SharePoint 2013 with VS 2013 as Farm Solution.

When deploying Web Part on the server i get the following error:

Error occurred in deployment step 'Activate Features': Feature with Id '8a442317-1158-4994-b265-26499b2def57' is not installed in this farm, and cannot be added to this scope.

Help.!!

Thanks in advance.:)

| improve this question | |
3

When you use Visual Studio to build your visual web part. In the Feature Design mode we you gave the scope of feature as Farm by mistake and when we try to deploy the solution you will get the error message.

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

The resolution is pretty straight forward just the change the scope of the feature in Feature design window as "Web".

If it is multi server farm, check following:

http://blogs.msdn.com/b/calvarro/archive/2011/11/06/sharepoint-2010-amp-visual-studio-2010-error-ocurred-activate-features-feature-with-id-installed-in-this-farm-cannot-be-added-to-this-scope.aspx

| improve this answer | |
  • Tried before...still it give following error: The Project Item "VisualWebPart1" cannot be deployed through a Feature with Web scope. – Pranav Bilurkar Oct 10 '14 at 6:22
  • Change it to site. – Aanchal Oct 10 '14 at 6:23
  • done...now error is: Error occurred in deployment step 'Activate Features': Feature with Id '8a442317-1158-4994-b265-26499b2def57' is not installed in this farm, and cannot be added to this scope. – Pranav Bilurkar Oct 10 '14 at 6:25
  • Are you using farm solution or sandbox? – Aanchal Oct 10 '14 at 6:26
  • farm solution.. – Pranav Bilurkar Oct 10 '14 at 6:26
0

Deploy it using Powershell

 Install-SPSolution -Identity MySolution.wsp -local -GACDeployment

or

Install-SPSolution –Identity MySolution.wsp -GACDeployment
| improve this answer | |
  • Error: This solution contains resources scoped for a Web application and must be deployed to one or more Web applications. – Pranav Bilurkar Oct 10 '14 at 8:52
0

Check the scope of the Feature. It should be scoped to Site. Since, the project contains visual webpart, you need to specify webapplication paramter if deploying through PowerShell

Add-spsolution -LiteralPath c:\WSPNAME.wsp

install-spsolution -identity WSPNAME.wsp -gacdeployment -webapplication http://aissp2013
| improve this answer | |
0

Check, that package.package has the correct office/sharepoint version, e.g. SP2016 16.0, SP2013 15.0. It's hardly noticeable but that could be the reason why the feature doesn't get installed into the sharepoint in the first place. Developing for multiple Sharepoint Versions on many dev machines with different VS and Office Dev Tools and cloning projects can lead to this mess.

VS Screenshot SP package

| improve this answer | |
0

On the project's Properties window, in the SharePoint tab select "No Activation" as Active Deployment Configuration.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.