Tag Info

New answers tagged

0

Try to define this constructor: public SendMailDaily SPWebApplication application) : base(JobName, application, null, SPJobLockType.Job) { } and then use it: SendMailDaily job = new SendMailDaily(site); instead of SendMailDaily job = new SendMailDaily(JobName, site);


0

I also received this kind of error before while deploying webpart, so i used powershell to add solution, that time it shown the actual error that my SharePoint_Config log file was full. You can check below two scenario: 1) Your sharepoint_config log file is not full and you have diskspace on server. 2) The account you are using to deploy solution has ...


0

Try below function string GetTimerJobStatus(string timerJobName) { string schedule = string.Empty; SPSecurity.RunWithElevatedPrivileges(() => { SPWebApplication webApp = SPContext.Current.CurrentWeb.WebApplication; foreach (SPJobDefinition job in webApp.JobDefinitions) { if ...


1

var spFarm = SPFarm.Local; var timerJob = spFarm.TimerService.JobDefinitions.OfType<SPJobDefinition>().FirstOrDefault(n => n.Name == "Timer Job Name"); and then take a look at timerJob.Schedule object.


0

You should consider the following during the move: You may only need WSP which contains timer job logic that can be deployed to 2010 platform. You have to perform IISReset and restart timer job service to have full impact in 2010 version. If you want to improve the timer job for 2010 (for whatever reasons) source code must be kept alive and you should be ...


0

I hope below link will help you https://bhandariasb.wordpress.com/2013/08/07/how-to-prevent-sharepoint-timer-jobs-from-running-multiple-times/



Top 50 recent answers are included