have an sbs 2008 install that generates daily reports but doesn't email 
them.
if i do it manually they generate and email to the correct address. so there 
seems to be nothing wrong with the process in that instance.

in the log file "Monitoring Report Detailed Network Report 
2010-06-06-06-00-00-0135.log" i get the results below.
is there another log file i can look at that will give more detail as to the 
error, or does anyone know a solution.

thanks

2010-05-07T06:00:00.826868 : Logger started at: 2010-05-07T06:00
2010-05-07T06:00:00.826868 : ***************** Starting
GenerateMonitoringReport task... *****************
2010-05-07T06:00:00.826868 : Generating Summary Network Report...
2010-05-07T06:01:04.590244 : XML generated...
2010-05-07T06:01:04.786264 : HTML generated...
2010-05-07T06:01:04.802265 : Report stored in archives...
2010-05-07T06:01:07.64855 : Failed to send report email.
2010-05-07T06:01:07.64955 : Generating Summary Network Report finished.
2010-05-07T06:01:07.64955 : ***************** GenerateMonitoringReport task
finished. *****************
 

On 06/06/10 11:03, mugen wrote:
>
> have an sbs 2008 install that generates daily reports but doesn't email
> them.
> if i do it manually they generate and email to the correct address. so
> there seems to be nothing wrong with the process in that instance.
>
> in the log file "Monitoring Report Detailed Network Report
> 2010-06-06-06-00-00-0135.log" i get the results below.
> is there another log file i can look at that will give more detail as to
> the error, or does anyone know a solution.
>
> thanks
>
> 2010-05-07T06:00:00.826868 : Logger started at: 2010-05-07T06:00
> 2010-05-07T06:00:00.826868 : ***************** Starting
> GenerateMonitoringReport task... *****************
> 2010-05-07T06:00:00.826868 : Generating Summary Network Report...
> 2010-05-07T06:01:04.590244 : XML generated...
> 2010-05-07T06:01:04.786264 : HTML generated...
> 2010-05-07T06:01:04.802265 : Report stored in archives...
> 2010-05-07T06:01:07.64855 : Failed to send report email.
> 2010-05-07T06:01:07.64955 : Generating Summary Network Report finished.
> 2010-05-07T06:01:07.64955 : ***************** GenerateMonitoringReport task
> finished. *****************
>
>
There is provision for detailed SMTP logging, but it is not enabled by 
default, and still may not help. If there is software blocking mail, 
there may be no entries in the SMTP logs.

The first question is whether the AV/security software on your server 
has provision for preventing email from being sent, with some programs 
being listed as exceptions. The McAfee system does that, under the 
heading of Access Protection. If so, check the log for an entry around 
the time the report should have been sent. If you find one for 
DataCollectorSvc.exe, that's your report mailer, and you need to add it 
to the list of exceptions.

-- 
Joe

Hello,

Thanks for your post.

As you found, reports are being scheduled and sent within the Windows SBS Manager service. Check the service execution log files under \program files\windows small 
business server\logs\MonitoringServiceLogs.

The service controls multiple tasks and some of those tasks conflict with each other. If something else conflicts with the daily report and that conflicting task has started running 
before the daily report task, the report will be sent delayed until the execution of that conflicting task is finished.

Moreover, if we manually generate and send the report, the report is sent as your currently logon user. But if it's a scheduled report, the scheduled report is sent as built-in 
SBSMonAcct@domain.com account. Therefore make sure the SBSMonAcct account is not disabled. Then please also check the Exchange Receive Connector Authentication 
which you are using for report email. 

1. You may open Exchange server 2007 management console(EMC)to find the Receive connector you would like to modify under Server Configuration, Hub Transport. (e.g. 
"Default servername" which use servername.domain.local as FQDN). 

2. Open the Authentication tab, make sure the "Transport Layer Security(TLS)", "Basic Authentication", "Exchange Server Authentication" and "Intergrated Windows 
authentication" are all checked.

3. On the Permission Groups tab, make sure "Exchange users", "Exchange servers", "Legacy Exchange Servers" are selected.

Then reboot the server and test the issue again. If the issue still persists, we may need to enable the Exchange Receive Connector protocol logging and look for further log 
information next.


Hope it helps.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================