New answers tagged

0

Problem Solved When I was specifying the site to run against: I had to use https for it to work. Silly mistake really: It connects properly now.


2

A single timer job could read from a data source (e.g. SharePoint list) which marks what Site Collections need to be processed, as well as what Site Collections have been processed (e.g. a column with the URL, and a column with a Boolean 'completed'). The timer job could then take 10 at a time and process only those. You could use multi-threading in order to ...


1

You would have a few options, you could have a service in Azure that handles this. The advantage here is that you can deploy services in the same region as your tenant for fast performance. Another option would be to create your timer job solution as a compiled executable and use a central server in your environment as a "scheduling hub". Here you would ...


0

As far as I know, timer jobs are not allowed on O365. However, you can create Microsoft Azure WebJobs. You can find a sample console application in the link below that will give you a good start on how to implement/deploy one: https://msdn.microsoft.com/en-us/library/office/dn986826.aspx


0

You can not do it up to my knowledge. This is one of the HUGE drawbacks to SharePoint in my opinion. Any time you make deployments for example, You have to schedule those because you know the app pool is going to recycle.



Top 50 recent answers are included