We help IT Professionals succeed at work.

Share Point Alerts

clintwolf
clintwolf asked
on
My users are not recieving alerts new changes/new/deleted items are added in sharepoint.
I've setup the SMTP in sharepoint to send out alerts to users.
When a user signs up to get an alert they do get the initial alert saying they have signed up.
But it comes in an odd format:

(the from address)
=?windows-1252?B??= [intranet@myserver.co.uk]
(the =?windows-1252?B?? changes based on he format you specifie for the email to be in... ie unicode etc)

(The body of the email is also odd)
Alert 'Supplier Logins' has successfully been added on ''.
You will receive alerts in e-mail. The timing and criteria for the alerts depend on the settings entered when the alert was added.
You can change this alert or any of your other alerts on the My Alerts on this Site page.

Notice that the "been addd on "" doesnt have the sharepoint name in it.

Please help.
Comment
Watch Question

Sounds like your shared timer job for alerts is not being executed. The intial alert you recieve gets sent by the SharePoint API. And then when changes occur in areas where alerts are set a MOSS shared timer job will fire off the mails.
If alerts are not working and you dont see a timer job definition titled 'Immediate Alerts' for your site you need to use these stsadm commands.
To check the timer jobs go to;
Central Admin - Operations - Timer Job Definition

stsadm.exe -o setproperty -url http://mysite.mydomain.com -pn alerts-enabled
-pv true

stsadm.exe -o setproperty -url http: http://mysite.mydomain.com -pn
job-immediate-alerts -pv "every 5 minutes"
I hope this helps.
Cheers
Bobby Habib - MOSS Technical Architect / Development Lead

Author

Commented:
Been there...
Done that...
Got the t-shirt...

Any other idea's?

Look at the odd bits in the signup alert post in original.  Surley that's got to be a clue as to the problem?
Are the timer jobs defined in central admin?
And can you see if they are executing without any errors?
You could do the following;
stsadm -o setlogginlevel -tracelevel verbose -windowslogginglevel information
and re-produce the issue. Make a note of the time of when you try and set up a alert and when you make a change to get a alert. Look at the time when the timer job executes and then go through the ULS logs to see if there are any exceptions. Go to the end of the ULS log and then search upwards for "error".
This should indicate where the problem is coming from, within SharePoints internal system. Let me know if you have worn the T-Shirt for this?
If you see any errors post them and I will have a quick look.
 Cheers

Bobby Habib - MOSS Technical Architect / Development Lead

Author

Commented:
Hey Bobb, thanks for the quick response.

I've tried running the above stsadm bit, but got an error:

Missing Operation name or Operation is missing.
Also, if  canget this to run.. where/what logs should I be looking at. (event view?)
Command should be the following;
 
stsadm.exe -o setlogginglevel
  [-category < [CategoryName | Manager:CategoryName [;...]] >]
  {-default |
   -tracelevel
        < None;
        Unexpected;
        Monitorable;
        High;
        Medium;
        Verbose;
        >
  [-windowslogginglevel
        < None;
        ErrorServiceUnavailable;
        ErrorSecurityBreach;
        ErrorCritical;
        Error;
        Warning;
        FailureAudit;
        SuccessAudit;
        Information;
        Success;
        >]
  }
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>
stsadm -o setlogginglevel -tracelevel verbose -windowslogginglevel information
Normally the log file sit here on a default install;  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS
 Here you can open the latest log file using a text editor and you should be away at seeing what happens internally within sharepoint. Do not leave this setting on for too long otherwise you will run out of disk space. Let me know what you see.
 Cheers
 Bobby Habib - MOSS Technical Architect / Development Lead

Author

