New MOSS 2007 installation w/SP2 Alerts now working at all. The only email the user receives is when s/he is added to authorized users for the site. No email when the user creates alerts. I run the stsadm command to check if alerts are enabled and they are. Any ideas where to look next? Thanks CostasCostas Tsaklas - http://costas.cpstechgroup.com

Looks like a security issue. Can you check out SharePoint log? Oleg

Hi Oleg, I don't see anything wrong in the logs. Anything in particular I should be looking for? Thanks CostasCostas Tsaklas - http://costas.cpstechgroup.com

The SMTP server is setup to allow anonymous access. Also, the initial email that goes to the user when he is added to the site is going successfully. Only the alerts do not work. Knowing that is there anything else I need to look at to solve that problem? Thanks for the help Costas Costas Tsaklas - http://costas.cpstechgroup.com

The job definition that send alerts is called Immediate Alerts. Could you chek out in Central Administration->Operations->Timer Job status a status of this job? Oleg

It looks like the problem might be with SMTP. I'm working with our messaging group to solve this. I'll update as soon as I know more. CostasCostas Tsaklas - http://costas.cpstechgroup.com

We solved the SMTP issue and now we are at the point where 'sometimes' the initial email is sent when the users registers for alerts, other times it does not come. For a picture library, alerts come in but for document libraries, the alerts do not work. Weird... any thoughts? Thanks Costas Tsaklas - http://costas.cpstechgroup.com

Did you check out Immediate Alerts job status? Oleg

Yes, it shows as succesful Costas Tsaklas - http://costas.cpstechgroup.com

Try to change Event Throttling to All & Error in Central Administration -> Operations -> Diagnostic Logging. Maybe it will give you more details in SharePoint log. Oleg

I did that, created a new alert (I received no email), then I changed a document in the library that had the alert and I still didn't receive any emails. I looked in the log file and there was no error registering. Actually the last log entry was 15:28, I created the alert at 15:30 and I changed the file at 15:32... I looked at the log again, still last entry 15:28Costas Tsaklas - http://costas.cpstechgroup.com

When you change Diagnostic logging to All ULS should growing very fast. Try to restart Windows SharePoint Services Tracing service and try to reproduse the issue again Oleg

This is weird, I created three alerts, received no emails and when I went to the logs there was nothing related to any kind of error. I did a log search for 'ImmedSubscriptions' the table where the alerts are stored and nothing was returned.Costas Tsaklas - http://costas.cpstechgroup.com

You can use SQL Profiler to see what is really going on when you create an alert. Oleg

I might do that, thanks for sticking with me. For some reason I think something is going on with SMTP but I don't have direct acess to it. I'll follow up on Monday with the messaging team to make sure everything is setup properly on their end CostasCostas Tsaklas - http://costas.cpstechgroup.com

I've put together a troubleshooting guide for SharePoint Alerts. http://sharepointalert.info/troubleshooting-sharepoint-alerts/ Sounds like your well underway with this but it may help. Good luck!...Ryan

How many WFEs do you have in your farm? If you can receive alerts sometimes and sometimes not, one possible cause is that your SMTP is configured to be accessed from only some IP address and not all your WFEs are in this allowed list. Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Ryan, I already went through that post :-) Thanks for putting it together. I don't have direct access to the messaging end so I have to work through the team but if I don't find the solution there, I'll dig again to your post. Thanks again, CostasCostas Tsaklas - http://costas.cpstechgroup.com

It's just one WFE..Costas Tsaklas - http://costas.cpstechgroup.com

The problems continue.... This time I used my personal corporate email account in the 'From' section of the 'Incoming Email Settings'. As soon as I create an email alert, the following message is going to my email account: "The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system adminstrator. <SERVENAME.DOMAIN #5.2.1> The messaging guys telnet from the above server (<SERVERNAME.DOMAIN>) and they send a message to the same person that created the alert (using telnet) and the message reached its destination. Now they are telling me to look back to SharePoint for the issue. Any thoughts? To add some additional info: When a user subscribes to alerts for a 'Links' list or a 'Pictures' library everything works. For the remaining libraries, the above error message is displayed. That sounds like a SharePoint issue. Thanks Costas Costas Tsaklas - http://costas.cpstechgroup.com

What follows is the description of Non-Delivery status code from http://technet.microsoft.com/en-us/library/bb124840(EXCHG.65).aspx : NDR status code Event log message ID Event log message severity Event log message text Possible cause Troubleshooting 5.2.1 3013 Warning A non-delivery report with a status code of %1 was generated for recipient %2 (Message-ID %3). Local mail is refused because the message is too large or the recipient’s mailbox is not mail-enabled. A missing Master Account Security ID (SID) number on the recipient can also cause this error. Check access permissions as well as the message size. Check if the recipient has a SID in Active Directory. Check to ensure that the recipient mailbox is mail-enabled. However, it may not apply to your issue. Your issue may be caused by Named Property Exhaustion in Exchange. See what follows from: http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx : When an add-in that adds named properties or X-headers to messages is installed in Outlook, certain messages may not be sent to other users in the organization. In this scenario, the sending user receives a non-delivery report (NDR) that resembles the following: The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator. And SharePoint alert email does use X-headers. To solve this issue, you may follow the steps in the link below to enlarge the Named Properties and Replica Identifier Quotas. http://technet.microsoft.com/en-us/library/bb851493(EXCHG.80).aspx Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Gu, Thanks for the reply. We are using Exchange Server 2003. The article for Name Property Exhaustion refers to Exchange 2007. Any ideas how to solve this with 2003? Thanks CostasCostas Tsaklas - http://costas.cpstechgroup.com

I found this blog about named property exhaustion in Exchange 2003: http://blogs.technet.com/b/ehlro/archive/2009/08/31/named-properties-problems-a-workaround.aspx ; However, I am not Exchange expert, so please post your question to Exchange forum for a more seasoned advice. Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Sorry, made a big mistake above: According to http://technet.microsoft.com/en-us/library/cc263462.aspx, the SMTP server must be configured to allow anonymous SMTP e-mail submissions.

Finally the problem was solved. As expected, the issue was with the Messaging Server. We were using a virtual name for the Exchange Cluster and for some reason something working out well. When we used one of the two servers in the clusters, all alerts were arriving on time. Thanks for the help everyone provided. CostasCostas Tsaklas - http://costas.cpstechgroup.com

Costas, I am having very similar issues. When looking at your resolution to this problem, can you clarify to me what you mean by virtual name for the Exchange Cluster? Do you mean the alias? and if so, where in SharePoint did you change this to fix the problem? Was it in Central Admin > Operations > Outgoing Mail Settings.....outbound SMTP Server? thanks, Thiago Silva--Thiago

Thiago, The virtual name is the DNS entry that points to the Exchange cluster. For example, the DNS entry is xyz.domain.com and the cluster conttains server1.domain.com and server2.domain.com For some reason xzy.domain.com wasn't working so we try the other two names and one of them (weird...) worked. So we used server2.domain.com in the entry for 'Outbound SMTP server' in Central Admin CostasCostas Tsaklas - http://costas.cpstechgroup.com