Note: This already existed as a WSS (2.0) FAQ item. This is an attempt to extend it into the WSS 3.0 (and MOSS 2007) world.
The standard reason in v2 for Alerts not to work was that SharePoint Timer Services wasn't running (and if running was using the wrong authority).
Read on for some v3 specific additions to that.
Christian Eidsmoe had these additional suggestions:
I went through the suggestions "and alerts still were not working for me, and I figured it out:
Under central administration, operations, (global configuration)timer job status or timer job definitions , if you don't see an "Immediate Alerts" timer job def, you need one!
I did not have one until I ran these stsadm.exe commands on my WSS 3.0 server:
stsadm.exe -o setproperty -url http://mywss30server/mysite -pn alerts-enabled -pv true
stsadm.exe -o setproperty -url http://mywss30server/mysite -pn job-immediate-alerts -pv "every 5 minutes" Now it works! All the alerts that had been piling up for two days came through."
Thanks, Christian!
Chandra had a similar experience
I had the same problem. I had migrated (better to migrate using the Central Admin backup-restore instead of STSADM to restore entire farm data) the sites to SQL server Express edition and deleted all the rows in ImmedSubscriptions and SchedSubsctions tables from the Content database.
Reset the alerts in the Web Application genaral settings. executed the following commands given by Christian Eidsmoe.
As Christian quoted "Under central administration, operations, (global configuration)timer job status or timer job definitions , if you don't see an "Immediate Alerts" timer job def, you need one! "
set your alerts now.
set your alerts now.
Alyssa sent me a comment which I hope was about this item
I found the following will get alerts flowing again when moving site from WSS3.0 to MOSS.
Basically, change the SiteURL and WebURL values for the content DB associated with the web application in the ImmedSubscription table.
Thanks Alyssa !