Commented:
07/03/2010 21:25:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:25:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Initial table size: 20108359 in 155 entries       
07/03/2010 21:25:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Final table size: 20108359 in 155 entries       
07/03/2010 21:25:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:28:50.75       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:28:50.75       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Initial table size: 61650962 in 316 entries       
07/03/2010 21:28:50.75       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Final table size: 61650962 in 316 entries       
07/03/2010 21:28:50.75       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:30:32.30       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:30:32.30       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Initial table size: 0 in 0 entries       
07/03/2010 21:30:32.30       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Final table size: 0 in 0 entries       
07/03/2010 21:30:32.30       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:30:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:30:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Initial table size: 20108359 in 155 entries       
07/03/2010 21:30:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Final table size: 20108359 in 155 entries       
07/03/2010 21:30:54.47       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:31:42.05       STSADM.EXE (0x0BDC)                           0x197C      ULS Logging                         Unified Logging Service             8wsv      High          ULS Init Completed (STSADM.EXE, onetnative.dll)       
07/03/2010 21:31:42.07       STSADM.EXE (0x0BDC)                           0x197C      Windows SharePoint Services         Topology                            0      Medium        Diagnostics settings: 32768       
07/03/2010 21:31:42.18       STSADM.EXE (0x0BDC)                           0x197C      Windows SharePoint Services         General                             0      Medium        Windows SharePoint Services log file                                                                                                                                                                                                                                                                                                                                                                         
07/03/2010 21:31:42.18       STSADM.EXE (0x0BDC)                           0x197C      Windows SharePoint Services         General                             72ju      Medium        stsadm: Running setlogginglevel       
07/03/2010 21:31:42.19       STSADM.EXE (0x0BDC)                           0x197C      Windows SharePoint Services         Topology                            9e7d      Medium        Initializing the configuration database connection.       
07/03/2010 21:31:42.35       STSADM.EXE (0x0BDC)                           0x197C      Windows SharePoint Services         General                             72ju      High          stsadm: One or more required arguments are missing. Callstack:    at Microsoft.SharePoint.StsAdmin.SPSetLoggingLevel.Run(StringDictionary keyValues)     at Microsoft.SharePoint.StsAdmin.SPStsAdmin.RunOperation(SPGlobalAdmin globalAdmin, String strOperation, StringDictionary keyValues, SPParamCollection pars)       
07/03/2010 21:31:42.37       STSADM.EXE (0x0BDC)                           0x197C      ULS Logging                         Unified Logging Service             8wsw      High          Now terminating ULS (STSADM.EXE, onetnative.dll)       
07/03/2010 21:33:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:33:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Initial table size: 61650962 in 316 entries       
07/03/2010 21:33:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Final table size: 61650962 in 316 entries       
07/03/2010 21:33:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:34:40.34       w3wp.exe (0x018C)                             0x1D24      Windows SharePoint Services         General                             72nz      Medium        Videntityinfo::isFreshToken reported failure.       
07/03/2010 21:35:04.57       OWSTIMER.EXE (0x097C)                         0x09B0      Windows SharePoint Services         Timer                               9e99      High          AlertsJob failed to initialize site collection for Subscription id: {6A3C40A1-2E85-439C-94F2-EBEEFFF2F016}. Possibly incorrect siteurl http://myiphere:8181 for site collection Id: {31F37C1E-ED0C-418B-A541-358625434612},HRESULT 0x80070002       
07/03/2010 21:35:04.57       OWSTIMER.EXE (0x097C)                         0x09B0      Windows SharePoint Services         Timer                               9e99      High          AlertsJob failed to initialize site collection for Subscription id: {F626F997-6795-4A58-95F4-6242E7610313}. Possibly incorrect siteurl http://myiphere:8181 for site collection Id: {31F37C1E-ED0C-418B-A541-358625434612},HRESULT 0x80070002       
07/03/2010 21:35:04.57       OWSTIMER.EXE (0x097C)                         0x09B0      Windows SharePoint Services         Timer                               9e99      High          AlertsJob failed to initialize site collection for Subscription id: {9D3CACAB-AAEA-4603-A11A-5E16159FB1A0}. Possibly incorrect siteurl http://myiphere:8181 for site collection Id: {31F37C1E-ED0C-418B-A541-358625434612},HRESULT 0x80070002       
07/03/2010 21:35:04.57       OWSTIMER.EXE (0x097C)                         0x09B0      Windows SharePoint Services         Timer                               9e99      High          AlertsJob failed to initialize site collection for Subscription id: {AFD0B899-8B6E-4D0E-AF25-4C2E1ED25E75}. Possibly incorrect siteurl http://myiphere:8181 for site collection Id: {31F37C1E-ED0C-418B-A541-358625434612},HRESULT 0x80070002       
07/03/2010 21:35:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:35:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Initial table size: 0 in 0 entries       
07/03/2010 21:35:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Final table size: 0 in 0 entries       
07/03/2010 21:35:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:35:54.48       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:35:54.48       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Initial table size: 20108359 in 155 entries       
07/03/2010 21:35:54.48       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Final table size: 20108359 in 155 entries       
07/03/2010 21:35:54.48       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:38:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:38:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Initial table size: 61650962 in 316 entries       
07/03/2010 21:38:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Final table size: 61650962 in 316 entries       
07/03/2010 21:38:50.76       w3wp.exe (0x018C)                             0x0E1C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:40:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:40:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Initial table size: 0 in 0 entries       
07/03/2010 21:40:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Final table size: 0 in 0 entries       
07/03/2010 21:40:32.31       OWSTIMER.EXE (0x097C)                         0x209C      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.       
07/03/2010 21:40:54.49       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Entering MRU trim routine.       
07/03/2010 21:40:54.49       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Initial table size: 20108359 in 155 entries       
07/03/2010 21:40:54.49       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Final table size: 20108359 in 155 entries       
07/03/2010 21:40:54.49       w3wp.exe (0x0C08)                             0x0F68      Windows SharePoint Services         General                             0      Medium        Exiting MRU trim routine.
OK the problem is pretty obvious.
The URL has changed for your site. When you set up the alert timer job the URL was different and then has changed.
07/03/2010 21:35:04.57       OWSTIMER.EXE (0x097C)                         0x09B0      Windows SharePoint Services         Timer                               9e99      High          AlertsJob failed to initialize site collection for Subscription id: {6A3C40A1-2E85-439C-94F2-EBEEFFF2F016}. Possibly incorrect siteurl http://myiphere:8181 for site collection Id: {31F37C1E-ED0C-418B-A541-358625434612},HRESULT 0x80070002      

