I would like to warn you that is may be a long post, but please don't let that deter you from reading. Because I need some help. In our production farm we have 2 servers, an SQL Server and a Front End server. Back some time around July last year when some updates were applying, our alerts quit working. Our search started working part time, but recently that has been fixed. At first I thought the two may have been connected, but now I don't believe so. Today I was comparing our dev farm and the production farm. I was checking to see if the alerts worked on the dev setup. They did so I decided to compare the two (pro v/s dev). When you look in the Timer Job Status list in Central Admin on the Dev box, it shows that the Immediate Alerts timer job is running on the Front End server. But the production server shows it to be running on the SQL server. I believe this is the reason why it is not working. But it has worked in the past. My current thinking is when the updates running last July ran something failed resulting in the job being diverted to another server. LONG story short, how can I direct this job back to the Front End Server?

Not sure wy this would be on SQL but you should be able to turn off alerts in the central administration for the web app they are currently running on - and turn them on on another. Take a look at the STSADM alerts-enabled command stsadm.exe -o setproperty -url http://myserver:112345/site -pn alerts-enabled -pv true Regards John Timney http://www.jontimney.com/blog

I believe I should have named this something different. There are alot of post about alerts not working, but very few seem to be the same as mine. So I believe it is getting looked over and not read a lot. The 2 I have found were issues where the admin added another server to the farm. In doing so the new server mysteriously took control of some timer jobs. Which is what has happened here, but I have not added any new servers. Their resolution was to turn off the new server for 30 minutes to an hours. In doing so, the central admin server took back over the jobs. But in my case the DB server took the over the jobs, for some unknown reason. Anyone want to take a guess at what will happen if I power off the DB server?