New answers tagged deployment
Ensure that the service : Microsoft SharePoint Foundation Web Application (using central administration) is stop on your application server it should be better. Sylvain
Application severs are the heavy lifting servers, and host the service applications, including the search, user profile, performancepoint, excel, and other resource-intensive services. Having four application servers may be reflective of the amount of users that will be utilizing these services. Workflow 2013 is new to SharePoint 2013 and allows users to ...
Deactivate your features and delete the pages. Reactivate the features and they'll be provisioned again. My rule of thumb was if I was deploying assets, I had feature deactivation code to delete them. This made rapid development deployment possible by right clicking deploy in VS. The feature would retract, delete the deployed assets, be removed form the ...
Did you try adding ReplaceContent="True" to your module XML? Maybe the problem lies in SharePoint ignoring the file as it already exists in the targeted folder.
The newly-suggested "remote provisioning" options use CSOM/JSOM/REST, et.al. I learned about this in the excellent MVA course here: http://www.microsoftvirtualacademy.com/training-courses/transform-sharepoint-customizations-to-sharepoint-app-model
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 ...
Export-SPweb -Identity http://site/sub1/sub2 -Path "c:\lstExport\lstName.cmp" -ItemUrl "/sub1/sub2/lstName" -IncludeUserSecurity -Force -IncludeVersions All Add slash("/") at the start of the ItemUrl parameter.
First, Remove from Site Settings > List templates (Web Designer Galleries) and then try to remove from Site content types.
Check the permissions on the folder tree to the dll. First I would try with Everyone Full Control to the entire path, then strengthen the security step by step if it works.
In your web.config check whether you have entries for this webpart as Safe Registered assembly. To register a Web Part assembly as a SafeControl Open C:\inetpub\wwwroot\wss\VirtualDirectories\Port Number of your web application\web.config in Visual Studio or Notepad. Check if there is an entry for your web part in the block, if not you can add it as ...
Top 50 recent answers are included