All the Alerts for a certain content database are located in the table "ImmedSubscriptions". The column that contains the URL is "SiteURL", so needs to be changed.
You can fix this by following this blog, but this is not supported.
 http://trycatch.be/blogs/tom/archive/2008/05/12/alerts-don-t-work-after-url-change.aspx
 Or you can set your URL in MOSS access management paths and recreate the timer job. As mentioned earlier.
Hope this helps.
Cheers
 
Bobby Habib - MOSS Technical Architect / Development Lead

Author

Commented:
I noticed that as well.. but some jerk has changed the password to SQL server so I'm locked out till tuesday.

Got detailed instructions on how to d the MOSS timer job magic trick?
LoL - No worries. Hope this helps you, the logging is a neat trick for working out internally what is happening within MOSS.
If you ever get stuck with MOSS, enable the logging and 9 out of 10 you will get a indication to your problem. ;0)
Have a good one,
Regards

Bobby Habib - MOSS Technical Architect / Development Lead  

Author

Commented:
Got detailed instructions on how to do the MOSS timer job magic trick?
Commented:
Just a comment: you could use the following command to "repair alerts" of this type.
stsadm -help updatealert
http://technet.microsoft.com/en-us/library/cc508980(office.12).aspx 

You would have to install SharePoint Administration Toolkit if you do not have it already.
Hope this helps.
Minesh ShahSharePoint & all about it

Commented:
Can you run SharePoint Products and Technologies Configuration Wizard on Index, this will work, i had similer situation (not the same) wherein wizard saved my life.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.