New answers tagged

0

But better synchronization service run by SP Central Administration. Central Administration > Application Management > Service Applications > Manage services on server , select "User Profile Synchronization Service" and "Start" with screenshots One of the possible causes of errors with EventID 6398 "The Execute method of job definition ...


2

I haven't done this but based on my discussions with people I respect in the community I think Azure WebJobs are the way to go. Here are a couple resources that will help you get started. SharePoint Timer Jobs running as Windows Azure Web Jobs Getting Started with building Azure WebJobs ("Timer Jobs") for your Office 365 sites


2

Arf, that's exactly why I 100% prefer on-prem SharePoint! In your situation, in all cases, you'll have to setup and maintain another server. Your options are: Create a Windows Service hosted on a third-part server. You can write in C# and leverage the client-side .NET API of SharePoint. Create a Console application, still hosted on a third-part server. ...


2

Farm solutions are only unavailable if SharePoint Online is a consideration. SharePoint 2016 continues to fully support not only custom Timer Jobs, but Full Trust Code Solutions, as well. I feel that FTC solutions should be used when and where appropriate for customers who continue to use SharePoint On-Prem. If you can find alternative solutions that do not ...


1

I would suggest a timer job or a console application to handle this. Pausing until a date won't have a huge performance impact as the workflow gets serialized to the database until it is time to do something. This big problem is that if that date changes, it doesn't affect the workflow that is currently running on the item. We have converted several ...


0

You need to carefully examine the ulslogs. And post back here with findings, otherwise it is total guess work.


0

Did you tried to debug your code. Your code has SPSite site = new SPSite(SPContext.Current.Web.Url); This line should not work in Timer Job, Since the Timer Jobs runs as a background process it won't take any SharePoint Context from SPContext.Current.Web.Url; Please create Property Bags in your Web Application or you can add App Settings in your ...



Top 50 recent answers are included