Alerts not working for some site collections in a WSS 3.0 farm. SP1, SQL Server 2005 SP2. 2 servers in farm. Problem: - E-mail is successfullysent informing user they are subscribed, so SMTP from the farm works. - No alerts are actually sent (immediate or scheduled) that meet the criteria for a site collection, while another site collectionsends alerts fine. - Site collection was recently migrated from a different WSS v3 farm (no v2 involved) - Alerts function properly for other site collections in the same web app - Same Active Directory account is running all SharePoint processes and accessing the DB - Property values were already set (obviously since alerts are working for others in this web app) but I executed these commands anyway: stsadm.exe -o setproperty -url http://server -pn alerts-enabled -pv true - stsadm.exe -o setproperty -url <http://server > -pn job-immediate-alerts pv "every 5 minutes between 0 and 59" - Also ran the following command: stsadm -o updatealerttemplates -url http://server.com -filename "c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\alerttemplates.xml" - Restarted the Windows Time service and the SharePoint Timer service from services.msc - Checked the Content DB and can see recently created entries in ImmedSubscriptions and EventCache that match alerts just created - ULS logs are quiet and nothing in Event Viewer - No AD groups involved - No versioning enabledI have found multiple sites discussing this problem, but the few with fixes don't apply to my situation. Hopefully the information provided above explains configurations that, if different, have been the cause in other situations. Any ideas or knowledge of this would be helpful.

Hi, Since the site collection are moved from different farms, you need to update the alert URL of a Web application used in alert e-mails by using Updatealert: Stsadm operation (Office SharePoint Server) command. This command is introduced in SharePoint Administration Toolkit, please refer to Installing SharePoint Administration Toolkit (Office SharePoint Server) (http://technet.microsoft.com/en-us/library/cc508849.aspx) for download links and installation steps. -lambertSincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Since you have done a recent migration, please refer the below KB article :http://support.microsoft.com/default.aspx/kb/936759/en-usAlso you can find details on the common alert issue :http://blogs.technet.com/steve_chen/archive/2009/11/20/alerts-in-sharepoint-troubleshooting-moss-wss.aspxHopes any one of the above helps.........Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS

Thank you both for the responses. Lambert, Your solution is for a problem where alerts contain the old URL. My problem is that the Alerts are not being sent for one site collection, while other site collections send alerts just fine. Aj, Your link (kb 936759) is for an upgradescenario from V2, but I'm doing a migration v3 -> v3. I visited the 2nd link before creating this thread, but none of the steps applied or fixed the issue.Any other thoughts?

Try the below stsadm commands for the particular site collection in which you find the alerts missing.-o setproperty -propertyname alerts-enabled -propertyvalue false -url <site collection url> -o setproperty -propertyname alerts-enabled -propertyvalue true -url <site collection url> -o setproperty -propertyname job-immediate-alerts -propertyvalue "every 5 minutes" -url <site collection url>Refer : http://www.thesug.org/Blogs/benm/archive/2009/04/17/SharePoint_Alerts_Not_Working.aspx.aspx Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS

Aj,Good link! I thought that sounded promising and I hadn't set the "alerts-enabled" to false yet before running the other commands, but still no alerts are being sent.

As its said that you have recently moved the site applications recently to the new server farm.Please check the below link which points on the timer jobs which may have failed to run and the hotfix to resolve it.Issue : http://support.microsoft.com/default.aspx/kb/942989HotFix : http://support.microsoft.com/kb/941422/Check It out..........Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS

Ajith, I have seen that in my research, but since it was specific to web applications and not site collections I don't know that it applies. I have other site collections within this same web app that are working fine with alerts. I think at this point I am going to try to upgrade to SP2 and see if some of the alert issues addressed will resolve this. That won't be for a month+ with change freeze for Christmas break at our company. I'll post here if SP2 resolves the issue or not.Thanks for looking into this.

I suffer from the exact same issue. I have configured timer services, I have updated the alert templates I have restarted IIS, but still cannot explain why one set of site collections have working alerts, and another set does not (eventhough they are in the same web application. What I have found is that the content databases are common to those that work and those that do not. I also noticed that the event cache for the non-working content DB is much much larger. Is it safe to clean out the cache on these databases???? Has anyone else found a resolution to this yet?