SPImmediateAlertsJobDefinition errors in Event Log

Question

I am sporadically getting errors in my Event Log for SPImmediateAlertsJobDefinition with the ID 6893, I've seen some of the posts out there pointing towards issues with the SharePoint assembly files. Yet I don't think this is the solution since this job runs but only fails say 25% of the time, this is a rough estimate but I do see it run. In Event Log I see the entry for ID 6893, the source is SharePoint Foundation and it comes from the Timer Task Category. Checking ULS I get:

Updates are currently disallowed on GET requests. To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.

The Execute method of job definition Microsoft.SharePoint.Administration.SPImmediateAlertsJobDefinition (ID 3b4f3122-46e4-4a9c-952c-a118758f3693) threw an exception. More information is included below. Updates are currently disallowed on GET requests. To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.

Exception stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.DispatchTimerJob(Int32 lJobType, Guid gVServerId, Int32 lScope, Guid gDatabaseId, String bstrDSNServer, String bstrDSNDatabase, String bstrDSNUser, String bstrDSNPassword)
at Microsoft.SharePoint.Administration.SPNativeDatabaseJobDefinition.Execute(Guid targetInstanceId)
at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)

Far as I know SPWeb should be set. Has anyone found a solution to this or should I just ignore it expecting the next run to resolve the problem?

Answer 1

Sometimes, when doing upgrades, or restoring from back ups, timer jobs aren't migrated correctly and become corrupt.