Sharepoint Server 2007（MOSS） Alert Email Troubleshoting--Part II

其他詳細步驟

1. Open the command window, go to the BIN folder and get the property of
Alerts-enabled to make sure the alerts are enabled for the timer service:
C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\BIN>stsadm.exe -o getproperty -url -pn
alerts-enabled
The expected output is


2. Open the MOSS Central Administration page, click Operations--Timer Job Status,
make sure the following two jobs are showing "success" and 100%
Change Log
Immediate Alerts


3. Make sure the account running the SharePoint Timer service is the account which has the administrator Full Control permission over the site and the full permission over the content database. Restart the timer service if required.

4. 檢查資料庫：
在content db中，timerlock
Open SQL Query Analyzer, connect to the content database of problematic site.
Run the following query and copy the result out.
Select * from timerlock
Let me know the server name seen in the LockedBy column is the same one of this SPS
server. This server is responsible for processing the timer service.

1. Run the following query against the content database of problematic site
select * from eventcache where EventData is not null
(找出尚未送出的ALERT，若完成寄送，EventData 會被設為null)
This will out put all fo the subscritions which have not been processed yet. We can see if there are some alerts which are not processed

2. select * from eventlog where ListID = 'xxx'
（）
You can get the ListID from the EventCache table by running
Select * from EventCache and check the documents which correspond to the problematic list.

3. If you cannot find any record in the step 1, please perform the following tests:
Put filemon on the SPS server and we can see if the Timer service picks up the alert template during the whole process.
a. Upload a new document to the document library which is supposed to have the alerts. Begin running the filemon.
b. Run
select * from eventcache order by EventTime DESC
Check if the latest log is the one corresponds to your uploaded document. Make sure the EventData and ACL columns are not NULL.
c. After 5 minutes or more minutes, check the EventCache table again to see if the EventData and ACL columns are NULLed.
d. If so, stop filemon after the EventData and ACL columns are NULLed