Tag Info

Hot answers tagged

3

Did a complete re-installation with the following power shell script to Configure the App Domain: net start spadminv4 net start sptimerv4 Set-SPAppDomain "<app domain name>" Get-SPServiceInstance | where{$_.GetType().Name -eq "AppManagementServiceInstance" -or $_.GetType().Name -eq "SPSubscriptionSettingsServiceInstance"} | Start-SPServiceInstance ...


3

The so-called "best practice" from MSoft is called "remote provisioning". This is basically using CSOM (or JSOM) to provision the site structure. Any environment that allows REST access and the proper permissions can be used to do this, including ConsoleApp, PowerShell, Javascript, provider-hosted app, et.al. I learned about this in the excellent MVA course ...


2

Go to the visual studio feature file and check whether you have all the webparts you needed in the feature. Else add them by selecting and send from left to right.


2

Make sure that your feature (in the VS solution) has all the web parts in it.


2

In a sandboxed solution cannot deploy files within the SharePoint root directory or any other location on the file system of the web server. That means you cannot deploy branding files to familiar locations that are commonly used in farm solutions, such as the IMAGES directory or the LAYOUTS directory. You must instead provision branding files, such as ...


2

After hours of trial and error I noticed that Fiddler was running on the server which is quite common when debugging workflows. When I closed Fiddler I was able to deploy WSP successfully. I was able to recreate this issue multiple times. For more details: http://slavensemper.blogspot.com/2014/08/error-occurred-in-deployment-step.html So, close Fiddler ...


2

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


2

Here are couple of points which can help you Find all custom Solutions - For this you can open Central Administration -> System Settings -> Solutions Now using PowerShell you can download those solutions from the Development Server $farm = Get-SPFarm $file = $farm.Solutions.Item("solutionname.wsp").SolutionFile ...


2

Can you try this: Go to Central administration -> Application Management-> Database -> Manage Content Database. Select the required web application and click on Add Content Database. Give the name to this database. Now restore the site collection to this database using Restore PowerShell Command: Restore-SPSite http://sitename/sites/site_name -Path ...


2

I think I had success with this by using the Overwrite=True attribute (https://msdn.microsoft.com/en-us/library/office/aa544268.aspx). Also I believe once the content type is in use in a list instance it might be blocked from being removed. Try deleting the instance and then clearing it from both the first stage and second stage recycle bin then ...


2

Here is the powershell command to deploy WSP to particular web application only : Install-SPSolution your_solution_name.wsp –webapplication http://server1:123 –GACDeployment


2

SharePoint solutions (non-sandboxed) can be deployed at both two scopes "Globally" and "Web Application". As stated by bloger Jan Steenbeek at Deploying solutions to a specific Web Application: "SharePoint has the annoying" (Debatably) "habit of forcing you to deploy globally whenever possible. When you try to deploy a global solution to a specific url ...


2

I'm also relatively new to SharePoint development, but will try share some of my experience. :) When I created new code/functionality to a site, I make sure that I 'deactivate' the webpart/feature, then under your Admin Settings I retract the solution from the farm. Before I package the solution in Visual Studio, I update both the .feature title and ...


1

My advice is do not use xml list templates. It will give you many headaches when you are upgrading the solutions, creating lookups and etc... I would suggest create a feature receiver and create the list in the feature activated event. With the C# code you get much flexibility and opportunities to change the things around without affecting the existing ...


1

I don't find any official documentation on that just now, but as far as I know it refers to the location within the SharePoint deployment package, that means within the .wsp file. If you open that file (for example, after changing the file extension to .cab), you can see its internal folder structure. This structure often (as long as the Type attribute of ...


1

Make sure Open the debug/release folder and make sure a WSP file is generated Open central admins -> system settings -> farm solutions. If a solution with the name exists, then retract and remove it. Check log files


1

I think Update-SPSolution should work. Update-SPSolution –Identity solution.wsp –LiteralPath “C:\solution.wsp” –GacDeployment An IISReset I've found is important for making sure it's updated. Like Waqas said, resetting the timer service and admin service in services.msc is also helpful to ensure the reloading of updated assemblies.


1

We had the same problem in our environment couple of months of ago, when ever you try to update the solution it says successfully deployed but still no changes showed. Almost same steps we followed as you mentioned. Finally we use some tool to check which Dll load in the Timer services and here we found our problem. SO in our case easy fix was Restart ...


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

Well I found an alternative solution in the form of a REST WCF web service for SharePoint 2013. (Guidelines Can be found here) After you have a working WCF web service. Use the HttpSend activity to call the method.


1

You receive the 401 because SharePoint still expects you to authenticate - so though IIS is passing in IUSR, it doesn't have permissions to logon. You stated you are not seeing the button for enabling site access - and this is what you need before anonymous user can see site content. From what you describe if you followed those steps you should be ok - but ...


1

I don't think you can accomplish this declaratively via CAML within an elements.xml file. However, if you are developing for SharePoint 2013 you may want to look into managed navigation, specifically the friendly URLs functionality: "Friendly URLs are URLs that correspond to a term in the navigation term set, and that provide a shorter, more meaningful ...


1

Basically its depend upon your requirement. as per your questions...you want to use the support for InfoPath, Excel Web Services, User Profile Synchronization, and Search. One thing is missing how many users will access the farm and how many documents search will crawl. As MSFT streamlined technology guideline, it is clearly mentioned one server farm will ...


1

In Sharepoint online you can not deploy files to the _layouts folder as there is no _layouts folder there. For Sandbox solutions, the Style Library is the correct location. If you are going to keep them in the Style Library can try referencing the scripts using the ~sitecollection replacement token (generally Style Library is only provisioned at the root ...


1

If you deploy a web part for a farm and you try to activate it from the feature it will not work because you need to activate it from a site, you cannot do it a deployment time and it will give you an error.


1

Custom developed web parts get the safe control entry automatically added, when it is created in Visual Studio 2010 and deployed . Only Refactoring the name or namespace of the web part class will break that safe control entry. OR This is common error if you eg. changed WebPart name after creation and/or changed its namespace. If you are working on ...


1

You should structure your features in a way that makes sense to your project. The key aspect of features is that they can be turned on and off on a site. The simplest thing to do is to put all your stuff in one feature, but that may or may not be the best solution in your case. Whether a feature is automatically activated on deployment depends on a few ...


1

There is nothing call Install Feature. When you deploy a new solution this is what happens. It first add the solution to farm. Then deploy the solution. If you have set the features to activate on the deployment in the Feature settings, it activates. You do not need to have one feature per webpart. It depends on the requirement. You can even handle with ...


1

I am not sure about the script why it is throwing the error, I would rather recommend you to post his Blog may be he will give you answer why it is failing. Did you check these commands from Gary. http://www.falchionconsulting.com/PowerShellViewer/Default.aspx I would also recommend you to use the 3rd party tools which have the atleaset 14 days trail. If ...



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