Welcome: Guest!

MOSS Forum

 
Home » Forum » MOSS       Ask a questionRSS Feeds

Sharepoint 2007 ALERTS not working

  Asked By: Garrett Reyes         Date: Nov 26, 2008      Category: MOSS      Views: 1006
 

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://.....

4. stsadm.exe -o setproperty -url .... -pn alerts-enabled -pv true

5. Checked the logs but nothing seems wrong


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


extract from the trace log:
________________________________________________________________


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)


Please help

Tagged:          

 

3 Answers Found

 
Answer #1       Answered By: Candy Walter          Answered On: Nov 26, 2008       

If a new alert is created, does the user get the initial email that they have
created the alert? Are you set up with multiple servers in your environment?
If so, connect to your content database throught the SQL administrator and run
the follwoing query:

Select * from timerlock - This will tell you which server is responsible for
Timer Service

Select * from eventcache where EventData is not null - This will show you all
the alerts  that are queued.

 
Answer #2       Answered By: Leanne Rios          Answered On: Nov 26, 2008       

Yes, when an alert is created, the initial email is sent to users.

My MOSS 2007 implementation is a Single Server or Web Server for small server
farms (All services run on this server)

i followed your guidance and run the sql commands and

1. "Select * from timerlock" result shows a different server which is not the
MOSS 2007 server (It actually shows my test server)

2. "Select * from eventcache where EventData is not null" , it returns all
alerts in queue.

kindly show me how to remove the lock to get the alerts  working.

 
Answer #3       Answered By: Zachary Roberts          Answered On: Nov 26, 2008       

I am experiencing what seems to be an identical problem.
I have several content databases within a web application and a couple of the
content dbs have a server lock from my Index server, not my WFE server. I
believe this happened when I attempted to enable the WFE service on my Index
server. I have since removed the WFE service from my Index server, but the
server lock remains. I can't figure out any way to get rid of it. Anyone have
suggestions?

 
Didn't find what you were looking for? Find more on Sharepoint 2007 ALERTS not working Or get search suggestion and latest updates.


Your Answer
  • Answer should be atleast 30 Characters.
  • Please put code inside [Code] your code [/Code].

 
Hall of Fame  |  Facebook  |  Twitter  |  LinkedIn  |  Terms of Use  |  Privacy Policy  |  Contact us
RSS Feeds: Articles |  Forum |  New Users |  Activities |  Interview FAQ |  Poll |  Hotlinks


Go4Sharepoint, is a Microsoft Featured Community. Microsoft, Windows, Sharepoint, Sharepoint logo, Windows logo, etc are trademarks of the Microsoft Corporation. All product names, logos, copyrights, and trademarks mentioned are acknowledged as the registered intellectual property of their respective owners. This site is not in any way affiliated with, nor has it been authorized, sponsored, or otherwise approved by, Microsoft Corporation.

Copyright © 2008-2011