In my medium farm, one server has timer error 6398 every night at 12am. The error message is:The Execute method of job definition Microsoft.SharePoint.Publishing.Internal.NotificationJobDefinition (ID 7401ef2c-8b6a-41a6-a776-1719f76e1d1d) threw an exception. More information is included below.Object reference not set to an instance of an object.This is a server running "search" service. I also use it as dedicated web front end computer for crawling so it has "windows SharePoint services web application" service running as well. The other "real" web front end server doesn't have the same Timer error. So I assume the error is somehow related to the indexing?I googled online and find very little information about this error. Thanks in advance!

This patch will fix the 6398 issue; FIX: You may be unable to manage IIS 6.0 by using Server Manager if two threads access IIS 6.0 at the same time http://support.microsoft.com/kb/946517 Cheers,

Thank you, Kristof. Actually I already applied the IIS hotfix you pointed out. I had timer error , error 7076 and error 6398 popping up every 5 minutes after I applied a recent secruity patches for Windows 2003. I therefore applied IIS hotfix and three errors disappeared. This Timer error re-appeared again Alone at 12am daily now. The error message for the error 6398 is different from the one before applying the hotfix.

Is 12am when you have an index job running? If so, do you see any errors in your crawl logs?

It was not my index job. When I looked Timer job status, at 12am it has a job "Scheduled Page Review" with "failed" status. This is the one related to the error. However I don't know what caused the failure and how to change its scheduled time if it's caused by overlapping time schedule. Thanks.

Judging on the source job definition "Microsoft.SharePoint.Publishing.Internal.NotificationJobDefinition" error you are getting, it seems like you are doing Content Deployment of sorts. Are you running Contend Deployment between farms or generating Variations? Have you checked the ULS traces and see what is logged before this error appears, or what appears after? If you check the Timer Job Definitions in Central Administratoin does this entry exist? Have you tried removing this definition from the Timer Jobs and see if it's recreated? Cheers,

I disabled the content deployment and the error still appeared.I disabled the Timer job and the eror disappeared. However I am still not sure what the cause is. I did check ULS traces and could not find any clue.

I get exact same problem.Scheduled Page Review Timer Service fails nightly. Everything else is great.Any resolution to this?

I disabled the content deployment and the error still appeared.I disabled the Timer job and the eror disappeared. However I am still not sure what the cause is. I did check ULS traces and could not find any clue. I have the same exact error. Every single symptom is identical.What are the ramifications of disabling the Timer Job? I've got four instances of "Scheduled Page Review" running in Timer Job Status (one for each Web Application). It doesn't identify which one of the four is the Failure.Any help is appreciated. I know my "Search and Index" is scheduled across all Web Apps for that time.

Same problem here. Did anyone ever resolve this? Or, is it fixed in any of the SPs or CUs? My production farm can't be upgraded at this time, so that's out for me.