From the mailbag tonight comes the question "have you come across a system that has randomly stopped emailing the nightly network reports? Mine has stopped and I can’t work out why, they are still set up correctly and I can manually generate them"
And I've seen this before but I always have a hard time finding this old post, so I'm going to reblog it for future bingling.
Bing/Google terms:
sbs diva sbs 2011 monitoring email not sending
For monitoring email cannot be sent issue.
------------------------------------------------
Most of this issue is caused by incorrect configuration on Exchange receive connectors. You can all Exchange Receive connectors and run fix my network wizard to fix SBS specific ones. However, for Default <servername> connector, FNCW cannot create it, you need to manually create by steps in the article below:
Fix My Network wizard (FNCW) Fails to Fix the Exchange SMTP Connectors in SBS 2008
http://blogs.technet.com/sbs/archive/2008/09/29/fix-my-network-wizard-fncw-fails-to-fix-the-exchange-smtp-connectors-in-sbs-2008.aspx
If this doesn't work, we could investigate this issue by reviewing the following log "C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs" folder, there will be a file called DataServiceComponents.log, this file usually is very huge, this is because it contains almost every detailed error file in it. However, it is incredibly useful, you will be able to find the exact error. Here is an example which shows why reporting email failed to send.
[364] 091128.120849.1072: AdminTME: Status: TaskId = TaskGenerateMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: True, Warning: False, Continue: True, Message:
---<< This line shows the TaskGenerateAndEmailReport, email generating and sending message can be found here, you need to search this key word to locate the root cause.
[364] 091128.120850.4192: Exception:
---------------------------------------
An exception of type 'Type: System.Net.Mail.SmtpException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 11/28/2009 12:08:50
Message: Failure sending mail.
Stack: at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MailUtil.SendMail(String from, String[] to, String subject, Boolean isBodyHTML, String body, String inlineAttachmentPath, String[] attachments)
---------------------------------------
An exception of type 'Type: System.Net.WebException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 11/28/2009 12:08:50
Message: Unable to connect to the remote server
Stack: at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6, Int32 timeout)
at System.Net.PooledStream.Activate(Object owningObject, Boolean async, Int32 timeout, GeneralAsyncDelegate asyncCallback)
at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback)
at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralAsyncDelegate asyncCallback, Int32 creationTimeout)
at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
---------------------------------------
An exception of type 'Type: System.Net.Sockets.SocketException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 11/28/2009 12:08:50
Message: No connection could be made because the target machine actively refused it fe80::309c:a749:6920:e429%10:25
Stack: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
The key aspect of the exception is this:
No connection could be made because the target machine actively refused it fe80::309c:a749:6920:e429%10:25
(In this case, the IP address is an IPv6 address which is not correct, it should be an IPv4 address for SBS 2008, we solved the issue by removing IPv6 address in host files.)
[TIP]: If you have any tough issue about monitoring, go to C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs\DataServiceComponents.log
Bottom line look in that log file, it should give you a hint to what's going on.
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")