JonathanHerschel
Programmer
My client currently has an issue where the alerts are not working. The initial confirmation gets sent, but no alerts are created when an alert is set up and item is added/deleted, etc... It appears that this issue is occuring when the server runs out of hard drive space. I've spent a few days researching a fix, but to no avail. Sharepoint SP1 was installed previously in attempt to fix
the alerts.
So far I've:
-Verified Alerts are enabled (set alerts-enabled to false, then back to true.)
-tried stsadm -o updatealerttemplates -url " -filename "c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\xml\alerttemplates.xml"
-tried STSADM -o setproperty -pn job-immediate-alerts -url url -pv "every 3 minutes"
-tried sts add-on stsadm -o restarttimer
-tried using sts add-on stsadm -updatealerts as client has web server https:// and app server so to do a search and replace of https with http and vice versa (alert propertybag setting).
-added the account used to run the SharePoint Timer Service as SharePoint Administration Group account (farm admin).
-Made sure the account used for OWSTimer.exe had read/write access to the Content Databases and SQL.
-verified account that the SharePoint Timer Service is running under does have access to the content database
-Re-entered username and password of Timer service account, stopped, started rebooted the servers (web, app, and db)
-Looked in WSS_Content and other content db's and looked in ImmedSubscriptions, schedsubscriptions for anything out of the ordinary.
-Looked in log files and this message appears.
-break permissions of site, then list/doc lib, then re-inherit.
-Ran vb script to test message to verify the configuration of the SMTP service (
1 thing I've come accross, but would rather wait until the last draw:
wipe out ImmedSubscriptions and SchedSubscriptions tables and have users re-create alerts
Any suggestions would be MUCH appreciatted
I hope this post will become useful by containing many things to try when alerts are not working.
Regards,
Jonathan K Herschel
the alerts.
So far I've:
-Verified Alerts are enabled (set alerts-enabled to false, then back to true.)
-tried stsadm -o updatealerttemplates -url " -filename "c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\xml\alerttemplates.xml"
-tried STSADM -o setproperty -pn job-immediate-alerts -url url -pv "every 3 minutes"
-tried sts add-on stsadm -o restarttimer
-tried using sts add-on stsadm -updatealerts as client has web server https:// and app server so to do a search and replace of https with http and vice versa (alert propertybag setting).
-added the account used to run the SharePoint Timer Service as SharePoint Administration Group account (farm admin).
-Made sure the account used for OWSTimer.exe had read/write access to the Content Databases and SQL.
-verified account that the SharePoint Timer Service is running under does have access to the content database
-Re-entered username and password of Timer service account, stopped, started rebooted the servers (web, app, and db)
-Looked in WSS_Content and other content db's and looked in ImmedSubscriptions, schedsubscriptions for anything out of the ordinary.
-Looked in log files and this message appears.
-break permissions of site, then list/doc lib, then re-inherit.
-Ran vb script to test message to verify the configuration of the SMTP service (
1 thing I've come accross, but would rather wait until the last draw:
wipe out ImmedSubscriptions and SchedSubscriptions tables and have users re-create alerts
Any suggestions would be MUCH appreciatted
I hope this post will become useful by containing many things to try when alerts are not working.
Regards,
Jonathan K Herschel