Re: WSS 3.0 sends new subscription alert, but no further alerts
- From: Vitamins <Vitamins@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Oct 2008 12:23:00 -0700
I was having the same issue, and figured out the user account that was used
to launch the "windows sharepoint services timmer" service, had changed
passwords based on the domain password policy. I changed the password to the
current one, and it is now working.
Jeff
"Megan Brown" wrote:
hi..
i actually have been trying to resolve this problem for months. i have
googled and googled and googled, and tested and still no joy.
i had actually already attempted everything you listed below, plus one more:
http://www.sharepoint-girl.com/2008/01/wss-alerts-not-working.html
and still no joy.
and thus, i posted here.... hoping on the off chance that someone might have
the solution.
here is what i've noticed:
there are no errors in Event Viewer
when i turn up sharepoint diag logs, i can see where the initial alert is
sent out (the notification after one subscribes). however, when the list is
updated, there is no indication that sharepoint is even trying to send the
alert.
i have tested SMTP... verified that sharepoint is not even handing off the
alert. to do this, i stopped smtp service, and tried to trigger an alert,
and then check the smtp mail folders. no joy. moreover, if this problem
were with SMTP, i shouldn't be getting the initial alert.
i know the timer service itself has access to the content database, because
it's running other jobs successfully. moreover, i even tried resetting the
account / password for the web application pool and timer service, just on
the off chance that gremlins had altered the rules of logic and magically
transformed the immediate alerts job into some other being that doesn't act
like the other timer service jobs... which obviously can access both the web
application and the content database without problems.
Tah Dah! still no joy.
i'm just a little irritated that you would assume that i'm just hopping on
the newsgroup looking for assistance without trying anything on my own. i
gave the short run down in my initial posting because i have found that
people don't tend to respond when i post a complicated problem that lists
out everything in detail.
"Callahan" <cacallahan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uBgoCP9%23IHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
Hmm, then you could check the usual suspects:
1) make sure that SMTP for the server is set to relay messages properly
http://technet.microsoft.com/en-us/library/cc288104.aspx#EHB
2) make sure that the immediate timer job is there and not failing
3) make sure that, if you have AV, it is not blocking the emails
4) make absolutely, positively sure that the timer job account has access
to
the content databases for the sites where the alerts are being set.
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=198
(shout out to Mike Walsh who compiled the alerts aren't working... list)
5) if you migrated from an earlier version to the one you have now, you
might have to force an update of some data.
http://glorix.blogspot.com/2007/10/alerts-not-working-all-time.html
I knew that problems with alerts were an issue that has popped up in the
past, so I did a quick google for it. I found all kinds of things that
could cause and fix the issue. In the future, you might want to search
through the newsgroups to see if anyone has had the same problem, or do a
quick google for it before posting here. If the problem has already been
solved, it will save you time. Often we have to query you several times
to really get the full skinny on what's going on before we can answer. If
you search through existing threads, you can see which match your
situation already, and possibly find your answer without delay.
Let us know which one worked for you (so when the next person searches the
'groups, they can use this thread to find the answer...).
-callahan
"Megan Brown" <mbrown@xxxxxxxxxxxxxx> wrote in message
news:%23kLiqt8%23IHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
Well, i have a test list so i can play around with it...
and i just use the drop down and select Alert Me.
i get the initial "welcome to" email that confirms the alert has been
set...
but then nothing else.
this is happening on all lists.
"Callahan" <cacallahan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%233$Fmyb%23IHA.3396@xxxxxxxxxxxxxxxxxxxxxxx
This may be a stupid question, but how are the alerts set for the users?
-callahan
"Megan Brown" <mbrown@xxxxxxxxxxxxxx> wrote in message
news:uvP$Z9Z%23IHA.3344@xxxxxxxxxxxxxxxxxxxxxxx
wss 3.0; windows server 2003 farm (1 web front end, 1 database backend)
i'm sure this issue is not SMTP. i have several other applications
using my smtp server without problem.
the issue is that sharepoint is not generating alerts. when a user
subscribes to a list, the initial "you have successfully created an
alert" email is generated and received by the user. however, users
receive no further alerts when the list is updated, even if the
subscription is set to send the alert immediately.
this problem arose a few months ago... just after i applied SP1 to wss
3.0. in fact, i would say it was working before SP1 and stopped working
after it was installed.
i have tried various ways to track down the problem, but i can't find
an
error anywhere... so i have no clue what the problem is.
what i have tried:
1. enable smtp logging. logs show smtp never receives mail from
sharepoint (i.e. nothing happens because nothing is given to smtp from
sharepoint)
2. turn up sharepoint logging... i can see where i add a new item to
the list... but never see the logging for an email being generated...
and there's no error either.
3. no errors in event viewer.
4. reboot sharepoint server. no change
5. check timer job definitions. one exists for immediate alerts, and
shows last run time that is recent.
i'm at a loss. ideas?
thanks.
- Prev by Date: SharePoint v2 Issue - Edit in Microsoft Office Word
- Next by Date: SharePoint v2 Issue - Edit in Microsoft Office Word
- Previous by thread: Survey showing Created By values as '***' instead of showing user
- Next by thread: wss3 shared workspace (infolabels) not updated
- Index(es):
Relevant Pages
|
