Tag Info

New answers tagged

0

It doesn't matter. Once a solution is deployed, the timer job will propagate the changes to all other servers. That is the reason for packaging everything as a solution. One the other hand, people tend to make direct changes to server (by editing files etc.) those changes will never get propagated. Major steps to farm solution installation: Adding: A ...


0

This is two step Process: First you have to Add the solution into Farm stsadm.exe -o addsolution -filename yoursolutionpackage.wsp Second, You have to deploy it. stsadm -o deploysolution -name yoursolutionpackagename.wsp -url http://sp-mach/ -local -force Check this for more info: ...


0

stsadm -o addsolution -filename C:\solution.wsp This is from a farm level, so it applies to the entire farm, whether you have one server or 10 servers. There is a page in Central Admininstration -> Operations -> Solution Management that will tell you the deployment state of all the solutions in the farm and whether or not they were deployed to a specific ...


0

Setting Force attribute while installing a solution using PowerShell will help resolving this issue. That way, you don't need to manually uninstall features one by one. Example: install-spsolution -identity SOMEWSPNAME.wsp -force -gacdeployment -webapplication http://aissp2013


0

I found the feature ID in folder C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES There are 7 features for this solution. I use stsadm to uninstall all features, then I redeploy the solution: stsadm -o uninstallfeature -id "ID GUID" –force It works


0

Couple of things: Make Sure Admin Services is running on all server in farm. Can you see the Solution from Central Admin and try to remove it from their? try to install with force feature. Is it Gacdeployment. Worst case Scenario( not recommended in Production), Manually delete the DLL from the Gac and also feature from 14/15hive. I did only once in my ...


0

You may want to rephrase your question. I am not sure what your end goal is, but if it is to use a term set to navigate through your site, then watch this video: https://www.youtube.com/watch?v=7ICmKCSGS7M


0

My assumption about variable count limit was correct. You can have 50 variables per activity, in my case Sequence. More on conducted analysis: http://slavensemper.blogspot.com/2014/12/maximum-number-of-variables-per-activity.html


1

Well they should be same, specially when you are going to use Backup/Restore of site or Import/Export. If you are just going to prepare a WSP solution and use that in different environments, it should work but there maybe complications. Safe side, they should be same versions. You have two options: 1- Either you use External Content Types, External Lists ...


2

In SharePoint 2013, sites can be created either in SP 2010 mode or SP 2013 mode. So, SP 2010 compatible WSPs can be deployed to 14 hive by specifying the compatibility mode in SP 2013. Therefore a SP 2010 mode site will work properly. However, if the idea is to use SP 2013 based site, then the custom solutions should be upgraded. If you have VS 2012 or 2013 ...


0

I'm not entirely sure what you're asking, but I'm going to assume you are having trouble figuring out where the code you've pasted here is supposed to go. The link you've provided suggests that you add it to the Codebehind for the pagelayout.ASPX that you are creating. This link explains how to add a codebehind file to an ASPX page:


1

No, there is no way to deploy a solution to a particular site collection. A solution is deployed either Globally to all web applications or a single web application. It is the feature inside the solution which can be deployed to a farm/webapplication/site collection/web.


1

Usually you deploy your farm solution to web application, but you activate solution's feature(s) only on desired site collection.


1

The webpart is deployed as part of a feature. Activate the feature in new site collection and then the webpart will be available.



Top 50 recent answers are included