Sharepoint 2016/2013 not sending alert on change in library
Technically we have Sharepoint 2016 setup. But we don't have anything in a cloud. All local server with SQL Server. So it acts like Sharepoint 2013.
Have 3 separate sharepoint sites. One of the sites has sub-sites in it. All set up at the same time.
None of them send out an alert on a library when a change is made to a document or a new document uploaded or deleted. All of them send out the alert when the user sets up an alert - but nothing when a document is changed.
Checked on with Stsadm on the sharepoint server and
- Alerts are enabled for the web app,
- Verified the time jobs properties (<Property Exist="Yes" Value="every 5 minutes between 0 and 59"/>.)
All the users have 1 email acct and have read or modify permissions
The sites are set up to send email through exchange - 1st alert saying you set up an alert comes through
All the doc change alerts go out to specific people in the company, not to any groups.
I've read where when the alert is set up on a library the email is sent out under the IIS identity. When a document is changed the email is sent out under WFE (Web Front End) / SP server identity. But not sure where to check from anything from here.
Any ideas?
Have 3 separate sharepoint sites. One of the sites has sub-sites in it. All set up at the same time.
None of them send out an alert on a library when a change is made to a document or a new document uploaded or deleted. All of them send out the alert when the user sets up an alert - but nothing when a document is changed.
Checked on with Stsadm on the sharepoint server and
- Alerts are enabled for the web app,
- Verified the time jobs properties (<Property Exist="Yes" Value="every 5 minutes between 0 and 59"/>.)
All the users have 1 email acct and have read or modify permissions
The sites are set up to send email through exchange - 1st alert saying you set up an alert comes through
All the doc change alerts go out to specific people in the company, not to any groups.
I've read where when the alert is set up on a library the email is sent out under the IIS identity. When a document is changed the email is sent out under WFE (Web Front End) / SP server identity. But not sure where to check from anything from here.
Any ideas?
ASKER
Thanks Walter for the point on 2013 vs 2016.
I removed myself from a site, added me back (making sure Email was checked & it sends on any changes) , then added a document. Same thing. Received a notice saying I'm setup to get alerts on the library but nothing came thru when I added a new document.
One thing on Outlook every morning I receive an error. Not sure if it has anything to do with this.
Task 'SharePoint' reported error(0x80040102): 'Outlook cannot connect to the SharePoint List(Projects - Project Group Contacts). The server may not be reachable from your location. Contact the Sharepoint site administrator for more information. HTTP 0.'
This particular sharepoint site does not have any contacts. I'm an Owner.
I'm thinking it has to be a rights thing. Just not sure how to check if it's hooked up correctly on WFE (Web Front End) / SP server identity.
I removed myself from a site, added me back (making sure Email was checked & it sends on any changes) , then added a document. Same thing. Received a notice saying I'm setup to get alerts on the library but nothing came thru when I added a new document.
One thing on Outlook every morning I receive an error. Not sure if it has anything to do with this.
Task 'SharePoint' reported error(0x80040102): 'Outlook cannot connect to the SharePoint List(Projects - Project Group Contacts). The server may not be reachable from your location. Contact the Sharepoint site administrator for more information. HTTP 0.'
This particular sharepoint site does not have any contacts. I'm an Owner.
I'm thinking it has to be a rights thing. Just not sure how to check if it's hooked up correctly on WFE (Web Front End) / SP server identity.
I would check a few things. First, run this PowerShell script on your SharePoint server:
This script would allow you to experiment with some of the send parameters, such as including an attachment. More here: http://code2care.org/2015/send-email-with-attachment-using-sharepoint-powershell/
Check this page for troubleshooting outbound mail:
https://social.technet.microsoft.com/wiki/contents/articles/13771.troubleshooting-steps-for-sharepoint-alert-email-does-not-go-out.aspx
It's a little old, but a lot of it is still relevant. I'd pay attention to the part about the timer jobs that govern sending alerts. An ad-hoc email message may succeed, but alerts are sent in batches via timer jobs. If the jobs are not running (or are on a schedule that's too infrequent) you can edit them via Central Admin --> Monitoring --> Review Job Definitions. Look for a job named "Immediate Alerts" (this governs sending out immediate and scheduled alerts).
I know the Alert confirmation email is being sent, but subsequent emails might be tagged as spam. A spam intercept will fail silently, but you can check logs on your anti-spam service.
Check the Application logs on your SharePoint web server. You might see, for example, event 6857, "cannot connect to host". You can also see other errors, such as whether the mailbox can be found on the destination, or if your SMTP server is not set up for relay.
I had a new SharePoint 2016 farm that had issues with outbound mail, because a default Outbound Mail setting (use TLS for secure connections) didn't get along with the customer's mail server. In SP 2013, you were stuck with Anonymous SMTP connections on Port 25. But in SP 2016, you now have the option for secure connections on a custom port. Also, make sure that your mail server will accept connections from your client (which will be the WFE from which the website is hosted).
$email = "youremail@yourdomain.com"
$subject = "SP 2016 Test Farm - Test Email"
$body = "Now is the time for all good men to come to the aid of their country."
$site = New-Object Microsoft.SharePoint.SPSite "http://yoursite.yourdomain.com"
$web = $site.OpenWeb()
[Microsoft.SharePoint.Utilities.SPUtility]::SendEmail($web,0,0,$email,$subject,$body)
# A True or False will confirm the message has been sent or notThis script would allow you to experiment with some of the send parameters, such as including an attachment. More here: http://code2care.org/2015/send-email-with-attachment-using-sharepoint-powershell/
Check this page for troubleshooting outbound mail:
https://social.technet.microsoft.com/wiki/contents/articles/13771.troubleshooting-steps-for-sharepoint-alert-email-does-not-go-out.aspx
It's a little old, but a lot of it is still relevant. I'd pay attention to the part about the timer jobs that govern sending alerts. An ad-hoc email message may succeed, but alerts are sent in batches via timer jobs. If the jobs are not running (or are on a schedule that's too infrequent) you can edit them via Central Admin --> Monitoring --> Review Job Definitions. Look for a job named "Immediate Alerts" (this governs sending out immediate and scheduled alerts).
I know the Alert confirmation email is being sent, but subsequent emails might be tagged as spam. A spam intercept will fail silently, but you can check logs on your anti-spam service.
Check the Application logs on your SharePoint web server. You might see, for example, event 6857, "cannot connect to host". You can also see other errors, such as whether the mailbox can be found on the destination, or if your SMTP server is not set up for relay.
I had a new SharePoint 2016 farm that had issues with outbound mail, because a default Outbound Mail setting (use TLS for secure connections) didn't get along with the customer's mail server. In SP 2013, you were stuck with Anonymous SMTP connections on Port 25. But in SP 2016, you now have the option for secure connections on a custom port. Also, make sure that your mail server will accept connections from your client (which will be the WFE from which the website is hosted).
Another tip: manually run the "Immediate Alerts" timer job and watch the ULS log for any errors.
Just curious - does this work on any other library?
ASKER
This does not work on any of the libraries.
Thanks for the info - if you haven't yet, follow Greg's great troubleshooting steps. The powershell test is the first thing to do. You need to determine if the problem is with the mail system as it is configured for SharePoint or SharePoint itself. Normally SharePoint won't cause this issue, but never say never. Also, the automated notice that you have signed up for alerts is a good indicator that mail is working, so this entire issue is puzzling, but that's SharePoint. :-)
Good luck...
Good luck...
ASKER
Sorry for not responding quicker. Projects came up.
Greg I ran the script and received an email.
In the server windows log -> Application: There's lots of 6398 errors: Task Category Timer. In the details = "Failed to run flow Microsoft.CustomDictionary
In SP Central Admin -> Timer Job Status -> Job History: There's many Search Custom Dictionaries Update Status Failed. We don't have search enabled on this.
Ran a health report and came up under Configuration: Missing server side dependencies SPTimerService. When I open this link it says Configuration:
"[Upgrade] The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped are
[Security] All SQL database roles are present "
Jess
Greg I ran the script and received an email.
In the server windows log -> Application: There's lots of 6398 errors: Task Category Timer. In the details = "Failed to run flow Microsoft.CustomDictionary
In SP Central Admin -> Timer Job Status -> Job History: There's many Search Custom Dictionaries Update Status Failed. We don't have search enabled on this.
Ran a health report and came up under Configuration: Missing server side dependencies SPTimerService. When I open this link it says Configuration:
"[Upgrade] The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped are
[Security] All SQL database roles are present "
Jess
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Greg
Thanks for your assistance - you lead me to the answer.
Found this https://www.ccrossan.com/blog/microsoft-sharepoint/sharepoint-2016-outbound-smtp-failures/
Spoke to my server guy. He added a connector on Exchange and modified the encryption. He captured the network traffic to see exactly what was going on.
And it's working now.
Thanks a bunch for the help.
Jess
Thanks for your assistance - you lead me to the answer.
Found this https://www.ccrossan.com/blog/microsoft-sharepoint/sharepoint-2016-outbound-smtp-failures/
Spoke to my server guy. He added a connector on Exchange and modified the encryption. He captured the network traffic to see exactly what was going on.
And it's working now.
Thanks a bunch for the help.
Jess
Glad I could help!
Check the documents settings on the library directly. When you select the "Alert" con in the ribbon while you are at the library, there are some options that control how and when an alert, or mail goes out. Check that if you have not.
As far as your other trouble shooting steps, they seem like a good process. Just keep in mind that SharePoint 2016 even when on premise (as you have) is SharePoint 2016 and it is acting like 2016 and not 2013. (SharePoint 2016 does not have to have anything to do with the cloud if you don't want it to.)
Hope that helps...