I have a medium server farm with two front end web servers. I'm a bit perplexed about a problem I've had with one of the servers. When I go to Central Administration > Operations > Timer Job Status I see that the Immediate Alerts service has failed with a status date of 10/9/2007. However, the other web server shows the status updating every 5 minutes as expected. I have disabled and reenabled alerts for the servers, both in Applications and using the stsadm command line tool. I have also changed the frequency of the alerts and even attempted to update the alert templates. I have restarted the server and I still get no update to the status date. It seems there is nothing that will tell the first server to kick off and retry running the timer job. Has anyone experience this and is there a way to instruct a specific server in the farm to run a timer job? Thanks!

Oh, let me add thatthis started after a power failure in our server room.

Have you found the problem or anyone have any ideas? Immediate Alerts says Failed 100% 10/15/2007 on the Timer Job Status screen. I've restarted the SharePoint Timer Job Service on each web box. Any ideas how to kick the Immediate Alert to start up again on the one web server? Thanks

I've restarted the Time Services on both of my web boxes but it didn't fix it--still says Failed--but they work. Another problem I'm working with is the alerts are not working for any of my SharePoint 2003 portals. It started when I upgrade the Shared Services to SharePoint 2007, would this prevent alerts to work on portals using SharePoint 2003?

Did you figure outthe problem here? We are getting the same behavior....2 WFEs in this environment and one of them has been failing ''immediate alerts' since 4 days ago. Shows Failed 100% while the other server has been running the alerts just fine. Restarting services, and enabling/disabling the service on the server, IISResetdoesn't seem to fix.Any help would be appreciated!Thanks

I am getting the same behavior here as well. There are six 'Immediate Alerts' timer jobs. Three for the Central Admin WFE server, and three for the Reporting Services server. The reporting services server jobs are humming right along, successfully running every 5 minutes. The jobs on the Central Admin server, (which evidently actually affect the ALERTS), have 'failed' status with dates from last week. Has anyone solved this? It's all over the 'net with varying degrees of advice. I've tried it all, checking the stsadm properties, checking the TimerLock in SQL, stopping and starting the Timer... No Joy.

Hi KVollero - I found this article which may help you http://weblogs.asp.net/mellota/archive/2007/10/11/sharepoint-2007-task-notification-alert-emails-not-working.aspxas well as MS KB which fixes a tons of WSS 3.0 problems together with "SharePoint timer job definitions" -->http://support.microsoft.com/kb/941422/en-us- Andrei

You can use a simple console application to tell SharePoint to run the timer job: http://www.johnchapman.name/sharepoint-2007-immediate-alerts-console-application/John Chapman | Blog: http://www.johnchapman.name