WSS 3.0 Alerts Not Working For All Sites
I have a fresh WSS3.0 installation in Windows Server 2008. Alerts aren't working the way they're supposed to. When I go to create an alert, I get an an e-mail alert that the alert has been created. However, when I make updates to the task or add announcements, I don't get any alerts at all. Immediate alerts are obviously working, however they don't work after the alert is created. Where should I look?
September 10th, 2010 6:26pm

This can often be rectified by issuing the statadm updatealerttemplaates command as outlined here: http://technet.microsoft.com/en-us/library/dd278299(office.12).aspx Chek your LCID here: (1033 is US) http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx Regards John Timney
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2010 1:45am

Hi frivers, Thank you for share your problem. Could you please tell me whether your SharePoint and your SharePoint databases run under an account that has access to the SharePoint Content database? Because the SharePoint Timer Service must run under an account that has access to the SharePoint Content database. And during WSS 3.0 configuration, whether you migrated from WSS 2.0 or you installed WSS 3.0 directly, you had to setup an administration account with domain administration rights on your front-end web server’s domain. This account had to be added to SQL-Server(windows authentication) and given some special database rights. Then this account would work. Also, whatever account your Web Application’s application pool use would also work. And if your SharePoint and SharePoint databases run on two different standalone domains, make sure that there is a cross-domain trust established between your font-end web server and SQL-Server domain. Hope this helps you. Best regards.
September 14th, 2010 5:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics