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.


17

You need to populate the gallery if web part is not appearing in the web part gallery. For that go to site setting(I use 2013) site gallery, click on web parts link There clicking on new documents, you will get all the web parts installed. Check the box along the web part name and click on populate button on the top. That should work, I hope.


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 ...


10

As a short answer: No You can't add two different versions of the same solution name in the same environment. Workarounds You have 2 workarounds Redploy the same solution with a different name. In UAT and Production farms, Try to do the following: Back up the current solution as mentioned here. Retract and remove the old version using PowerShell. ...


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 ...


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-...


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

The workaround is as follows: Open up your SharePoint 2012 solution in Visual Studio 2012/2013 In the Solution Explorer (use View -> Solution Explorer if you don't see it) expand your solution and browse to the Package within your project Double click on the Package.package entry to open up the package editor Click on the Advanced Tab The Additional ...


6

Here is the PowerShell code to create a webpart page: Add-PsSnapin Microsoft.SharePoint.PowerShell $pageTitle = "Page Name" $layoutTemplate = 4 # Template code $web = Get-SPWeb http://server/site $list = $web.GetList("http://server/site/LibraryName/") $xml = "<?xml version=""1.0"" encoding=""UTF-8""?><Method ID=""0,NewWebPage""><SetList ...


5

Paul Liebrand posted a blog post which would do the magic in PowerShell. I assume you could modify the where/? part to fit your needs, like matching the solution id for example. Get-SPTimerJob | ? {$_.Name -like "Solution-Deployment*" } | % { $_.Delete() } I haven't got a chance to try this myself.


5

With the recent update to SharePoint Online you can deploy SharePoint Framework solutions and add-ins either globally in the tenant app catalog, which will make them available in all sites, or locally in a specific site collection app catalog. Site collection app catalogs are not enabled by default and tenant administrators have to explicitly enable them on ...


4

Yes, you can build and publish WSP without deploying solution.There is 'Publish' option in visual studio 2012, click on it & specify hard drive folder path to publish WSP. First bulid your solution then Right click on project in solution explorer-->Publish


4

Are there only 2 kinds of SharePoint Solutions? yes, but since SP 2013 we could count the APPs as a separate solution type as well Does the SharePoint Foundation Sandboxed Code Service" (SPUserCodeV4) have to be active ... yes On what server(s) should...Code Service" (SPUserCodeV4) be active? I would suggest on the front end "Save Site as ...


3

Try this code,it will donwload it from the site collection $spWeb = Get-SPWeb -Identity http://SPServer $listTemplate = [Microsoft.SharePoint.SPListTemplateType]::SolutionCatalog $solGallery = $spWeb.Site.GetCatalog($listTemplate) $solGallery.Items | ForEach-Object { if($_["Title"] -eq "the title of the solution") { [System.IO.FileStream]$outStream = ...


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

SP.Update() should work after you add the solution to the farm. var complete = false; while (!complete) { complete = SPFarm.Local.Solutions[“solutionName.wsp”] != null; if (!complete){ SPFarm.Local.Update(); Thread.Sleep(10000); } }


3

SharePoint's solution deployment is a bit of a black box. I would try two things: 1) Use -Force on the Install-SPSolution cmdlet to instruct SharePoint to override files, etc., and hopefully result in "Deployed". 2) If #1 doesn't work, I would retract and remove the solution. Then restart the SPAdminV4 and SPTimerV4 Windows Services. Then re-add the ...


3

I can't find a resource on this atm, but the main differences are: if your solutions contains dll's it will ask to deploy them to the gac. I've personally not deployed them to a specific web app's bin folder yet. if your solution contains webparts or other resources that require modifying the web app's web.config file, it will ask you what web application ...


3

You can put the specific term store name in the Site property bag and in the feature receiver fetch it from there.


3

This solved my problem: remove-spsolution -identity {name of wsp file.wsp} -force


3

Here is the line may help you: This does not seem to be a supported use case at the moment. It is possible with SharePoint Add-Ins, but not SPFx WebParts. You can find the complete thread Deployment to Developer Site is not possible


3

First, It's not possible to have 2 solutions with the same solution ID on the same farm. In your scenario, Unfortunately, you don't have SharePoint solution to open it with Visual Studio and change the Solution ID easily! Check also Difference between Feature ID and Solution ID So the available workaround is changing the Solution ID and rebuild the WSP ...


2

There is a more fail-safe approach than what @lwbecker2 suggests Get-SPSolution | ? { $_.JobExists } | % { Write-Host "Deployment job is currently running" } This has the benefit of not having a race condition. If you only look for the timer job, it may be that a deployment has already been initiated, but a timer job was not yet created when you check for ...


2

Hire a capable resource that knows sharepoint...


2

There are only a few instances where you get any real benefit from the CompatibilityLevel having both 14 and 15. If you have a solution where you are adding ghosted files to a site, you will get health analyzer warnings that the files don't exist in the 15 HIVE if you only deploy in 14 mode. Another instance is having site definitions for both 2010 and ...


2

Try doing a full retract on the solution. I'm assuming you are using Update-SPSolution when you are deploying. In the help to Update-SPSolution it states that "If files and features are different, the solution must be retracted and redeployed by using the Uninstall-SPSolution and Install-SPSolution cmdlets, respectively." p.s. This should maybe be a comment,...


2

Update your "new" server with the latest wsp-packages Create a new site collection, for testing purposes and restore your site collection there When you are done verifying everything is ok, backup the site collection you're restoring to. Everything will be overwritten when you restore. You can restore to both new or existing site collection. The effect will ...


2

You're right, usually that does the trick: Close Visual Studio; Run iisreset.exe /noforce on command line; Open Visual Studio again; Deploy every single project, one by one. If that fails, you can also try manually retracting the solution and redeploying afterwards.


2

Finally, I found an another solution for this critical problem. Cause we modified directly js or CSS or some files of Front End in the server SharePoint, "IIS" will keep the original files as web content cache, even we did Ctrl+F5 or empty the cache in browser, that doesn't work at all. I tested many times in that way. So we need Expire the web content in ...


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