Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Alerts not working after server runs out of space (MOSS 2007)

Status
Not open for further replies.

JonathanHerschel

Programmer
Mar 29, 2007
33
US
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
 
Sorry I didn't post back to this thread earlier. We fixed the Alerts issue, but we have no clue what 'fixed it'. We did the following:

1. We found that one of the front end servers didn't properly upgrade to MOSS 2007 SP1. We tried to upgrade with the sp1 upgrade file, but it said that it was already upgraded to SP1.

2. We called MS support and they had us modify an XML file to 'force' the upgrade and then our one front end server displayed the proper version.

Duing this 2 day venture, the Alerts started working. We asked the MS support person if there is anything that during this failed then forced upgrade that could have fixed the alerts. He wasn't sure, but did say that alerts are controlled by 1 server. He said it was possible that when we tried to run the upgrade and it failed, it could have kicked the alerts over to the other front end server and therefore started working. A few knowledgable SP friends said they never heard such a thing.

Look at this other forum response ( dealing with the Alert cache folder being deleted. Never heard of this before, but something to add to the list of things to look at when alerts are not working

Jonathan Herschel
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top