Users do not recieve alerts for changes made to items although “Immediate alerts” are enabled in the site collection.
• The record is not processed by the timer service job correctly for this specific content database.
• The record is processed correctly. However, the email delivery mechanism is not working fine. For example, the alert templates fail to be picked up by the SharePoint Timer Service.
• Email server is not working.
• Open Central Administration
• Open the command window and navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> and run the following command: stsadm -o getproperty -url <http://siteurl> -pn alerts-enabled
• The expected output is <Property Exist=”Yes” Value=”yes” />
on the content database.
extensions\12\BIN>stsadm.exe -o getproperty -url <http://siteurl> -pn job-immediate-alerts
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o setproperty -url <http://siteurl> -pn job-immediate-alerts -pv “every 5 minutes between 0 and 59″
The internal working mechanism of how an alert works in Windows Sharepoint Services 3.0:
• The EventCache table records the SQL level events as they occur and the EventData and ACL columns are not NULL for an alert event.
• There is an alerts timer job that runs periodically to process the records in the EventCache. After the alerts timer job runs, it nulls out the EventData and ACL columns.
• It will log an event into the EventLog table.
• Open SQL Query Analyzer and connect to the content database of concerned site.
• Run the following query in SQL and copy the result out: Select * from timerlock
If the issue persists, collect the following information:
• Run the following query against the content database of concerned site: Select * from eventcache where EventData is not null
This will show all the subscriptions which have not been processed yet. We can see if there are some alerts which are not processed.
concerned listor document library.
• Create a new item in the list or document library where the alerts should work and start Filemon
• Check if the latest result is the one corresponds to your uploaded document. Make sure the EventData and ACL columns are not NULL.
• After some time, check the EventCache table again to see if the EventData and ACL columns are NULL.
• If yes, stop Filemon after the EventData and ACL columns are NULL.