Tag Info

New answers tagged

0

To get around it with the client Object Model you can use this code snippet, it uses item pos to leverage getting more than 5000K items. if you need VB.NET or more in-depth breakdown this is the site for you here The Snippet is from here List list = ClientContext.Web.Lists.GetByTitle("Assets"); ListItemCollectionPosition itemPosition = null; while (true) { ...


1

The timer service is for all administrative, deployment, and services from a very high level, including updating configuration and those servers to the farm. Turning the timer service off can be problematic. If you want emails to go out on a specific server, enable the SMTP service and follow this guide to set up SMTP and the configuration that goes along ...


1

If this is YOUR TEST/DEVELOPER ENIVRONMENT, you can use the following method In Web Application's web.config, change the deliveryMethod of the SMTP settings to SpecifiedPickupDirectory and give it a location to push the emails to. <system.net> <mailSettings> <smtp deliveryMethod="SpecifiedPickupDirectory" ...


0

You need to set the SPJobDefinition.LockType property on your job definition to None. Here are the possible SPJobLockType values. Behavior that I have seen is, if you set it to Job, it will run only once, on one server. If you set it to ContentDatabase, it will run on only one server, but it will repeat consecutively for as many times as you have content ...


0

The 'System.Management.Automation' dll issues have several sources and in your case, it's also coupled with changes in the SharePoint versions (2010/2013) and the move to 64-bit Server 2012 (presuming your SP2010 was on a 32-bit platform). Here's a checklist of items to look into - A). Check Execution Policy of script: Set-ExecutionPolicy -ExecutionPolicy ...



Top 50 recent answers are included