Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

My MOSS 2007 Alerts stopped working

  Asked By: Gabriella    Date: Mar 15    Category: Sharepoint    Views: 1139

i have a problem with the alerts in sharepoint server 2007. i have tried
the following

1. restarted the timer service
2. stsadm -o execadmsvcjobs
3. stsadm.exe -o setproperty -pn job-immediate-alerts -pv "every 5
minutes between 0 and 59" -url http://..... <http://...../>
4. stsadm.exe -o setproperty -url .... -pn alerts-enabled -pv true
5. Checked the logs but nothing seems wrong


However, when a user subscribes or is subscribed to an alert, the first
email is sent.

The problem started after we lost power in the datacenter and the server
shutdown.


extract from the trace log (what does "DB n/a" mean?):


Timestamp Process TID Area
Category EventID Level Message Correlation
06/25/2009 15:44:45.65 OWSTIMER.EXE (0x12A0) 0x1BA0
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4}, DB n/a
06/25/2009 15:44:45.65 OWSTIMER.EXE (0x12A0) 0x1BA0
Windows SharePoint Services Timer 8e46 Verbose End
invoke timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4}, DB
n/a
06/25/2009 15:44:45.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4} at
25 Jun 2009 15:45:00 -0000 (now is 25 Jun 2009 15:44:45 -0000)
06/25/2009 15:44:57.65 OWSTIMER.EXE (0x12A0) 0x19E8
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job Application Server Timer Job, id
{0F83E892-B188-4D9E-BEE7-E16C535A6F48}, DB n/a
06/25/2009 15:44:57.65 OWSTIMER.EXE (0x12A0) 0x19E8
Windows SharePoint Services Timer 8e46 Verbose End
invoke timer job Application Server Timer Job, id
{0F83E892-B188-4D9E-BEE7-E16C535A6F48}, DB n/a
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utq Verbose
Scheduled internal timer job 2 at 25 Jun 2009 16:00:00 -0000 (now is 25
Jun 2009
15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x1CDC
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job SharePoint Services Search Refresh, id
{093FDD31-32CE-4DF0-9514-FA2BDDBF2DA1}, DB n/a
06/25/2009 15:45:00.67 OWSTIMER.EXE (0x12A0) 0x1414
Windows SharePoint Services Timer 8e46 Verbose End
invoke timer job Quick Profile Synchronization, id
{8CE5D803-9F09-4C77-B2E0-3108B77431D4}, DB
{9E582CA6-5131-4CE8-AE9D-C3A887C1F89A}
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x14E4
Windows SharePoint Services Timer 8e49 Verbose
Begin invoke internal timer job 2
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x1AEC
Windows SharePoint Services Timer 8e46 Verbose End
invoke timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4}, DB
n/a
06/25/2009 15:44:57.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Application Server Timer Job, id
{0F83E892-B188-4D9E-BEE7-E16C535A6F48} at 25 Jun 2009 15:45:57 -0000
(now is 25
Jun 2009 15:44:57 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4} at
25 Jun 2009 15:45:15 -0000 (now is 25 Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job SharePoint Services Search Refresh, id
{093FDD31-32CE-4DF0-9514-FA2BDDBF2DA1} at 25 Jun 2009 16:00:00 -0000
(now is 25
Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Quick Profile Synchronization, id
{28209E94-9FFB-4CE5-BD23-EB80181DA3BE} at 25 Jun 2009 15:46:00 -0000
(now is 25
Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Quick Profile Synchronization, id
{E54B0FA6-894C-4B80-8908-048AFB0508E1} at 25 Jun 2009 15:46:00 -0000
(now is 25
Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Quick Profile Synchronization, id
{8CE5D803-9F09-4C77-B2E0-3108B77431D4} at 25 Jun 2009 15:46:00 -0000
(now is 25
Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Synchronization Scheduler, id
{4E960EF0-86D6-4FA1-A8AE-5EF7F3B4332B} at 25 Jun 2009 16:00:00 -0000
(now is 25
Jun 2009 15:45:00 -0000)
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x1AEC
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job Config Refresh, id
{AF6DC3A1-B32E-41AA-920F-EFEF28FD13B4}, DB n/a
06/25/2009 15:45:00.65 OWSTIMER.EXE (0x12A0) 0x1414
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job Quick Profile Synchronization, id
{8CE5D803-9F09-4C77-B2E0-3108B77431D4}, DB
{9E582CA6-5131-4CE8-AE9D-C3A887C1F89A}
06/25/2009 15:45:01.65 OWSTIMER.EXE (0x12A0) 0x0190
Windows SharePoint Services Timer 8e45 Verbose
Begin invoke timer job Workflow, id
{149C9DE1-C410-4965-BC78-73CBCE698AB6}, DB
n/a
06/25/2009 15:45:02.04 OWSTIMER.EXE (0x12A0) 0x1CDC
Windows SharePoint Services Timer 8e46 Verbose End
invoke timer job SharePoint Services Search Refresh, id
{093FDD31-32CE-4DF0-9514-FA2BDDBF2DA1}, DB n/a
06/25/2009 15:45:04.65 OWSTIMER.EXE (0x12A0) 0x0910
Windows SharePoint Services Timer 5utp Verbose
Scheduled timer job Workflow Failover, id
{BB310331-797F-4031-B240-3F238872A877}
at 25 Jun 2009 16:00:04 -0000 (now is 25 Jun 2009 15:45:04 -0000)

Share: 

 

No Answers Found. Be the First, To Post Answer.

 
Didn't find what you were looking for? Find more on My MOSS 2007 Alerts stopped working Or get search suggestion and latest updates.




Tagged: