Hi,

We had one custom timer job in production. Which is showing under job definition but not showing under job history or Running job status even after selecting Run now. I restarted timer services twice. I couldn't able to get any error related to timer job from log file also.

Its running fine in test environment.

Can any one suggest on

Hi Krishna,

If all you want to know is when it has ran for the last time you might want to check in the timer job definition where you should be able to see "Last run time".

Otherwise, in the Timer job history there is a filter at the right which may filter the current server. Make sure you are on "All" and that you are showing the last 2000 job history.

Regards

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

• Edited by Samuel Levesque 6 hours 10 minutes ago

Hi Krishna,

If all you want to know is when it has ran for the last time you might want to check in the timer job definition where you should be able to see "Last run time".

Otherwise, in the Timer job history there is a filter at the right which may filter the current server. Make sure you are on "All" and that you are showing the last 2000 job history.

Regards

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

• Edited by Samuel Levesque 6 hours 4 minutes ago

Hi Krishna,

If all you want to know is when it has ran for the last time you might want to check in the timer job definition where you should be able to see "Last run time".

Otherwise, in the Timer job history there is a filter at the right which may filter the current server. Make sure you are on "All" and that you are showing the last 2000 job history.

Regards

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

• Edited by Samuel Levesque Saturday, March 21, 2015 1:29 AM

Hi Samuel,

Thanks for reply.

I have checked the history which I was unable to find my timer job instance under runned status at my scheduled time.

So I run the timer job manually selecting run now from central admin.But still no use...

Hi Samuel,

My last run status of my timer job is showing as NA in central admin.But we are writing error log to log file if it throws any error. Unfortunately I was unable to find any thing related to my timer job from log files also.

Hi,

We had schedule throw feature receiver in code is a below. But in central admin its showing configured daily for 12AM to 12AM

SPDailySchedule dailySchedule = new SPDailySchedule();

            dailySchedule.BeginHour = 0;

            dailySchedule.BeginMinute = 0;           

            dailySchedule.EndHour = 0;

            dailySchedule.EndMinute = 0;

Hi Krishna,

Have you checked the Event Viewer and restarted the Timer Service (SPTimerV4) after deploying your WSP?

Are you scoped and activated to the Web Application level on your feature ?

Other than that you might check to see if the "time" is set correctly on your production server. This could cause problem with the job execution if it's not synced.

You could also check the Job definition with SharePoint Manager, this might give you additionnal information.

Also, i've found this article but I've never tried it (use it at your own risk, last resort) :

http://blogs.technet.com/b/victorbutuza/archive/2010/05/11/timer-jobs-missing-too-many-cpus.aspx

Regards

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

• Marked as answer by krishna_2012 32 minutes ago

Hi Krishna,

Have you checked the Event Viewer and restarted the Timer Service (SPTimerV4) after deploying your WSP?

Are you scoped and activated to the Web Application level on your feature ?

Other than that you might check to see if the "time" is set correctly on your production server. This could cause problem with the job execution if it's not synced.

You could also check the Job definition with SharePoint Manager, this might give you additionnal information.

Also, i've found this article but I've never tried it (use it at your own risk, last resort) :

http://blogs.technet.com/b/victorbutuza/archive/2010/05/11/timer-jobs-missing-too-many-cpus.aspx

Regards

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

• Marked as answer by krishna_2012 39 minutes ago

Hi Samuel,

Thanks for reply.

Unfortunately timer job not worked when I restarted my timer service once.

But I done the restart of timer service twice then luckily it started working. And now I can able to see my job status under history. But to make my job run against only one content DB what is the lock type to be used.

Currently we are using it as Locktype.ContentDatabase.

Hi Krishna,

I'm glad to hear that the Timer job reset worked. Please mark my previous post as an answer as this would be much appreciated :)

For your question about the locktype I think you are correct as per Microsoft documenation :

https://msdn.microsoft.com/en-us/library/office/hh528519%28v=office.14%29.aspx

SPJobLockType values

Samuel Levesque | http://sharepointerie.com | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.