Hi,
I’m a beginner on SharePoint Foundation 2013 and i’ve done a SharePoint farm. I don’t understand why but some jobs enumerated in my tasks job, has in last execution time “Non Applicable”. The task are default sharepoint tasks
Also immediate alert are “Non Applicable” so they don’t work !
I’ve passed 7 days looking for it but i didn’t find the problem.
I’m totaly lost 🙁 If someone has an idea it will be helpful for me 🙂
Thanks,
Dear Leitao,
I am facing the exact same issue but on SharePoint 2016 Farm. Did you manage to resolve this Issue?
Appreciate your help on this guys,
Best Regards,
ok i ‘ll become clear with the following description :
SharePoint farm :
Just one server (Windows Server 2008 R2, SQL SERVER 2008 R2, SharePoint Foundation 2013)
2 applications web : The first got one collection site “intranet” and the other got two collections sites.
I begin by the list of process : We can find only one the process “OWSTIMER.EXE”
Next all the immediate alert jobs in the timer job part of central sharepoint administration have the last execution time : “not applicable” like this (in french) :
So the alerts are never receive however i receive the email notifications and all my sharepoint worflow who send email are received with no mistake.
Next, if i run the powershell command “Get-SPTimerJob”, i’ve got my list of jobs with the last execution time. All the job tie to an application web (like in the picture below Application web : extranet Sothis) didn’t have a correct execution time but jobs who refer to global job for the farm have a correct execution time.
For example, jobs with no application web tie who worked fine :
Processing using Microsoft SharePoint Foundation Data
Work synchonizer licences
Timer job usage analysis for the search application Search Service Application
whereas this jobs didn’t worked :
Warning disk quota
Immediate alert
Switching Workflow
I hope to be clear 🙂
Thanks for your kindness,
?width=721?width=500
That means the alert has not fired. Can you clarify the last part of your statement? If the timer job was not associated with a Web Application, I’d expect this default year, and if it was, I’d expect it to be very recent.
Thanks for your answer,
for all my alert immediate the last execution time is “01/01/0001 00:00:00” and i notice that all my job tie with an application web have this execution time unlike all job not tie with an application web (they have a correct execution time).
Very strange !
If you enumerate the timer job via PowerShell (Get-SPTimerJob | where {$_.DisplayName -like “*immediate*”}), does it show a proper last execution time?
